Michael Schroeder 

Thanks for reporting.  We have already got this logged as our reference CRQ-34629.

Hi Paul,

has there been any movement on this?

Term verification in TS 2021:

Term verification in TS 2022 for the same project:

Michael Schroeder 

Only insofar as it's a bit more complicated because it's linked to some major changes underway with Multiterm generally in terms of how it works with Trados Studio.  I'll come back to this post when I know more.

OK, thanks for the update and for following up when the time comes, much appreciated!

 Michael Schroeder , Paul 

I just checked and could reproduce the issue, but not after I uploaded my termbase to the cloud. Is there a reason not to leave MT Desktop behind and move to the cloud?

Daniel

Hi Daniel, thanks for the additional information! Not really, just logistics. Will definitely be taking a look at this solution.

Michael Schroeder

The one painpoint I have is that images don't get transfered, so if you have illustrations in you MT termbase they won't import into the cloud termbase (at least mine did not). Apart from that it's terribly easy. I used the "manual" way, export the definition, create the cloud termbase, import the entries. But there is even a function in Studio - no clue where that is, but if you type "migrate termbase" into the tellme box, you'll see it.

The online version is not as feature-rich as the Desktop version, but it claims to have better term recognition.

Had a quick test and it works great - followed your procedure, thanks! - and none of the duplicate false postiives appear. However, terminology verification (alone) took over 20 minutes for a 12k word document. That's unfortunately prohibitive.

Michael Schroeder 

Wow, that's long. How many entries does your termbase have?

ca. 3500

For comparison, what would you expect for a termbase and project this size? To me, it seemed like every segment was being sent to the cloud for checking, and like I said it was 12k words, so not super giant but also not super small.

Michael Schroeder 

Yes, it's likely that each segment is sent individually, given that individual segments can be excluded etc. The size of the termbase might be of little relevance. As Paul and others expressed, the Studio - MultiTerm connection is undergoing a lot of changes right now, maybe this is something that could be put on a wish list – a more efficient way of data transfer for large files. For me the cloud termbases work really, really well, and I am considering switching completely. I am still waiting a bit to hear the experience other users made since switching means a bit of work getting all the images into the entries again.

Michael Schroeder 

Yes, it's likely that each segment is sent individually, given that individual segments can be excluded etc. The size of the termbase might be of little relevance. As Paul and others expressed, the Studio - MultiTerm connection is undergoing a lot of changes right now, maybe this is something that could be put on a wish list – a more efficient way of data transfer for large files. For me the cloud termbases work really, really well, and I am considering switching completely. I am still waiting a bit to hear the experience other users made since switching means a bit of work getting all the images into the entries again.