Kelly Edward

Interesting... what's the usecase for this?  Also, what's the reasoning behind deleting at the concept level?  If you have multiple synonyms for example deleting at that level seems a bit drastic:

good point, always..

Usecase came from here, specifically.
https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/41088/dedicated-term-extract-workflow

and Yes, I know, TB is quite complicated animal.
This code is a good "StartPoint" and one has to go further with its own fingers.

Regards

good point, always..

Usecase came from here, specifically.
https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/41088/dedicated-term-extract-workflow

and Yes, I know, TB is quite complicated animal.
This code is a good "StartPoint" and one has to go further with its own fingers.

Regards

Kelly Edward

I see.  So your thought was process was to copy the existing termbase, identify all the matching terms from your project and then delete what wasn't identified?  As opposed to identify matching terms and copying to a new termbase?

Not judging... only trying to understand your thought process based on that link.

I think a tool like this would be quite useful, better as a plugin so it could be added as a batch task to a project.  I have got this on our own backlog of items to look at when we have time as I think the concept of a project termbase could be quite useful.  It starts to become less important as we do more and more cloud based solutions as you don't need to send so many resources around as file, but I can imagine many users would still find this helpful, especially when working with translators who don't have great internet connectivity, or just prefer to work offline.

just like a "project TB"..