• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 190 subscribers
  • Views 3464 views
  • Users 0 members are here
Options
Related

Problem with Ad Hoc entries in Multiterm-Won´t show with Normal Search even after Editing/Saving them individually

Beatriz de Vega

Hello,

I had been adding entries to Multiterm through the Editor as well as from imported glossaries (converted with Glossary Converter). I know they are in the termbase since I just made an export of them and they were all there. However, when I do a Normal Search for them I cannot find them. I just realized that there seems to be a special category of Ad Hoc entries that you can only search using a specific function for it, not just as the Normal Search. I searched all the Ad Hoc entries (and indeed they were in the termbase), Open/Edit each of them individually and Save them so that they would supposedly become regular entries. They have now disappeared from the Ad Hoc entries category but when I do a Normal Search I still cannot find them. 

So, my questions:

-Where are they now and why they wont´show up with a Normal Search?

-Isn´t there a way so that entries created through the Editor or from imported glossaries become just regular entries automatically instead of having to go through each of them individually and Edit/Save them? What´s the reason behind this separate Ad Hoc entries classification? I really do not see the point of it. Very frustrating.

-Does it mean that the only way to create regular entries that you can find with a Normal Search without the need of further operations is using Desktop Multiterm?

Thank you in advance.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Beatriz de Vega

    Hi Beatriz,

    It sounds as though your termbase has become pretty large and an error like this is quite possible with the filebased version of MultiTerm.  Have you tried the solutions in this KB article for this problem:

    If size is the issue then perhaps it's worth seeing if you can split the termbase up into smaller ones based on some attribute in your termbase?  If you just keep source and target terms only with no other information then maybe the Term Excelerator is a solution worth looking at as this can handle much larger sets of data than MultiTerm, but it is only for simple glossaries.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hello Paul,
    I knew size could be an issue (original termbase was 62000 terms and 1.99 MB) so I had already splitted it in two: 28,000 terms at 187 MB and 32000 terms at 820 MB. I created the two new smaller termbases with the exact same definition but still the slightly larger one gives me the same error when I try to reorganize it. I had seen that solution to modify Windows registry but I am just too scared to mess up something with my system and not being able to undo it. Unfortunately it´s not just terms but many languages with quite a complex structure of fields so I really need Multiterm. I think I will leave it as it is for now. Thanks for your help.