Importing TMXs from file-based TMs into GS 2014

Dear all,

I am in the process of migrating data from file-based to server-based TMs. Mostly, this is done by upgrading the TMs individually to server format. However, for certain TMs (where we had separate file-based A > B and B > A language pairs and we want to bring both language directions into the same server TM), this involves exporting to TMX and then reimporting via the Groupshare console. or alternatively via the Studio TM dialogue, into the server TM created previously by migrating/upgrading one of the language pairs to the server.

Hope all that is clear!

On import, we tried selecting the "Add fields to TM" option. In this case, I had anticipated the behaviour would be to import all of the TUs and all of the fileds (where these fields differed from the server TM). However, the effective behaviour is that the import fails entirely (i.e., no TUs are imported at all, all TUs are recorded as "errors"; no additional fields are created in the TM).

We then attempted to import the TMXs by selecting the "Ignore" fields option. The anticipated behaviour was that all TUs would be imported and any fields that corresponded to the original server TM would also be imported, but that any fields that differed would be ignored. However, the effective behaviour is that all of the TUs import, but that no fields at all are imported (even where they are the same as the host server TM.

Clearly we are doing something wrong - can anyone give me a pointer?

Thanks!

 

 

 

Parents Reply
  • Hi Luis,

    Thanks for your suggestion.

    While we did not solve the actual puzzle, we did ascertain that unlinking the TMs from the Field Templates we had set up enable the import of TMXs.

    It is not however immediately obvious to me why linking the TMs to Field Templates would have this effect, so would welcome your thoughts.

    Regards, James
Children
  • Hi James,

    Ah, this explains it :)

    The idea with Field Templates is that they are the "master" which is why Fields won't get added by import in that case. As you can have permissions on Field Templates, you want the Field Templates to be centrally managed and not allow every user to modify them.


    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

  • Luis,

    Thanks. Yes, that much I appreciate.

    What was strange was that we could not add data to fields existing in the template.

    Let's say you had in the template a numerical field for "Year", we could not add this data without unlinking the template.

    Applying the template did give us the fields. But if the templates cannot remain linked (so that you can make centralised changes to the fields), what is the purpose of the link function at all?

    Best,

    James