SDL TMS & MultiTerm Integration

Some questions regarding SDL TMS, SDL MultiTerm and integrations:

1. Is SDL MultiTerm included in SDL TMS?

2. In case it is, does it also function for the online version of SDL TMS?

3. Is there an API/SDK to integrate with both of these? Can you share some info on how it works. If it is a plugin or a web service.

Thank you

Parents
  • Hi Stefanos,

    1. SDL Multiterm Server is part of another SDL product called GroupShare. You can find more details on docs.sdl.com.

    GroupShare is made up of 3 components:

    • Multiterm Server
    • TM Server
    • Project TM

    2. TMS and the Multiterm Server part of GroupShare can function together as they have support baked in to the products to do so. If you are translating using the Online Editor with TMS you can search terms in a Multiterm termbases seamlessly.

    3. Both TMS and GroupShare now have RESTful APIs but because its already baked in to this products you would need to do anything with it just configure your TMS to connect to your Multiterm server under the menu path of Setup >Terminology.

    What Versions of TMS and Multiterm are you dealing with? 

    Thanks

    Ryan

  • First of all thank you for your answer.

    We are not into the translation business, but rather in the terminology management software business.
    We are interested in integrating our terminology management application with SDL Groupshare and TMS.
    We already have a working integration with MultiTerm and we are evaluating our options to integrate with TMS instead.
    Is this possible with the RESTful API?
    Do you think, you can provide us with a documentation and some examples?
Reply
  • First of all thank you for your answer.

    We are not into the translation business, but rather in the terminology management software business.
    We are interested in integrating our terminology management application with SDL Groupshare and TMS.
    We already have a working integration with MultiTerm and we are evaluating our options to integrate with TMS instead.
    Is this possible with the RESTful API?
    Do you think, you can provide us with a documentation and some examples?
Children
  • To view the TMS REST endpoints you can follow this structure on your server = https://{server}/api/doc.
    But I am afraid there is no endpoint for Terminology and no plans to have one either since TMS connects to Multiterm to get Terminology functionality.
    The only access to Terminology via a REST API would be with Multiterm and through the new Groupshare 2017 REST API.
  • Hi ,

    Just to add to the response from Ryan, you also have the Terminology Provider API for Studio (you would then work with your solution in Studio in a similar way to the way MultiTerm works) which might be a useful option given any translator/reviewer working with TMS/GroupShare will probably be doing it via Studio. I guess it depends on what your usecase is for such an integration?

    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

  • Thank you Paul Filkin,

    I am interested in more information about the Terminology Provider API.
    Is it a plugin or a Web Service?
    Is it possible to segment-search using an interface or does it work with database synchronization?
    Does it support two-way integration? Can the user add/edit a term to third party terminology software directly using the API?
    Is it possible to get some technical specifications, documentation and examples?

    Thank you for your time
  • Terminology Provider API for Studio enable the developer to create a plugin for Trados Studio. The API leverage the standard Trados Studio UI for the segement search and offers the ability to create a custom term viewer (displayed instead of the default MultiTerm Viewer). Also the Quick Add and Add term are working via the API.

    Technical documentation for the Trados Studio API's is available here (including the Terminology Provider API). The documentation covers a simple provider implementation. For something more complex you can have a look here. This is a Terminology Provider implementation that gives the user the ability to use excel as a terminology database (if this looks a bit unusual have a look here).

    In GS 2017 we also have a REST API for terminology stored inside the product. The documentation for this is available with the product. We also have a client library that makes things simpler in terms of consuming the REST API.

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/