How can several translators share a project (work simultaneously on same server-based TM/textbase) from Studio with a project received via Multitrans plugin?

Scenario: organization with Multitrans. Translators have Trados Studio and receive their tasks via the SDL Multitrans Plugin. For projects where the translators work alone, no problem. However, very often several translators have to share a large or urgent project. Each translator receives a different Multitrans task with their assigned portion of the text to translate. Translators want to work simultaneously with the same TM so that they can leverage each other work and ensure consistency. As of now, the only solution offered to translators is to use the Multitrans Web editor translating agent with the same Team Server translation memory. This is far from ideal since translators are used to and want to use the much more advanced and powerful Studio, which also allows them to use their own personal local translation memories. Is there any way for these translators to connect from Studio to a Team Server translation memory via the Multitrans Plugin? The documentation available on the plugin says: "Your providers must have at least read access to your MultiTransTextBases, Team Server TMs and TermBases to connect successfully to them from Trados Studio.... For any necessary Team Server TMs, the minimum access right is Can retrieve TM matches". If that is the minimum, is there a higher or maximum access right that would allow a translator to add/update the TM instantaneously? If so, I assume that would solve the problem, wouldn´t it? If not, is this a functionality SDL is going to add in the near future? If not, is there any other way for the translators in this situation to translate shared projects using Studio where they can update the same translation memory in real time to take full advantage of Studio functionalities? Would Groupshare be an option in this case? If so, how would it work? Can you combine SDL Studio licences with Groupshare with Multitrans without technical on compatibility problems? What about the new SDL Trados Live or any other function in Studio 2021?  

In the same vein, with regards to Termbases. In this same scenario, apparently translators are not able to add terms on the go from within Studio to the Multitrans server termbase associated to their project (received via Multitrans). They need to use Multitrans Termbase Web Collaborator. The Multitrans Plugin documentation says "For any necessary TermBases, the minimum access right is Read." So again, what other access are there? Is it technically possible for a translator in this situation to add (or update) terms on the Multitrans termbase directly from within Studio if given the appropriate access rights? If not, is that a functionality that SDL is exploring in the near future? 

Any help on this matter would be much appreciated.  

Parents
  • The MultiTrans plugin is read only so you can't share the TM that way for read/write access.  GroupShare is an option since you will have a Studio project and can add any type of TM you have access to.  Same for termbases.

    Is it technically possible for a translator in this situation to add (or update) terms on the Multitrans termbase directly from within Studio if given the appropriate access rights? If not, is that a functionality that SDL is exploring in the near future

    The reason we don't support this now is down to limitations on the Multitrans side, but if this was ever resolved we could support it in Studio.   or  might be able to add some value to your questions.

    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 mentioned, the reason for the Read access is so you can view the TermBase terms. Additional access rights would be required if you're using the TermBase Web to add or edit terminology. This (updating terms from directly within Studio) is being considered as part of the future roadmap, however we cannot provide a timeline for this yet.

Reply
  • As mentioned, the reason for the Read access is so you can view the TermBase terms. Additional access rights would be required if you're using the TermBase Web to add or edit terminology. This (updating terms from directly within Studio) is being considered as part of the future roadmap, however we cannot provide a timeline for this yet.

Children
  • Thank you for your answers.  I have another question for you regarding the Multitrans plugin, that seems to take away some very important Studio functionnalities.  Is there any way to be able to generate the target in Studio when you receive packages via the Multitrans plugin?  It is an absolute must for the translator to be able to review the translation in its final format before delivering it to the client or to the next person in line (reviser, proofreader). And it has to be done in Studio (not through an xliff export task in Multitrans), so that he can enter any necessary corrections before returning the package (which means the translation is done and you can´t update the segments with the last corrections).  This is a huge issue.  Moreover, you cannot previsualize the translation either. Thanks. 

  • There is no way to generate the target in Studio when received via the MultiTrans plugin. The intent of the plugin is to offer an alternative to working in the MultiTrans editors (desktop or Web) however the file management including export is still controlled through MultiTrans. We have noted the request to be able to preview the files as well. We are happy to take your feedback into account for future iterations of the plugin, so it's much appreciated.