Yulia Kovalskaya 

1. Exactness of phrase match
   • Is the entire term ("comprehensive maintenance") present as-is?
   • If yes => 100% match
   • If only components are found, Studio will attempt a fuzzy term match
2. Proximity of tokens
   • If the term is made up of multiple words, Trados checks how far apart those words are in the segment.
   • Closer = higher match score
   • Separated by multiple words or punctuation = lower score
3. Additional modifiers or interference
   • Words like “digitized” and “complex” interrupt the expected phrase, reducing confidence in the match.
4. Order of tokens
   1. If the words are out of order, it further weakens the score.

So, if I then look at some examples:

I changed the distance between "comprehensive" and "maintenance" in each one resulting in 78%, 87% and 72% matches, all based on the same single termbase entry "comprehensive maintenance".

Yulia Kovalskaya said:

First, I thought that Multiterm recognized only "comprehensive" and returned a fuzzy match from the database (even this would be a 50-60% match, definetely not 70%, in my opinion).

If it was a translation memory I'd agree... but it's not :-)

Studio attempts to infer the intent and provide useful term suggestions even if the exact match isn’t there.  In your use case (technical documentation/rail), this behaviour might be quite useful.  But equally it could be misleading if translators assume that “comprehensive” or “maintenance” are individually present in the termbase (when they're not).  So one difference I do see between 2024 and 2022 is that the match value seems to be there by default in 2024 (it wasn't in 2022 - although I didn't investigate this to see if my earlier or current default settings are at play).  Either way the match score helps flag that partial matches are being made, based on token recognition and order.

Hope that helps?

As always, thank you for answering, Paul!

As for the match value, it appears in 2024 version. My colleagues with Trados 2021/2022 do not have it and there is no such option in the Hitlist settings.

But this is not the issue. Technically, I do not know how the match calculation is performed, but let me assure you that Multiterm has never "recognized" terms separated by word/words before.

A recent example: my colleague asked me about a very common system used on the train (Juridical recording unit / Unidad de Registro Jurídico), she needed the exact, "official" term in Russian. Since I work on the TDB on a daily basis, I knew it HAD to be there, so I wondered why it did not appear in the Multiterm window.

In effect, it was not there, because the engineer used the wording "unidad jurídica", and I had only the first three options saved: 

Therefore, Multiterm had "unidad de registro jurídico", but when it came across "unidad jurídica", it was not recognized as a fuzzy match (null result). As you can see, I added this term "variation" to the database.

This is why the example I came across yesterday kind of struck me. Because it would save me recording so many "similar" wordings in the database (I really have plenty of them):

And in Russian, for example, the adjective can come before or after the noun (without any change in meaning), so I have to save both. If not, the term won´t be recognized.

So I think, some kind of update-improvement has been performed on the Multiterm search engine. But, then, I am just the final user :).

And if it works as you have explained above, then it is really great, since this may save us many manual fuzzy searches.

Best regards!

Me again, Paul:)

Something does not work. Look at this example:

We have "Passenger information system" in the TDB:

So, as far as I can understand: two of the three words (tokens) are present in the source segment, the match % is lowered to 60%, however, it is not detected by the search engine. For whatever reason. Nevertheless, "passenger" and "information" are recognized separately. 

I also selected "passenger information" in the source segment and used CTRL+ALT+F1 to perform the same search via Multiterm Widget: 

Then I have another question: how do these two options affect the search results: 

I played with them, but saw no difference...

Thanks in advance!

Yulia Kovalskaya 

ok - so you're not using 2024, so here's my 2024:

You can see I get a 75% match.

Then checking in 2022 I also get the same recognised terms:

I can't use 2021 on my laptop now so if that's what you're using you're on your own ;-)

Yulia Kovalskaya said:

Then I have another question: how do these two options affect the search results: 

I played with them, but saw no difference...

Most likely you are affect by whatever is causing you not to get a result in the first place!

But you can always use the help...

https://docs.rws.com/en-US/trados-studio-2024-1145319/terminology-recognition-settings-345706

Somehow the same version works differently:

Thank you for the link with the settings explanation!!!! Will study it!

Paul said:

Most likely you are affect by whatever is causing you not to get a result in the first place!

I am thinking about all the mergings I perform on the entries...maybe they are causing the "recognition" troubles. 

I will read the article, probably it has the answers:)

Thank you, Paul!!!

Maybe a reorganisation would help?

Paul Filkin said:

ok - so you're not using 2024, so here's my 2024:

I have just understood why you said that. Because match value was not shown in the Multiterm window of my example. 

I keep working and it has not appeared yet. I restarted Trados and it´s not there....magic...but , yes, my version is 2024. And the terminology match value comes and goes :). Randomly.

As for the reorganization. Well, I can try it, though I remeber half of the pictures disappeared after the last try :).

But, yes, ok, I will make a copy and try to reorganize.

Unknown said:

I keep working and it has not appeared yet. I restarted Trados and it´s not there....magic...but , yes, my version is 2024.

What version of MultiTerm do you have installed?

Same as Trados

Unknown said:

Same as Trados

Not sure what that means!  You should have:

Trados Studio 2024 - 18.0.2.3255

MultiTerm 2024 - 18.0.2.3266

Do you have these and no other versions of MultiTerm installed?  If you have other versions installed run a repair on the 2024 version.

True, Paul, I have two notifications on the update. Currently I have these installed:

and

Ok, then, maybe it´s the update issue....

Unknown said:

Ok, then, maybe it´s the update issue....

Maybe... maybe not.  Certainly you should update and then test before we worry about what doesn't work.

Also worth looking at where you are saving your termbases.  What's the full path?  Good to make sure it's not on a OneDrive path to avoid any synch issues that could be affecting your testing.

Unknown said:

Ok, then, maybe it´s the update issue....

Maybe... maybe not.  Certainly you should update and then test before we worry about what doesn't work.

Also worth looking at where you are saving your termbases.  What's the full path?  Good to make sure it's not on a OneDrive path to avoid any synch issues that could be affecting your testing.

OneDrive is a must now. So everything is synchronized immediately. But originally I have it on Disc C.

Ahh, since you´ve mentioned OneDrive, I will tell you another problem. My OneDrive gets full (1TB) every two months. And I have no permission for bulk operations (to delete all backup versions in one click). I can do it only one by one. You know the reason? Every time I merge, delete, add or modify an entry...with every click of mine, a Multiterm TDB backup version is created :) 

Same happens to the translation memories:

So, the first step is to update both applications. I will request for it and see how Multiterm "behaves":)

Unknown said:

Ahh, since you´ve mentioned OneDrive, I will tell you another problem. My OneDrive gets full (1TB) every two months. And I have no permission for bulk operations (to delete all backup versions in one click). I can do it only one by one. You know the reason? Every time I merge, delete, add or modify an entry...with every click of mine, a Multiterm TDB backup version is created :) 

A good example of why it's a bad idea to put Trados and MultiTerm resources on a OneDrive path.  Like many applications that use large resources and synch often they can have issues when they are living on a OneDrive path.  This isn't anything we can address... we have addressed it already with Trados Cloud... so if you wish to use the desktop environment you'd be advised to make sure your resources are not hosted on OneDrive and you just back things up the old way with a regular backup up.

You don't have to keep things on OneDrive... they can be wherever you want.

Completely agree with you, Paul! This has become clear to me even without IT-knowledge. Sometimes (when I don´t forget), I just turn the sync off during the day. In this case, if I am not mistaken, only the last available version of the resources is synchronized when on again.