...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
In XTM Workbench, you might sometimes come across the following message displayed in the metadata of a particular 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”.
...
| Note |
|---|
IMPORTANT! The message only applies to the for TM matches which were that have been populated during project analysis and no longer meet relevant criteria once an XTM Workbench session is triggered. From a business perspective, there are some general rules:
|
...
When does the message occur?
There are multiple scenarios in which this message might occur:
A newer version of a TM match exists
When In this case, the message is displayed because, when a project had has been created, the segment in question was has been populated by a TM match , which is currently then marked with the message “This TM entry has been changed and no longer qualifies as a matchmatch”.
Then, after some time, a new project with containing exactly the exact same segment was has been created under for one of the XTM Cloud customers , which whose TM had been used in the initial project , and according to and, in accordance with the global TM settings of for your XTM Cloud instance, a new TM entry was 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).
...
Upon re-entering When you display the original project in XTM Workbench for the initial project, you will actually see the message “This TM entry has been changed and no longer qualifies as a matchmatch”.
| Info |
|---|
Remember to always access a particular segment in XTM Workbench in the edit mode, to make sure ensure that the related TM matches are updated. |
EXAMPLE:
Both the initial and further TM matches were later TM match have been created from the segment that contained the Segment ID. As the tags and segment IDs for those 2 segments were are different, a new TM entry has been created, instead of updating an existing TM match, a new TM entry has been created.
This TM entry has been applied to the reported project in question, replacing the previous match and being placed at the first place the top of the matches list in the Matches tab of , in the docked panel. When this had happenedConsequently, 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 was has been found for this segment. Two matches with matching source and target are viewed treated as duplicates , therefore so only the newer match could appearbe displayed.
Generally, XTM Cloud does not show display duplicates (same source and target in both TM matches). Therefore, when suddenly there are suddenly two TM matches in a segment that have with the same source + target + score, in a segment, one of them has to be filtered out – the older one – must be filtered out . If the older TM match was populated has been inserted during project analysis and a TM match update subsequently occurs is performed later, in XTM Workbench, then the warning described above is displayed for this older TM match gets the warning.
You do not use Not Approved Memory
Another scenario assumes the situation in which case that you do not use Not approved TM at all.
...
For this reason, the TM match has to must be deleted because you do not want to see not approved translation memory to be present in your projects. ThereforeFor this reason, the said warning described above is displayed for this TM match gets a warning accordingly.
A Leveraged match transforms into an ICE match
Imagine you have a Leveraged match populated that is inserted during project analysis. Then, in an XTM Workbench session, a new TM entry appears is displayed – an ICE match.
It points to the same TM entry as the Leveraged match, because it originates from the same TM record. You must have confirmed This can happen if the Linguist confirms the segment and added adds context to the very same TM entry, according to your the global TM settings:
...
The TM entry has thus therefore become an ICE match, so it no longer qualifies as a valid Leveraged match. Therefore, it must get a proper warning in its metadata For this reason, the warning described above is added to the metadata for this TM match, in XTM Workbench, and the ICE match must appear 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 revolves around involves Leveraged and ICE matches. This time you also receive : once again, a Leveraged match populated is inserted during project analysis. Then, you create a new project with exactly the same source file is created, and this project also gets the same Leveraged match . You accept 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 your the global TM settings:
...
You also have the following option 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 come back return to the first project and open XTM Workbench in the edit mode. A new ICE match appearsis displayed. Since there is an ICE match, the said Leveraged match can no longer be returned , so, once again, it gets a proper warningthe 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 one some way or another, a proper suitable message will be displayed in its metadata, stating exactly that the TM was modifiedmatch 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 which was that has been added additionally to the project.
...
The root cause for such a message to appear in the first place be displayed is that you the Project manager must have removed the said additional customer from the project at one 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 which that had some tags right after the project creation. Once the project is has been created, you the Project manager then add adds a TM penalty profile to the projectit, 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 will get a proper warning.