WorldServer - after importing a TMX file containing the Usage Count attribute to more than 0 into a new/different WorldServer TM, that value is re-set to 0

We have exported a TM (TMX file) from a WorldServer Translation Memory. Many TM entries contained the Usage Count attribute with a value higher than 0, meaning that the TM entry had been re-used more than once during segmentation when applying that TM. This is how the system attribute Usage Count attribute would display in the Translation Memory in WorldServer (as an example):



The Usage Count system attribute and its value is written into the TMX during the export process as (for example):
 

<tu srclang="en-GB" creationid="System"
      creationdate="20230609T105258Z" changeid="System"
      changedate="20230609T105258Z" usagecount="4"
      lastusagedate="20230614T072014Z" tuid="42829933-1">

After importing the same TMX into a different Translation Memory, the Usage Count attribute is reset to 0. What is the reason for this behaviour?

Preface: WorldServer records the number of segment matches that each translation memory (TM) provides for each task during the segmentation process, as well as the number of times each individual segment has been used as a match (Usage Count). This information gives you a better understanding of which TMs and segments provide the most value. However, this usage count is specific to the Translation Memory and the TM Entry that was applied during segmentation. The usage count is updated every time an asset is segmented. The usage count can only be applied in combination with the TM that is applied.

- When importing a TMX file containing a TM Entry with a Usage Count more than 0 (i.e. 1, 2 or higher) into a different or new TM, after the import, the Usage Count is reset to 0 because - in fact - at the time of the import that TM entry in that TM was not reused during segmentation. Therefore, the behaviour that sets the Usage Count to 0 after an import in a different TM is correct.

- When importing a TMX file containing a TM Entry with a Usage Count more than 0 (i.e. 1, 2 or higher) back into the same TM it was exported from without any change, the import will result in no change. The existing TM Entry with a higher Usage Count will not be overridden and will still be present. This behaviour is correct and to be expected.

- When exporting a TM Entry with a Usage Count higher than 0 to a TMX file and then importing it back in the same Translation Memory after changing something, for instance, the target translation, the existing TM Entry will be overridden or updated with any change BUT the Usage Count will be reset to 0.  This behaviour is correct and to be expected.

This article is relevant:

WorldServer - what is Cache TM and how is it used?