Translation groups overview
In WorldServer, TMs are generally associated with AIS paths. This association identifies the TM to use for leveraging content stored at the AIS path location. It also identifies the TM to be updated when new translations are supplied for this same content. Only one TM selection can be associated to an AIS path, which limits the ability to leverage translation information stored in another TM. The customer has the option of storing all translation information into a single TM, but for business reasons, this may not be appropriate. Nonetheless, the user may need to leverage across multiple TMs. The TM group feature addresses this consideration and allows users to group TMs together so that they can be leveraged as a single entity. As a result, instead of associating a TM with an AIS path, the user can specify a TM group.
The WorldServer TM group implementation is based on rank. Within the TM group definition, TMs are not given equal weight. When you create a TM group, you need to choose the TMs to be included, and also establish the order of precedence. Additionally, only one TM in the TM group can be designated as the TM to receive new or updated translations. This TM is called the update TM or write TM.
The use of a TM group does not yield the same results as using a single TM that contains all the data of the TMs within a TM group. To effectively use TM groups, you need to understand the order of precedence and how this affects the leverage process. When a TM group is used during the leverage process, it queries each of the TMs in the group individually and in order of precedence.
An acceptable match is defined as either a 100% or ICE match. Within the current TM being leveraged, the best match will be taken. (That is, ICE will always be preferred over 100% matches.) As a result, if a 100% match is found in a TM of higher precedence, then an ICE match candidate for that segment will not be sought in the lower-ranked TMs. (In the same TM, of course, an ICE match is always chosen over a 100% match.)
Split/merge options are also evaluated before moving to the next TM in the TM group. Once a split/merge candidate has been accepted, it cannot be undone. Splitting or merging segments may lead to improved leverage against the current TM. Depending on the configured auto split/merge settings, the resulting segments might not result in a 100% or ICE match. Because the split or merge cannot be undone, the new segments may disrupt the ability to find an acceptable match in TMs of lower precedence. The impact is that the actual results may not be the expected results. Split/merge occurrences can be identified within the Browser Workbench.