Multi Review Compare Workflow Steps (MRC-steps)

In Multi Review Compare Steps (MRC-Steps) of a workflow, the previous workflow step is done not only by 1 proofreader, but by 2 proofreader simultaneously and indepently from each other.

• The proofreader who does the MRC-step gets presented a special interface for each segment, which had been changed by one or 2 of the previous proofreaders.
• This interface will be placed inside the segment grid at the normal editing position of a segment.
• The segment is editable in the standard way, but it does not contain the changes of any of the previous proofreaders. That means, that the user can edit the segment directly, or choose one of the MRC-variants. This applies to all columns, also to the source column if editable.
• Instead below the editable segment the changed segment-variants of one or both previous proofreaders are shown.
• In these segment-variants the changes are shown with change marks (see corresponding section of this Jira-story). The segment-variants are not editable, but clickable. This is shown by a nice mouse over effect. A click on the segment accepts the corresponding segment-variant and adopts its content to the editable segment field. If the same segment is opened later again, the chosen variant should be highlighted by comparing the "last edit user" value. If both variants were made by the same user, which is very unusual, nothing is highlighted.
• For MRC-segments, who have variants changed by the previous proofreaders, a new translate5 autostatus is introduced: "MRC-variants". For these segments this is the initial autostatus at the beginning of a MRC-step. Same is true for the workflow-step filterable column
  • The autostate “MRC-variants” is distilled and set only for the third alternate column (the target MRC column) on the step transition from proofreading step to MRC-step. Since the MRC step is responsible for the setting of the "MRC-variants", this autostatus change must be run just before starting the MRC-step.
• a user who is assigned to a MRC-step will get 2 independent notification emails of the 2 previous parallel working users of the workflow at the time each of them finishes its workflow with 2 independent lists of changed segments.
  • since the count of users involved in the first proofreading step is flexible, the last notification mail should also contain in body and subject the notice that this was the last user, and the notified user can start now to work.

• regarding document-wide and task-wide QM: on MRC-steps (see below) and all steps following a MRC-step, the QM criteria of all previous users from all branches which connect to each other in the MRC-step are shown in the table which shows the previously entered QM data.

• for history entries, which originate from MRC-workflow-steps: the previous revisions (which technically originate from different target alternatives) will be shown in the current target alternative in the segment history.
  • They will be marked as originating from different branches in the workflow to show.
  • This shows, that they are not revisions from each other.
  • Their change markers will not point to the previous revision in the change history (as normally) but to the previous revision which originated from the same branch.