• State Verified Answer
  • Replies 1 reply
  • Subscribers 39 subscribers
  • Views 878 views
  • Users 0 members are here
Options
Related

How to Schedule Translation Memory Updates

Burckhardt Rueffer

Can anyone explain their best options for how and when to update TMs in cloud projects?

The situation:

  • Large multi-week project for our client, let's call it Project A.
  • While the project is still ongoing, we receive another project from the same client - Project B.
  • Because Project B is from a different requestor within the client, we cannot add Project B to the existing Project A.
  • We obviously want to make use of translations from Project A in Project B.

According to the workflow, TM update happens in the Finalization stage. Does this mean that we would need to complete Project A before we can use its translations in Project B?

We tried a workaround by updating the files from Project A in Studio, but I am not sure that it works. It's also an awkward workaround because it would have to be done often to be in sync.

Does the Cloud TM store TUs right away when they are confirmed either in Online Editor or in Studio?
If so, are those new TUs available to other projects immediately?

Any tip is highly appreciated.
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • +1

    Hi   - Cloud TMs store TUs right away when you confirm them in Studio or Online Editor. The TM update in finalization is roughly similar to the corresponding Studio batch task for local projects - i.e. TUs are stored right away, but the final approved translations will get updated again when you reach that stage in the workflow. There is also a new capability in cloud TMs within cloud projects - you can now manage status at the TU level within the TM as well. So the TU statuses (draft, translated, translation approved etc.) are no longer only maintainable in SDLXLIFF files but also at TU level within the TM itself. This can be useful if you want to penalize TUs that are not yet approved, for instance. More information is available at RWS Documentation. That is a bit more advanced use case but perhaps good info to have down the line. Thanks, Daniel

    Daniel Brockmann
    Team Trados @ RWS

    emoji
Reply
  • +1

    Hi   - Cloud TMs store TUs right away when you confirm them in Studio or Online Editor. The TM update in finalization is roughly similar to the corresponding Studio batch task for local projects - i.e. TUs are stored right away, but the final approved translations will get updated again when you reach that stage in the workflow. There is also a new capability in cloud TMs within cloud projects - you can now manage status at the TU level within the TM as well. So the TU statuses (draft, translated, translation approved etc.) are no longer only maintainable in SDLXLIFF files but also at TU level within the TM itself. This can be useful if you want to penalize TUs that are not yet approved, for instance. More information is available at RWS Documentation. That is a bit more advanced use case but perhaps good info to have down the line. Thanks, Daniel

    Daniel Brockmann
    Team Trados @ RWS

    emoji
Children
No Data