Term recognition window - only show allowed terms

Question

I'm sorry but I can't seem to find the answer to this one in the RWS documentation/on Google. 
 
 If we have a long list of forbidden terms and we only want to see the good ones in Studio when translating, how can we do this? 
 I know how to make descriptive fields visible for terms, but this is not what I'm looking for. 
 
 THANK YOU!

Lydia Simplicio · Answer

Tanja Hampf I have a slightly different view on things. I feel a termbase should showcase both approved and forbidden terms. 
 If you remove forbidden terms out of your termbase entirely as Michael Schroeder suggests, then how do you ensure users didnt start introducing terms interactivity/systematically mid translation that would have been classified as forbidden? Is this an exercise post translation?? Studio does have the capability of putting a term QA on a term based on term status - so if the forbidden term does get used in error it will be picked up. By going into the HitList settings you can also specify for more detail to come through as part of term recognition. As seen below I have 2 terms showing, but one is clearly marked forbidden while the other is approved 
 Defining your Termbase hitlist settings - is possible even for Language Cloud Termbases. And whats nice is you can set your ideal preferences. Save it as a template which others users can then implement. If you do continue with the notion of your term lists only contain approved terms, then I suspect you will become very dependent on the other term QA setting known as: Check for possible non usage of target terms. As seen in the screen prints above. 
 Also noteworthy information: Depending on which technical solution you are using other options to help manager user settings could be done. Example with GroupShare you can set Filters, Layouts and even use Termbase classifications at user group level to ensure users see the right level of information. Making the idea of 1 complete termbase even more ideal - depending on the level of detail you need. What this means in practice. By configuration, users as part of Group A automatically gets to see all terms while users as part of Group B only sees approved terms. I always loved this concept because I could set a group of users up (Subject Matter Experts) who only work on pending approved terms and in this way they dont get overwhelmed with large term lists. And managing such detail as part of configuration makes it easier to manage and puts less dependency on the users themselves I hope that some of this helps you explore whats best for you Lyds

Trados Studio > 2. Trados Studio

Term recognition window - only show allowed terms