"No results available" in Term Recognition window even though the entries exist in the termbase and I can see them when I perform a termbase search

Question

Im running SDL Trados Studio 2019 SR2 15.2.7.2849 and SDL Multiterm 2019 15.0.6.56482, both u`pdated to the latest versions 
 For example in Segment 146 term "Wasserfilter" is not displayed in the term recognition window:

But if I search "Wasserfilter" the termbase search window shows the entry:

How can I solve this problem?

Alison Field · Accepted Answer

Hi Samanta Ingrid Schneider , John Fry , ADOLFO BENEYTO , 
 As a starting point, if you open the termbase in MultiTerm, click on 'Termbase Management' then on 'Reorganize', you might find this problem will be eliminated, see below... 
 
 Then click OK: 
 
 Click 'Next': 
 
 Then 'Next': 
 
 Then 'Finish': 
 
 Then click 'Close' on the Reorganize Termbase dialog, then close MultiTerm. 
 This should help... 
 All the best, 
 Ali

Alison Field · Answer

Hi Samanta Ingrid Schneider , John Fry , ADOLFO BENEYTO , 
 If that procedure doesn't solve the problem, you may need to run a Windows Repair of Studio and MultiTerm, as described here: 
 Repairing your installation of SDL Trados Studio 
 and here: 
 Repairing your installation of SDL MultiTerm Desktop 
 The repair function in Windows is particularly useful if there's been a large OEM software update or a Windows update. 
 I hope this helps, 
 All the best, 
 Ali

Alison Field · Answer

Hi Erik Hansson 
 Are you running the latest version of Studio 2017 and the corresponding latest version of MultiTerm? 
 Have you run a Windows Repair on both Studio and the MultiTerm components via Control Panel > Programs and Features, as described here: 
 Repairing your installation of SDL Trados Studio 
 and here: 
 Repairing your installation of SDL MultiTerm Desktop 
 Did you try removing the termbase and re-adding it? 
 If you've done all of the above, you could try creating a new project and adding all the components to it. You can add the sdlxliff file/s and process the project as 'Analyse Only'. I always do this if I have a problematic project and it usually solves whatever problems I'm having. 
 If none of this works, please create a NEW thread describing your problem in detail and how it occurred then someone at SDL will be able to give you a case number (if they still support Studio 2017, which I think they do...) so that someone in Support can link up to your computer and take a look at what is happening. 
 All the best, 
 Ali

Paul Filkin · Answer

Please be careful with your content. The solution suggested by Ali did work so there was no need for your post at all, and you are verging on too much self promotion in here which will be frowned upon and does raise complaints. It's absolutely no problem to share your solution if it will help solve a particular problem. But that isn't the case here for at least the following reasons: 
 
 Tb-Scout isn't free - just noting this as you have not mentioned it 
 Tb-Scout isn't integrated with Studio so isn't a solution to this users problem anyway 
 better alternatives to work interactively that might be worth investigating would be these for example:
 
 TermExcelerator - use Excel as your termbase if you just have simple glossaries and get term recognition in Studio - FREE https://appstore.sdl.com/language/app/termexcelerator/534/ 
 RyS Termbase & Translation Assembler - uses another kind of database capable of handling millions of terms and is very fast, also gets you term recognition in Studio - PAID https://appstore.sdl.com/language/app/rys-termbase-translation-assembler/766/

So one free and one paid. Might be worth investigating. 
 It might also be worth looking at Language Cloud for Trados Studio 2019, or SDL Trados Live Essentials for Trados Studio 2021, where you have a cloud based terminology solution at your disposal and this is also interesting. 
 But having said that... MultiTerm isn't that bad. Definitely rough around the edges but quite flexible and good enough for the majority of users once you get used to its quirks. Can always be improved however.

Alison Field · Answer

Jonathan Haerinck 
 Hi Jonathan, 
 I wouldn't expect term verification to pick up a two-word source term where the termbase only has a single word. Also, I'd never go as low as 45% Minum match value (under Terminology Verifier > Verification Settings) because that would trigger a whole lot of unrequired false positives, because that figure applies to Source and Target terms. 
 If, however, you are referring to the Termbase Search Settings, i.e. the settings used when searching for source terms as you translate, then this match value can be lower and I find 70% usually finds everything I need except when the source term is split in to two words. 
 It would be good if you could create a new thread giving precise details of what you're flagging up as an issue, as I'm not sure here. Also I've just noticed how old this post is, over 4 years. 
 That way, someone from RWS (I'm just a Studio user, not an RWS employee) such as Paul Filkin can look at the issues you're describing and help you achieve greater accuracy in term recognition, etc. 
 All the best, 
 Ali

Alison Field · Answer

Michael Beijer said: Use a CAT tool that works. 
 I do. Up to date and properly maintained, Trados Studio and MultiTerm together work very well indeed, and I do rely heavily on terminology. However, Michael Beijer , if you start a new thread (this one is over 4 years old) and describe precisely what your problem is, giving steps to produce your problem and which versions of both Studio and MultiTerm you use, someone from Trados Help will be able to help you achieve what you need from the products. 
 All the best, 
 Ali

Alison Field · Answer

Hi ADOLFO BENEYTO , 
 As far as I am aware, the 'Reorganize' function should not change any termbase settings. It smooths the data so it runs more efficiently, e.g. by removing blank numbers left by deleted entries. 
 All the best, 
 Ali

Former Member · Answer

I definitely think that this a clear and present issue (existing terms not showing in "term recognition" in Studio 2021, 2019) is simply a programming issue in Studio. Your termbases are most likely in good shape. I think you need not "reorganize" or do anything with your termbases. That is simply a waste of time. On related topics, I am certain that SDL Studio and SDL MultiTerm have limited capabilities to deal with SDL termbases, for instance, searching a termbase is usually a slow and not always fruitful process. That is the reason why, of necessity, I created Tb-Scout v2.0 (version 1.0 was released back in 2017). I did not just complaint, I created an effective and practical solution (that is my style of work, in general): https://tbscout20.translationist.com/ . Try this, just one of the many evidences I have to my claim. Open SDL MultiTerm Desktop, open a termbase, one with, say, 30,000 terms, run an "Advanced Search" and look for duplicates. SDL MultiTerm Desktop may take minutes to complete the task and then finally show a crammed list, whereas with Tb-Scout v2.0 it will only take a few seconds (seconds!) and will provide you with a neat and clickable list that will land on that term directly in SDL MultiTerm Desktop.

Trados Studio > 3. MultiTerm

"No results available" in Term Recognition window even though the entries exist in the termbase and I can see them when I perform a termbase search

Top Replies