• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 190 subscribers
  • Views 1870 views
  • Users 0 members are here
Options
Related

How do I avoid importing duplicate entries into my termbase?

Felix Zimmermann

Hi there

I have just found this article: kb.sdl.com/
It says that duplicate entries can occur because the fuzzy index was not rebuilt. This is the reason for duplicate entries in my case, and a regorganisation solves it until the next Import. But having to do this extra step of doing a reorganisation after each import is time-consuming. Furthermore, these duplicates didn't use to occur earlier.

Is there a way to skip reorganisation, or to have the fuzzy index rebuilt automatically?

Thanks in advance!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Felix

    The KB article you mention states two conditions for getting duplicates and the lack of reorganization is only one of them and - in my eyes - the less probable of both.

    Importing entries into a termbase is a bit tricky in that you need to make sure that you do not get duplicates. If you import them using the default import definition, you will always get duplicates because the default import does not check for duplicates.

    In order to avoid this, you need to do an import with "Synchronize on entry" (if the file you import was exported from the same termbase) or an import with "Synchronize on term", where you tell MultiTerm what it needs to do if it finds entries to import for a term that already exists in the termbase.

    Walter
Reply
  • 0

    Felix

    The KB article you mention states two conditions for getting duplicates and the lack of reorganization is only one of them and - in my eyes - the less probable of both.

    Importing entries into a termbase is a bit tricky in that you need to make sure that you do not get duplicates. If you import them using the default import definition, you will always get duplicates because the default import does not check for duplicates.

    In order to avoid this, you need to do an import with "Synchronize on entry" (if the file you import was exported from the same termbase) or an import with "Synchronize on term", where you tell MultiTerm what it needs to do if it finds entries to import for a term that already exists in the termbase.

    Walter
Children
No Data