RWS Language Cloud: Termbase import process fails with error message "Your file could not be imported. Try again at a later point."

In Language Cloud Terminology, the import of an XML file into a termbase fails with the below error message:

Your file could not be imported. Try again at a later point.


 

Checking the import log file will show:

Import results:
        FAILED duplicate entry_exp tessst.xml 
                Reason: The entries were not imported because the import file could not be parsed and seems to have an invalid format or structure. 
                Source: "Validation issue at line number: 1. Issue:cvc-identity-constraint.4.1: Duplicate unique value [X,] declared for identity 
constraint "uniqueConcept" of element "mtf"."

 where X is an entry ID (concept ID).

Solution 1. Manually edit the XML file in a file editor (e.g.Notepad++) to remove the duplicate entry (concept ID) or manually provide a new concept ID

This would be the fastest solution if you have only 1 or very few duplicate entry IDs. In many cases, they are pure duplicates (exact same entry content of the same entry/term), and either removing completely  1 instance of the duplicate entry or giving it a new ID will be enough.

NOTE!
If you choose to remove the entry completely, make sure you remove it correctly. Termbase entries in an XML file are always enclosed between <conceptGrp></conceptGrp> tag pairs. When deleting the entry from the XML you need to make sure that both the starting tag <conceptGrp> and the closing tag </conceptGrp> are deleted.

If you choose to provide a new entry ID to one of the duplicate instances, make sure you provide one that does not exist in the XML already. Better to choose a high value.

Solution 2. Use Multiterm Desktop to import the XML content into a file-based termbase by using the Synchronize on entry number import definition.

Choose to Ignore, Merge or Overwrite entries with the same ID according to your preference. Once the import is ready, run a new XML export from the file-based termbase and use the resulted file for a new import in TLT.

The import log file already provides information about the root cause: the XML contains duplicate entry IDs for different entries.

Under normal circumstances, XML files with identical (duplicate) entry IDs should not exist in the first place as even file-based TB or GS TBs do not allow the creation of entries with duplicate IDs. However, this could be the result of known (e.g. CRQ-6093) or other unknown defects.

Multiterm Desktop performs this type of import and, depending on your choice, it either ignores, merges or overwrites the duplicate entry with the second instance of the same concept ID (which would be the second in the XML).

.