Hi Maite,

By default I don't think that TMS should be adding 100% matches to the master TM that have come from a different TM. That would prevent you from maintaining the integrity of your existing TMs. There are three possibilities here:

1. Ensure that the 100% matches are confirmed before the task reaches the UpdateTM step. This could be done in one of two ways:

   a. Use the App Store link that I provided previously

   b. Request a customization from PS to ensure that 100% matches are confirmed

2. Turn off the organizational setting for "Only Update Confirmed Segments in TM" although this would add all content to the TM and I don't know whether that's desirable

3. Wait for a TMS enhancement to add an option for "Update 100% Segments in TM" which is I guess what this Idea would cover.

Regards,

David

Hi David,

The other day, I prepared some statistics for a client where we showed them where the leveraging was coming from for one of their TMS workflows, where they have a TM sequence in place, with a Master TM and other secondary TMs. In those graphs, we could see that 1/3 of the leveraging was regularly coming from a secondary TM, applied wit no penalty, in the TM sequence. This means that 1/3 of the content translated in that workflow is not being populated in the Master TM because it was recouped as 100% match from a secondary TM. With the current default settings in TMS, that content will never enter the Master TM. SHouldn't this content be populated into the master TM by default? This would only be possible if both, confirmed and 100% matched segments, are imported into the TMs after project completion.

Thank you!

Maite

Hi Maite,

In this case I think the best solution would be to engage with the PS organization to request a customization that confirms 100% matches in the file before the TM is updated in the workflow. This would be an additional workflow step that you could add in as necessary. Alternatively, have you looked in the App Store for a solution. A quick search turned up this:

appstore.sdl.com/.../

That would appear to be a much quicker way to confirm the 100% matches for the project.

Regards,

David

Thanks, David. Here are some examples and reasons why this feature would be very useful:

-Scenario: TMS account with different TMs and TM sequences. The client wants each Master TM (update TM) to contain all content translated via that TMS organization, including the leveraging coming from other TMs applied in the sequence as 100%. (Client could ask for a copy of this TM, but we do not want to give them a copy of all TMs used in the TM sequence).

-In the past, we discovered considerable loss of leverage for some clients/languages, because translators were applying local 100% matches without confirming them. The result was that the client kept paying for those segments over and over again, as they never reached the online TMs.

-When you have 40 target languages and lots of small files everyday, the admin time necessary to confirm 100% matches becomes  a considerable effort. Additionally, it is a manual step that that can be error prone.

Hi Maite,

Thanks for your idea. In order to take this further I was wondering whether you could expand on this to provide more detail around the workflow, the requirement and the use case. It's quite possible that a simple operation of confirming all 100% matches would work here.

Thanks,

David