When sending a bundle that contains more than a hundred items for translation (to TMS), the translation job (on the Tridion side) is split into multiple translation jobs on the TMS side.
For example, if a bundle containing 280 components was sent for translation then there would be three matching jobs created in TMS:
- TMS job 1 - 100 tasks
- TMS job 2 - 100 tasks
- TMS job 3 - 80 tasks
This 'maximum job size' is configured within the
Looking at the Configuring maximum job size page in the online documentation, one reason given for this is:
... Splitting the translation job up into sizeable chunks allows you to manage and process translations better and faster by scaling the job between several translators.
Q1. Given that each task (i.e. each individual Tridion component) can be assigned to a separate user (e.g. translator) in TMS (even if they're in the same TMS job), is this a valid reason?
Q2. Are there any drawbacks (performance, functional or otherwise) to setting the
<MaximumJobSize> to a really large number (e.g. 2000) to prevent Tridion translation jobs from being split into multiple TMS jobs.
My client's concerns are that:
- Splitting the translations into multiple TMS jobs increases the risk that one of these TMS jobs is missed/delayed - holding up the entire translation (on the Tridion side), and
- That it may be unclear to the translator(s) that these tasks (e.g. all 280 of them) are related.