Export of graphics in MultiTerm requires naming convention

Hello,

I have recently noticed that if 2 graphics have the same name in the termbase, they overwrite during export.

As a result, one of the images is lost and the image that overwrote the other is used for both term entries during the rebuilt of the termbase.

For example: let's say that under the entry "car" you have a picture of a car named "capture.jpg" (because you took a screenshot and were too lazy to rename it) and that under the entry "bicycle" you have a picture of a bicycle named "capture.jpg" (because you took a screenshot and were again too lazy to rename it). Since they were uploaded from a different location on your computer and/or uploaded under a different term in any cases, each image will appear correctly were it should be, although they have the same name. Yet, if you need to export your termbase, during the export, the graphics will be exported and stored in the "media_" folder next to your XML file. When exported, "capture.jpg"-car will overwrite "capture.jpg"-bicycle because they are exported to the same folder and have the same name. When you re-import the data, the entry "bicycle" will call the media file "capture.jpg" but there will be only one left, the car. So it will import a wrong photo. The entry "car" will also import the media "capture.jpg", but in this case it will be the only one and correct. In conclusion, the same image will be uploaded in two entries, and one of your image will be lost.

Now that we have noticed the problem, we do pay attention at the naming convention of the media file, but I just wanted to know if it was an known issue and if not, bring it to your attention.

By the way, we're using MultiTerm 2014 SP1, so I may be bringing up an outdated issue, solved in later releases.

Kind regards,
Audrey

  • Hi Audrey,

    This is most likely a known limitation and occurs because images are all dumped into one folder. Ideally if images are duplicated then MultiTerm should rename them... but then they might be intentionally the same. I think even then it would be ok to rename but it might make the work of the terminologist harder if the images were coming from another source.

    Perhaps can comment on this, but I think it's more likely this is just how it works and you need to ensure image names are unique unless they actually the same.

    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