Documentation Center

Repairing linkage to orphaned TM entries

This procedure enables restoring the linkage of assets to their orphaned TM entries.

Procedure

  1. Identify the impacted TM entries. Using the TM search tools, you can search for the entries associated with a specific asset or a collection of assets sharing a common path by constructing an advance query against the “Entry of Origin” field.
  2. Export the selected Tm entries.The results of step #1 should be exported twice. One file will be keep for backup purposes, while the other will be updated.
  3. Update the paths in the TMX file.The TMX file to be updated can then be edited using any text editor of choice. You may be able to easily use the editor’s search and replace tools to effective make the necessary file path changes. For instance, consider the following TM entry stored in a TM file:
    <tu srclang="en-US" creationid="Admin"
    creationdate="20070726T205127Z" changeid="Admin"
    changedate="20070726T205127Z" tuid="23-0">
    <prop type="x-idiom-source-ipath">/product1/release1/myFile.html</prop>
    <prop type="x-idiom-target-ipath">/product1/release1/myFile.html</prop>
    <tuv xml:lang="en-US">
    <seg>Segment Text</seg>
    </tuv>
    …
    
    As a result of the move or path normalization process, the /release1 portion of the path is no longer a part of the path. You may be able to search for all occurrences and replace it with “” (nothing).
  4. Import the updated TM entries into a test TM.The process of importing the TM entries will associate the entries with the asset identified through the source and target paths stored in the TMX file entries.
  5. Verify that the linkages are in fact properly established. To do this, take one of the assets that should be linked to the TM entries and associate it with the test TM. Record the count of TM entries imported into the TM after the import. Next perform a mock translation of the asset. Save and update the TM. Search the test TM for the entries associated with that asset and verify that the TM entries have been updated with the previous entries now designated as history records. The number TM entries in the TM should not have increased. Ideally, you would run all the assets through a mock translation process, and verify that the number of TM entries remains constant.
  6. Delete the original TM entries from the production TM.Provided that the test in step #5 passes, delete the set of TM entries identified in step #1.
  7. Import the updated TM entries into the production TM.Import the updated TMX file from step #3.