SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
In importing my MT 5.1 files into new MT Studio databases somehow quite a number of entries were duplicated. Sometimes they even appear 12 times in my database. Since my MT database is rather extensive, trying to fix this manually would take days.In MT 5.1 it was very simple: just synchronize on index field, and double entries were combined.Why doesn't this work in MT 2014?
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:
I am sorry, I was too early in assuming all went well. Now it seems a number of entries are missing in the new file, that were present in the old files. So I started using my old files again. I tried to import the three databases myself into a new database, after performing an export, and now I discovered the problem of the multiplication: when the source contains multiple synonyms, which is often the case in my database, they are duplicated after an export and a new import. Seems to me this would be an error in MT. This problem was not present in MT 5.1. And I do assume MT will not forbid us to have entries with multiple synonyms? So I thought, perhaps I should try the filter: source contains synonyms, but then only the entries with multiple synonyms are imported, and the ones with only one source term are skipped. But here once again: the imported entries were multiplied as many times as there were synonyms in the source entry. So this will make it completely impossible to export a database that contains synonyms into a new database without multiplying the entries that contain synonyms, and who would want that? Is SDL aware of this problem?
Hi Ineke, Can you create an excel file (or termbase whichever is easier for you) with one or two entries in it and multiple synonyms to explain the problem and I'll take a look. If we can reproduce the problem with one or two entries it'll be much easier and faster to solve. Thanks Paul
Hi Paul, of the files I already sent you, the 03 file does not contain many entries. I tried it with that one, and the problem was immediately visible. I exported the 03 file to a tmx file, created a new TM on basis of the 01 file, and then imported the 03 export file in it. This was done really quickly, and when browsing the termbase, I immediately noticed the duplicate entries. Since I was sure there were no duplicate entries in the 03 file (since I had not imported anything into it, I had only filled it with new terms while working), I had a look at such a duplicated entry and noticed it contained two synonums. Other entries were duplicated more than once, while I was also sure I only imported the file once.So I imagined it might have to do with synonyms. When I checked this, I noticed the number of duplicate entries was similar to the number of synonyms in the source.
Hence my conclusion: Multiterm 2014 treats each synonym as a new entry, without giving me the option not to do so. Does this help enough? And if not, I guess it would be very easy to replicate this yourself. I use SDL Trados 2014. This is a big hickup in my view, which has already cost me far too much time.
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?
Ineke Kuiper said:For starters, it worked with the termbase I created for this.
Good start ;-)
Ineke Kuiper 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:
Ineke Kuiper 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!!
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: msconfigWhy 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: 37846Total entries added: 5205Total entries merged: 32641Total entries omitted: 0Total entries written to the output file: 0So 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.
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?