Different TM leverages for same TM entry in exported WSXZ package compared to WorldServer server TM

I have exported a Task from my WorldServer project to a Studio package (WSXZ).

After opening the WorldServer package in Trados Studio, the very same TM entry displays as 100% match and coming from the WorldServer server TM (through a server connection to WorldServer) and as 97% TM match when displaying the local project TM as exported from WorldServer. Here is an example of how both TM entries could display in Trados Studio:

:

The default scoping mode for lookup TM from Trados Studio is the one set in the tm.properties files on the server where WorldServer is installed.

Open the tm.properties file and find this setting set per default:
 

#scoping_mode=worldserver9.x

Uncomment the property and set it to studio:
 

scoping_mode=studio

Save your change and restart WorldServer (Idiom Service).
Reconnect to the WorldServer (server) TM from Trados Studio. Now the entry will display as for the local Trados Studio project TM.

Also, to prevent this issue to happen for projects created manually using Project Types, make sure that the scoping mode selected in the Project Type used to create the project in WorldServer is set to Studio-aligned scoping mode and not to WorldServer 9.x:



 

Discrepancy between the default scoping mode used by SDL Trados Studio (Studio scoping mode) and the WorldServer 9.x scoping mode set per default on WorldServer for ad-hoc project or as configured in Project Types. The WorldServer 9.x scoping mode will repair the TM entry and display it as 100% while the Studio scoping mode algorhythm calculates it as fuzzy match.

Related article:

Significant discrepancy in Total Wordcount in WorldServer versus SDL Trados Studio 2017 when using the WorldServer 9x Scoping Mode