In XTM Workbench, you might sometimes come across the following message in the metadata for the TM entry for a particular segment: “This TM entry has been changed and no longer meets the criteria to be qualified as a match”.

Open

There are multiple scenarios in which this message might occur:

A newer version of a TM match exists

In this case, the message is displayed because, when a project has been created, the segment in question has been populated by a TM match which is then marked with the message “This TM entry has been changed and no longer qualifies as a match”.

Then, after some time, a new project containing exactly the same segment has been created for one of the XTM Cloud customers whose TM had been used in the initial project and, in accordance with the global TM settings for your XTM Cloud instance, a new TM entry has been created (Configuration → Settings → Translation → TM → Matches - general:

• Modify the existing TM record if the project segment has the same: Source, Inlines, Context, Tags;

• Modify the existing TM record if the project segment with Segment ID has the same: Source, Inlines, Segment ID, Context, Tags).

Open

When you display the original project in XTM Workbench, you will actually see the message “This TM entry has been changed and no longer qualifies as a match”.

EXAMPLE:

Both the initial and later TM match have been created from segments that contain Segment IDs. As the tags and segment IDs for those 2 segments are different, a new TM entry has been created, instead of updating an existing TM match.

This TM entry has been applied to the project in question, replacing the previous match and being placed at the top of the matches list in the Matches tab, in the docked panel. Consequently, XTM Cloud has indicated that the previous TM match could not be returned anymore, since a newer TM match with the same source and target has been found for this segment. Two matches with matching source and target are treated as duplicates so only the newer match could be displayed.

Generally, XTM Cloud does not display duplicates (same source and target in both TM matches). Therefore, when there are suddenly two TM matches with the same source + target + score, in a segment, one of them – the older one – must be filtered out . If the older TM match has been inserted during project analysis and a TM match update is performed later, in XTM Workbench, the warning described above is displayed for this older TM match.

You do not use Not Approved Memory

Another scenario assumes the case that you do not use Not approved TM at all.

In this case, a TM match is returned as Approved during project analysis, but its status has changed to Not approved (due to, for example, changing the status in the TM base in the XTM Cloud UI), while the XTM Workbench session is active.

For this reason, the TM match must be deleted because you do not want not approved translation memory to be present in your projects. For this reason, the warning described above is displayed for this TM match.

A Leveraged match transforms into an ICE match

Imagine you have a Leveraged match that is inserted during project analysis. Then, in an XTM Workbench session, a new TM entry is displayed – an ICE match.

It points to the same TM entry as the Leveraged match, because it originates from the same TM record. This can happen if the Linguist confirms the segment and adds context to the very same TM entry, according to the global TM settings:

The TM entry has therefore become an ICE match, so it no longer qualifies as a valid Leveraged match. For this reason, the warning described above is added to the metadata for this TM match, in XTM Workbench, and the ICE match must be displayed instead.

A Leveraged match transforms into an ICE match due to being updated in another project containing the same source file

Another scenario also involves Leveraged and ICE matches: once again, a Leveraged match is inserted during project analysis. Then, a new project with exactly the same source file is created, and the same Leveraged match is also inserted in this new project. The Linguist accepts the TM match in that second project, which causes a new TM entry to be created with the appropriate context, according to the global TM settings:

This option is also selected, in the Leveraged matches section (Configuration → Settings → Translation → TM → Leveraged matches → Search only if there are no ICE matches).

You return to the first project and open XTM Workbench in edit mode. A new ICE match is displayed. Since there is an ICE match, the Leveraged match can no longer be returned so, once again, the warning described above is displayed for this Leveraged TM match.

A TM match has been modified or deleted

When a particular TM match has been modified in some way, a suitable message will be displayed in its metadata, stating that the TM match has been modified, and how.

A populated TM match comes from an additional XTM Cloud customer

The message might also be displayed in a TM match that does not come from the project’s main XTM Cloud customer, but from one that has been added to the project.

The root cause for such a message to be displayed is that the Project manager must have removed the additional customer from the project at some point in time during the project’s life cycle.

A populated TM match has a tag

The message might also be displayed in a TM match that had some tags right after project creation. Once the project has been created, the Project manager then adds a TM penalty profile to it, that is supposed to remove all TM matches with that tag. As a result, a suitable message will be displayed for the TM match in question.