How can we implement a double review process in Catalyst? Thread poster: Thomas Rebotier
|
|---|
We frequently work on updates of a very large project for an end client who reserves moving segments from "for review" to "validated" for their own QA, on their own time. Thus, the "for review" accumulate from update to update, and we have until now used the flags to communicate the translation status between translator and editor, our theoretical process being:
[untranslated segment] (translator translated and flags)-> [for review, flagged segment] (editor reviews, and removes th... See more We frequently work on updates of a very large project for an end client who reserves moving segments from "for review" to "validated" for their own QA, on their own time. Thus, the "for review" accumulate from update to update, and we have until now used the flags to communicate the translation status between translator and editor, our theoretical process being:
[untranslated segment] (translator translated and flags)-> [for review, flagged segment] (editor reviews, and removes the flag only when no changes)-> [for review/unflagged verified segment OR for review/flagged edited segment] (translator verifies editor's changes, finalizes and removes flag)-> [for review, unflagged, doube checked segment]
We recently realized that when the translation is interrupted in the midst of a segment, such as saving the file as when interrupted (CTRL+S) and exiting the Catalyst, the segment is moved from "untranslated" to "for review", and since this occurs before the segment is completed, the flag is not yet raised, and this incomplete segment bypasses all downstream flag-based scrutiny.
ideally, we would like to define an additional status and user roles, for example to have "untranslated", "for review", "for LQA" statusses and "translator", "reviewer" and "LQA analyst", and to have the segments follow a natural workflow where the status changes ONLY by an active decision of the corresponding user--for example the status would change only upon clicking on the right arrow or using the keyboard shortcut that moves on to the next segment. Is there a way to do this?
Even if we cannot define an additional status, is there a way to protect status change and make it so that the segment does not change status unless explicitly requested by the current user?
If we still cannot implement either above solutions, is there a simple way for untranslated segments to be automatically flagged when added by the end client (double status: untranslated AND flagged), which would not prevent accidental move to the for review status but at least would keep the segment under scrutiny?
All workflow suggestions are welcome.
[Edited at 2014-04-10 14:50 GMT] ▲ Collapse
| | | | | Feature Request | Apr 15, 2014 |
Hi Thomas,
Unfortunately, you have to flag a string manually. Furthermore, once you start typing in the string it will be automatically marked as for review unless you specify otherwise.
We currently do not have a better work process for your; however, I will log an enhancement request with development to be able to assign more statuses or at least have different coloured flags. Which should make your reviewing process a lot easier.
Thanks and regards,
... See more Hi Thomas,
Unfortunately, you have to flag a string manually. Furthermore, once you start typing in the string it will be automatically marked as for review unless you specify otherwise.
We currently do not have a better work process for your; however, I will log an enhancement request with development to be able to assign more statuses or at least have different coloured flags. Which should make your reviewing process a lot easier.
Thanks and regards,
Jette ▲ Collapse
| | | | | no auto status, and sortable colored flags, :) | Apr 24, 2014 |
Thank you Jette,
if you opt to create different color flags, please make the flag sort regroup items of the same color.
But really the issue is the automatic change of status. I also work with Trados, Wordfast Pro, WorldServer. All thes programs work logically: a segment isn't considered translated until the translator says so. There may be a variety of ways to do that, UI buttons to click on, keyboard shortcuts, etc., but the decision is always the translator's. Ther... See more Thank you Jette,
if you opt to create different color flags, please make the flag sort regroup items of the same color.
But really the issue is the automatic change of status. I also work with Trados, Wordfast Pro, WorldServer. All thes programs work logically: a segment isn't considered translated until the translator says so. There may be a variety of ways to do that, UI buttons to click on, keyboard shortcuts, etc., but the decision is always the translator's. There is no good reason whatsoever to turn a segment's status to 'translated' at the first keystroke... It's not a feature, its a bug
[Edited at 2014-04-24 14:47 GMT] ▲ Collapse
| | | | There is no moderator assigned specifically to this forum. To report site rules violations or get help, please contact site staff » How can we implement a double review process in Catalyst? | Protemos translation business management system | Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
More info » |
| | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
