I am a heavy user of Multiterm Termbases and have built many rather large termbases during years.
There are some issues/bugs in Studio (and Trados?) environment:
1. This one is a nasty one. It started propably after SP2 (I'm not sure). (I have discussed this earlier, sorry about bringing this up again, but nothing seems to have been done to fix this problem)
I have many entries (at least thousands, maybe over ten thousand) that differ only by the case of the first letter (source), like:
In Photoshop terminology:
In general terminology:
FI: pois sulkeminen
FI: pois jättäminen
Now, in Studio, when translating and there is the word "exclusion" in source text, the term recognition shows only the first match it finds (In above case, only the Exclusion/Poistava entry). The case of the source text does not matter, and it does not matter if the entries are in the same termbase or different termbases. If the Exlusion/Poistava entry would be in lower case, the term recognition would show all found entries
2. This one happened also in previous versions (Studio) and in Trados if I remember right. So this is not necessarily just a Studio issue.
Every time there is a major upgrade in the software, and the termbases must be upgraded during update, the termbases (at least some of them) grow enormously.
Last time (Studio SP3) my 0,5 G termbase grew to almost 3 G !!!
The only way to "restore" normal situation is to export all entries, create a new termbase, and import those entries.
3. In Finnish the words often have different meanings depending on the context.
So, when I started to build my main termbase years ago, I started to add terms basically in this way (as they appear in dictionaries):
example: Colour the wall red
example: She tends to colour her stories
Sometime along the way (this started before Studio, if I remember right) I was not able to add identical target terms anymore like this. I wonder, if there is a setting in Multiterm that allows this again.
Although it may not seem to make any sense to add multiple identical target terms, there is at least for me. The words may have many, many meanings in Finnish, and it is much more convenient and informative to group ("sort") those meanings by context in the entry, than to add multiple contexes under the target term.
4. This is a minor one, but still...
In Studio, when I perform a termbase search in Termbase Search tab, there is no button to start the search. I can only start it by hitting Enter, and that plays the windows alarm beep or something at first, like there was something wrong in what I did.
5. This is rather a missing feature than a bug
In Studio, it would be very handy, if you could start the termbase search/fuzzy search through right-click menu after selecting the word.