Hi Bobbie,

It is a very interesting topic. Since it has been a question for me too somehow, I have just done a small test as below.
- Creating one entry with 3 terms in French (one-to-three)
- Creating three entries for each pair (one-to-one)

As the screenshot shows, there is no big different on BWB.

However in Studio, it looks different as below.

Either way, the term recognition could work correctly. So I think there is no big difference in those two styles so far, but some considerations as I wrote below.
When I tried to create the three entries in one-to-one style, I was prompted by a warning by WorldServer as:
    This term has previously been proposed: associate(Approved)
Because of this warning, I can assume WorldServer is expecting terms are created in one-to-multi style.

Another consideration is, when you work with Excel files for the terms by exporting and importing.
If you are collecting new terms in your local Excel file, and you import it to WorldServer sometimes, we should carefully determine which style is the best.
If you export one-to-multi style in "Delimited File: Simple Format", it will be a CSV as below, that means you need to create your Excel in a same manner.

For one-to-one style, it will be:

So I think one-to-one style might be handy for us, when we need to think about import/export.

Of course, there are some other considerations like in case of using attributes, TD Groups, etc.

Best,
Taiki

Hello Taiki.

Thank you for your very thorough analysis.  You are absolutely correct that there are issues with the export functionality. I tested the one-to-many scenario, exporting as a Delimited file and a CSV file.  The Delimited format did not export any of the translations. The CSV format exported only the first translation; omitting the other two translations.

Nevertheless, as you point out, there is an issue with the one-to-one scenario during input, where WorldServer is indicating that multiple entries for the source term exist -- message:  "This term has previously been proposed: associate(Approved)". Therefore, the best format I think is the one-to-many scenario as:  

This will solve the input part of this issue however, I still need to research the best method to export so that all translations for a source term are exported correctly.

Hello Taiki.

Thank you for your very thorough analysis.  You are absolutely correct that there are issues with the export functionality. I tested the one-to-many scenario, exporting as a Delimited file and a CSV file.  The Delimited format did not export any of the translations. The CSV format exported only the first translation; omitting the other two translations.

Nevertheless, as you point out, there is an issue with the one-to-one scenario during input, where WorldServer is indicating that multiple entries for the source term exist -- message:  "This term has previously been proposed: associate(Approved)". Therefore, the best format I think is the one-to-many scenario as:  

This will solve the input part of this issue however, I still need to research the best method to export so that all translations for a source term are exported correctly.