Deletion of multiple entries

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?

  • Hi Ineke,

    Probably it's me being dumb but I'm struggling to follow you a bit. Presumably you meant TBX and not TMX, and SDLTB instead of TM?

    Can you tell me a few of the terms that are being duplicated and I can focus on these?

    Thank you

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Sorry, all those abbreviations... and I am working against the clock, so I do not have much time right now.
    I uploaded a few new files, and left the original databases in dropbox too.
    I have uploaded the export of the 03 file with the filter 'contains synonyms' and the complete export (03a).
    I have uploaded the 2016 database, with the imported 03 files, so only the synonym containing entries are in there.

    Hope this helps.
    I do not have any more time today, so if you have further questions, they will have to wait until tomorrow or the day after, I have to concentrate on my deadline now.
  • Hi Ineke,

    I think, when you have more time, we need to go through this together. I have looked at your list of duplicates and I don't have any of these duplicated in the file I sent you. I also tried to replicate what you did and when I imported the same file over the top of the termbase synchronising on English I still don't get any duplicates.

    This is a tricky one, but such an important feature that I don't think there is a glaring problem with the software because we would certainly know about it already.

    Let me know when you have more time and we can work through this together so that I can see exactly what the problem is and where it may be caused.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 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.

  • Most likely you are not creating your own import model, rather you are relying on the defaults. Not a good idea.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • When creating an import model from scratch, I still do not get the option to synchronize on index field, which was the setting that did the trick excellently in MT 5.1.
    So if this option is available while importing, please tell me, where is it hidden?
  • Does this help?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Thank you for creating this for me, Paul. I couldn't help myself, and just tried it.
    For starters, it worked with the termbase I created for this.
    But... the new definition is only available in that termbase, not for all termbases.
    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?

    And next to that, in my view, it is rather strange that one has to do a simple task this way, to have the option: import on index field and choose the index field, as was possible in MT 5.1
    This option should automatically be possible for every import action.
    When I see Import/Export in the main menu, then why should I think of going to termbase management to make an import model?
    The option should be available in the import/export menu, and it should be possible to create an import model that can be picked for every database, not only for the current one.

    I am currently importing my other databases too, and I will let you know if this option of creating a new import model for a new termbase did the trick. I do hope so.
  • 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

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 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.