Repairing TM Entry Linkage after moving assets or implementing path normalization
TM entries created within WorldServer are associated with the segment and asset that led to its creation. This linkage is important in establishing and maintaining additional content context. The context can be used to influence ICE and exact match ranking, to provide additional ICE context requirements, or to penalize matches applied to a different asset context. Depending on the use of this information, maintaining this information can be critical.
If translated content is moved, the TM entries that were previously created from it will be orphaned. Further translations will be added to the TM for the content instead of updating the existing TM entries, since the new location of the content will result in the assets being treated as new or different assets. As a result, the movement of content within the AIS system is discouraged, and should only be done if absolutely necessary.
The use of path normalization that is introduced at some point after the initial setup of WorldServer can result in a similar issue in that it affects the TM's perception of where the asset actually exists. Processing the same files (stored in the same AIS location) after path normalization has been implemented may lead to the TM to see the assets as being located somewhere new (as determined by the normalization implementation.) The end result is that the previous TM entries are now orphaned from the content they were originally associated.
While not ideal, one or both of the above scenarios may happen. The process below, while involved, provides a means for restoring the linkage of the assets to their orphaned TM entries. In short, the solution is to export the entries for each affected asset into a TMX file, update the paths globally in the TMX file, delete the original entries, and upload the modified TMX.