If configured, Translation Jobs can have metadata fields that will appear to translators in the translation management system as a separate (XML) file.
We can configure multiple Metadata Schemas in the Translation Manager configuration with the caveat that "only one Metadata Schema is allowed per BluePrint hierarchy".
What does "BluePrint hierarchy" mean in this context? Is that the Publications between a Source and Target?
Or is that BluePrint hierarchy as an entire stand-alone tree? Where typically there's only one BluePrint hierarchy in a given Content Manager, though you could have multiple such trees.
Does this impact the Translation Job screen?
Does it work like other Metadata Schema drop-downs where the user can choose from a list of configured Metadata Schemas?
I'm looking for a simple way for a CMS user to share a Staging URL (internally) from a Translation Job to the translator.
I'm aware of the Translation Preview capability and the idea we can (sometimes) programmatically determine the URL for content or pages, assuming a given Component is on a published Page for the given target.
But do we have programmatic access to the Translation Manager job Metadata?
I don't think we create an actual Component for the translation job metadata, so Event System wouldn't apply, right?
The desired user story is something like this.
As someone creating a translation job in the CMS, when available, I would like to automatically determine and share the URL to the Staging website for a given piece of content with my translator. This would save me time for finding and copying the URL into a given Translation Job.
Is Translation Job Metadata a good or possible fit here? If not, what might be an approach to share known URLs with a Translation Job without a full Translation Preview setup? :-)