• Replies 4 replies
  • Subscribers 46 subscribers
  • Views 1583 views
  • Users 0 members are here
Options
Related

How to extract values from old field-templates in Groupshare 2015 in order to load them automatically in field-templates in Groupshare 2017

Martha Ebermann

Hello to all,

Does anybody have a procedure or a good idea how to do this without filling in all values manually (my lists are huge......:-()

 

Thanks in advance for your advice.

Best regards

Martha Ebermann
Rate translation
×
Suggest better translation
×
  • Hi Martha,

    Unfortunately right now there is no option to easily do this in the user interface, because if you upgrade from 2015 to 2017 we automatically preserve this information as part of the upgrade installation.

    Maybe you can create an Idea so others can vote on it and we might introduce an import option in the future: community.sdl.com/.../studio-groupshare-ideas

    Thanks,
    Luis

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

  • in reply to Luis Lopes
    Hello Luis,
    thank you for your answer, which I just got also from the support. Unfortunately the migration 2015 2017 didn't go smoothly: when the guy from SDL was trying to upgrade the old structure from 2015 the containers came without the TMs they where supposed to contain, therefore I have to create now the complete structure from scratch in order to get the existing information into Groupshare 2017. The guy from SDL had about 12 hours and he could get over the TMS nor make work the SSL connection. Only Localhost is working. It's really a nightmare.
    And the import des tmx via the Groupshare interface doesn't work correctly. And as they are no more background tasks visible you can't even see how your import etc. is doing. Do you think, these facts are user-friendly and a progress in Groupsahre 2017.
    I would like you to report all this to whom it concerns.
    Thanks a lot for your help
    Best regards
    Martha Ebermann
  • in reply to Martha Ebermann
    Hi Martha,

    I think the appropriate thing to do here is take it up with whoever did the upgrade for you. I'm sure nobody would leave this unfinished or in an unfit state to work. Can you drop me an email at pfilkin@sdl.com so I know who worked on this for you and I'll take this up with the team responsible.

    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

  • As discussed (putting it here for reference):

    Workaround: Use TM Import/Export

    1. Link the existing field template to a small translation memory
    2. Export the translation memory to TMX
    - If the TM is empty, run export via Trados. If the TM has at least one TU, this can be done via the GS web interface.
    3. Create a translation memory on the second GroupShare server. Do not link a field template.
    4. Import the TMX file from step 2 into this TM
    - Use the option Unknown Fields: Add to Translation Memory
    5. Export a field template from the TM
    - GroupShare 2017, on website: Select TM > Export > Fields


    The details can be tricky though if changes to the field structure are planned.