Project & job management

Custom criteria for pre-translation to set the segments as Completed

At the moment, during pre-translation, it's possible to set the segments as Completed only if they are evaluated as 100% and 101% matches. Introducing an option Set job to completed if document score is higher than criteria could include MTQE percentages as the main deciding factor.  

Example: Pretranslate document with a 100% TM threshold and apply Memsource Translate to the rest of the document. If 90% of the translation units are either from the TM or NT, or have an MTQE > 99%, and if no TU has a "no score" MTQE, then set the job to completed.

Current behavior:

Only 101% and 100% matches can be set to Completed during pre-translation.

Required behavior: 

It's possible to set custom criteria to set the segments as Completed. 

Use case: 

This could be used for Continuous Jobs, where the client uses pre-translation and push the “good enough” jobs back almost immediately. 

14

2 comments

  • Official comment

    Hi, thank you for your feedback. I have edited the example accordingly! 

  • Hi Hana, thanks for publishing my idea.  To be extra clear, the example I meant to describe would be something like this:

    Pretranslate document with a 100% TM threshold and apply Memsource Translate to the rest of the document.  If 90% of the segments in the document are either 100% or better matches from the TM, are detected to be NT,  or have an MTQE > 99%, and if no TU has a "no score" MTQE, then set the job to completed.

    The idea is that in that scenario, we would have high confidence that the output is good enough without humans in the loop and could implement what TAUS calls the Modern Translation Pipeline FAUT scenario.




    0

Please sign in to leave a comment.