Not Considering

WS shouldn't write unconfirmed segments to the TM

Similar to TMS, WS shouldn't write unconfirmed segments to the TM at all. Linguists leave segments unconfirmed, generally, in order to keep them from the TM for a variety of different reasons including: one-time project specific instructions, one-time ICR or other third party feedback that shouldn't be implemented in the future, etc.

Suggestion: Create a setting to let organizations choose if unconfirmed segments should be written to the TM or not.

Rebecca Herrera

  • You can put a penality on segments in a "Pending Review" status.  The infomration is here: docs.sdl.com/.../GUID-6EFE1CFC-467F-4BDE-8EE0-2F00B8DC0DED

    I am not really happy with the Live TM ability and the limited options of writing to the TM, but this at least mitigates the risk of unreviewed 100% matches applying to content as 100% match.  

  • This has come up again. It seems that when segments are not confirmed in studio and are uploaded to WS, the segment will get a status of Pending Review in the TM. However, the segment will still leverage 100% though it needs to be reviewed. If 100% matches are out of scope for review in a project, this segment will not be reviewed, though it was never completely reviewed int he initial project. This seems risky.

  • How does this segment status affect the leveraging? Will the Pending Review status make it a high fuzzy instead of a 100% match? The concern here is when 100% matches are not reviewed.

  • The WorldServer TM is unique in that it support segment statuses. A TU can be 'Pending Review' or 'Reviewed', depending on which step in the workflow the TM was updated in Live TM mode. This means that newly translated segments are available for leverage for new projects while their review is pending or in progress, potentially lowering costs. In this case, TUs with this status should be penalised so that it is clear that are unreviewed.