Salesforce

Are fuzzy matching or partial string matching supported for terminology hits when using Multiterm Term Databases instead of native WorldServer Term Databases?

« Go Back

Information

 
TitleAre fuzzy matching or partial string matching supported for terminology hits when using Multiterm Term Databases instead of native WorldServer Term Databases?
URL Name000014109
SummaryThe Fuzzy Term searching is a function of the WorldServer Terminology tool if Multiterm Term Databases are used. It is not supported in native WorldServer Term Databases. This article provides more details.
Scope/EnvironmentWorldServer
Question
Is fuzzy matching, or partial string matching supported for terminology hits when using Multiterm Term Databases instead of native WorldServer TermBases?
To give an example: If a new source segment contains the word airport and the project TermBase contains the term entry port, there should be a match and that match should be found and visible when clicking on the TD icon in Browser Workbench. It should also be exported as part of the WSXZ package. 
Answer
The Fuzzy Term searching is a function of the WorldServer Terminology tool if Multiterm Term Databases are used. It is not supported in native WorldServer Term Databases, as explained in this article. The Fuzzy Term when using Multiterm Term Databases search applies to Browser Workbench, Online Editor or when exporting as part of a Studio package. This section of the RWS Documentation Center talks about the integration between WorldServer and GroupShare/Multiterm Term databases. This is an example of Fuzzy Match results displayed in Browser Workbench when using a Multiterm Term Database:

User-added image

Also, the WSXZ package exported from a project using a Multiterm Term Database includes a TBX file with the relevant terms (including Fuzzy Matches) and some additional files and folders that are not present in packages exported from projects that do not use Multiterm Term Databases. Here is an example of the content of such WSXZ package including a Multiterm TD:

User-added image
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by