Hi Anna,

The first thing to make sure is that both termbases are based on the same termbase definition because otherwise you may be trying to bring in fields from your XML that are not in the termbase you are importing to.

But a simple workaround to avoid messing with import definitions might be these using the Glossary Converter from the OpenExchange:

1. Use the Glossary Converter to convert the XML to Excel
2. Clean up the Excel so it only contains the values you want (if you didn't just export the languages you want to Excel during conversion with the Glossary converter)
3. Convert the cleaned up Excel to MultiTerm XML and import that to your Termbase

or....

1. Use the Glossary Converter to convert your termbase to Excel
2. Use the Glossary Converter to convert the XML to Excel
3. Combine the Excel files in the structure you wish (remove duplicates in Excel too)
4. Use the Glossary Converter to recreate your Termbase

Depending on the content of your Termbase the second option may be the easiest, but if your Termbase is complex then the first method might be easier to just get three language fields in and nothing else.

Regards

Hi Anna and Paul 

I tried out Anna's solution to be able to split a very large termbase into smaller ones containing only a few languages:

Modified the term definition of an existing, empty termbase by deleting all indexes/languages not needed and then  imported the xml.

I found out that MT only imports the full number of entries containing terms in the selected languages if I choose the option "Allow over-complete entries" (as Anna had observed as well).

But if I do so MT will import all languages and terms contained in the XML  It seems that MT can only import and filter on the entry level.

The desired result would be a termbase containing exactly the full number of terms in the selected languages. 

As a first solution I use an XSL transformation on the XML to get rid of the unwanted languageGrp elements.

Is there a simpler solution to the desired result by using MT without having to manipulate the XML before importing it?

PS: Using the Glossary Converter (which would do the job exactly in the way I want it) is not an option in my case. 

Thank you for your help

Victor Linnemann 

Better to create a new thread as this one is already marked as complete so many users won't even see your question.  You can refer to this thread with a link if you wish.