Hi Lais Lewicki 

Reading this the first thing that came to my mind was: dont do it

Before I explain let me address this point

Lais Lewicki said:

But can I use it to delete all entries in a termbase without deleting the termbase itself?

My approach which if anything may require less concentration and mouse clicks would be:

A: save termbase definition (termbase itself) then create new empty termbase 

Last point to address, you asked

Lais Lewicki said:

And can I use it to easily identify duplicated entries? 

There is a out the box command to help

But the big topic outstanding is 

Lais Lewicki said:

Multiterm provides a Batch Edit/Delete feature, but I am not completely sure how to use i

There is a correlation between custom filters and batch/edit tasks

This means you first get to "test" your batch edit by evaluating your filter, based on what you would be batch editing 

To do this, you need to go to Termbase  Management, create a custom filter.
Once done, activate it on the home ribbon. Review and adjust accordingly.
Only once you are happy do you then attempt your batch edit/delete with a bit more confidence

How to create filters can be evaluated here: https://docs.rws.com/983473/370967/multiterm-2022/creating-filters

I hope this helps

Lyds 

Hi Lais Lewicki 

Reading this the first thing that came to my mind was: dont do it

Before I explain let me address this point

Lais Lewicki said:

But can I use it to delete all entries in a termbase without deleting the termbase itself?

My approach which if anything may require less concentration and mouse clicks would be:

A: save termbase definition (termbase itself) then create new empty termbase 

Last point to address, you asked

Lais Lewicki said:

And can I use it to easily identify duplicated entries? 

There is a out the box command to help

But the big topic outstanding is 

Lais Lewicki said:

Multiterm provides a Batch Edit/Delete feature, but I am not completely sure how to use i

There is a correlation between custom filters and batch/edit tasks

This means you first get to "test" your batch edit by evaluating your filter, based on what you would be batch editing 

To do this, you need to go to Termbase  Management, create a custom filter.
Once done, activate it on the home ribbon. Review and adjust accordingly.
Only once you are happy do you then attempt your batch edit/delete with a bit more confidence

How to create filters can be evaluated here: https://docs.rws.com/983473/370967/multiterm-2022/creating-filters

I hope this helps

Lyds 

Thanks for your input, Lydia!

The search for duplicate terms works as a charm!

Here is the situation that led me to this question. My project manager created the termbase in Groushare for German and English but he imported an XML file for English and Portuguese. So what happened was that the termbase only actually imported the English half of the terms.

Then, he changed the languages of the termbase to English and Portuguese and imported the XML file again.

And my end result was duplicate entries for all terms, one with the Portuguese translation blank and the other entry with the correct Portuguese translation.

What would have been the best course of action in this case? Deleting the termbase and creating a new one, as you suggested, or can I easily delete terms without a target translation or can I maybe overwrite the terms when importing a new XML file?

Thanks for the documentation on filters!

EEK! Lais Lewicki 

I think you are in a mess now and as your termbase is still in its new phase with only 2 languages, I would advice start again.
Especially as I assume your imported XML files are still complete and accessible. 

However this experience is certainly building your product knowledge. Had there been more care when 

Lais Lewicki said:

he changed the languages of the termbase to English and Portuguese and imported the XML file again.

What should have been considered, are the import rules

Had this been done, I believe you would have done your 2 imports (1 incorrect), 2nd revised. But during the second import source terms/entries (English) would have merged and therefore not duplicated themselves.  

I have been offering support for roughly 15 years now,  and I either forget or still find things to learn

Take care

Lyds

I know what you mean about constantly finding things to learn with the Trados suite of products.

I have been using Trados Studio for about 6 years already and it constantly surprises me with "new" features (but rather just things I hadn't discovered yet).

Multiterm is something I use much less, and that I haven't explored as much!

Thanks for the tip with the Synchronization option, we usually just use the default for everything, but I'll try using the other two and I'll pass it along to my team.

You've been extremely helpful, thanks!

Very welcome Lais Lewicki