- Can a Source Publication have multiple Target Publications?
- Can a Target Publication have multiple Source Publications?
I think I've seen the first scenario, where Global Content needs to be translated into the same language pair but to separate child Publications. But I'm trying to figure out how to avoid conflicts if the second scenario is possible.
The use case would be for a given Target (e.g.
040 Marketing Content - Spanish for the US), the business wants the ability to translate from either English Publication:
020 Global Contentor
030 Marketing Content.
If possible, how (or when) could we copy BluePrinting rules so the closest localized items "win," in case of conflicts (see example below)? For example:
- During Translation Job creation
- When Translation Jobs start
- Or maybe failing individual items?
This is somewhat related to "Multiple languages in a source Publication?" but there I was asking about multiple locations within a given Publication.
As an example, we might have the following:
- Component "Policies" created in 020 Global Content in English (US)
- "Policies" localized in 030 Marketing Content in English (US) <-- we only want to permit translations from this Publication
- "Policies" localized in 040 Marketing Content in Spanish (US)
In this case, with "Policies" localized in 030, the business wants this version to be the shared item in 040. We'd also want to prevent translation jobs started from 020, which I believe would directly update 040, regardless if 030 is localized.
In other words, could we only allow translations from the closest localized parent Publication?