Hi Ineke,

It should work in MT 2014 as well.  Maybe try reorganizing your termbase first?  Perhaps something was lost during the upgrade?

Another way that might be interesting for you is to export to Excel using the Glossary Converter and then use excel to easily remove duplicates and convert back again afterwards.  How easy this will be depends mostly on the complexity of your termbase but the Glossary Converter is an excellent tool that everyone should have in their armoury:

When importing, I do not get the option to synchronise on English. Where can I find it?
I did export the file on the English field.

Does this help?

Unknown said:

For starters, it worked with the termbase I created for this.

Good start ;-)

Unknown said:

So when creating a new termbase, I have to create a new import model again. Copying it to another termbase did not seem possible, is that correct?

No that's not correct.  You can save the definition to a file and then load it into any termbase you like:

Unknown said:

This option should automatically be possible for every import action.

I guess... but the idea here is that users can create different import export models for themselves and depending on who they are sharing it with they just select the appropriate one.  This is far better than having to work through the options every time they do it.  As a translator you won't do this very often and I can see your view.  As a terminologist maintaining a termbase for many uses you wouldntt be very happy with that.

I can't comment on 5.1... can't even remember what it looked like!!

Regards

Paul

This is what 5.1 looked like, when I chose Import. Then immediately I got all the options available.
I understand that from the point of view of database maintenance it is nice to have a lot of programmable functions, but for freelance translators who work with the program every day, in my view it is a nuisance that simple options like this one that were instantly available are now hidden, and demand an extensive study of the program to be understood.

It is one of the reasons why I started to really hate upgrading any program: always there will be things I liked that have disappeared or hidden, despite any new features which I might or might not have missed in the past.

For instance, on a new laptop I installed W10, and for the live of me, I cannot find the simple command box in which I can type: msconfig
Why do program makers have to change the way a program looks so often?
I do not like the ribbon in Word or Trados either: it only means more work: things I could do with one mouse click now often need two mouse clicks. Why?
It worked fine, and except for the fact that it might look prettier, it did not improve the functionality. On the contrary. I used to be able to create my own customized tool bars, and now I can only use one. I used to be able to create icons for functions on these tool bars, now I cannot do that anymore.
So in my view, these days upgrades too often feel like downgrades.

By now, the import of the three files in the new file with the new import definition which makes the import synchronize on the index field, has finished. And all duplicates are gone.
From the log file of the import of the worst file (02):

Total entries processed: 37846
Total entries added: 5205
Total entries merged: 32641
Total entries omitted: 0
Total entries written to the output file: 0

So no need to use the Converter or Excel, it can simply be done in Multiterm itself, if you know and can find how.

Thank you, Paul, for explaining this, now my problem is really solved, with the instructrions you send in the youtube video.
I safed the import definition, since I expect I will want to use it more often.
Thank you for your patience, too.

Hi Ineke,

As you have a fairly simple structure why don't you export to Excel, get rid of the duplicates in there and then just recreate the termbase instead of trying to import with the import models?

Hi Ineke,

As you have a fairly simple structure why don't you export to Excel, get rid of the duplicates in there and then just recreate the termbase instead of trying to import with the import models?