Hi Eva,

I discussed this with the developer of the Glossary Converter and this is not possible the way you are doing it.  the separator you are using is for term synonyms and not for fields unless they map to the terms.  So multiple fields for a single term won't work, they just get merged into one when you go from Termbase to Excel, and the other way around you'll lose the fields values after the first one because there are no terms to associate them with.

So the only way to handle this is as Ali suggested and use different field names like this for example:

Then you'll get this:

Apparently trying to do what you want with the same field name was far too complicated because you have to start deciding what to do when there is only one term, or maybe more terms than fields and perhaps some field values apply to only certain terms... hopefully you can see the problems here?

Regards

Paul

Hi Eva Repolusk-Stoppel,

I have attached an example of what you can do and what it looks like.  Probably not too helpful but you never know.

example.zip

Maybe this will help you to explain in more detail what you need here and perhaps we can find ways to be more creative.

Regards

Paul

Hi Eva Repolusk-Stoppel,

Unknown said:

However, I have my misgiving about the (same) source popping up in different fields. Offhand, I feel that will rob me of a lot of search and filtering power.

That's true to some extent, although you can construct filters using multiple fields.  It is quite a tricky thing that you are attempting to do and it will work if you manually enter into a termbase.  It's really the import export scenario where things start to get a little tricky.

One possible solution for you if you can find a reliable tool that supports editing of XML is to manually create the sort of structure you would like with a few entries in MultiTerm... like this perhaps:

https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/160/Manually-created.sdltb

Then export to MultiTerm XML.  This format actually retains the structure you want perfectly.  So if you can find a way to edit the XML and even extend it to suit your needs, then all you would have to do is import the XML into a MultiTerm Termbase based on the definition you wanted... perhaps like the one above.

I had a little play using Excel for this but the format is not particularly friendly and you would probably have to duplicate a lot of entries to get the structure you needed.  But possible.

I reckon Excelling MultiTerm might be a useful tool for this.  I have not tried it with this example but there is a free trial and maybe the expense of the software would be worth it if you do these kind of things often.

Regards

Paul