Repetitions are not correctly handled with task statistics feature

    • Type: Bug
    • Resolution: Unresolved
    • None
    • Affects Version/s: None
    • Component/s: kpi, Repetition editor
    • Critical
    • For repetitions the postediting time and levenshtein distances statistical data was not recorded.

      Problem

      Currently

      • Levenshtein distance is not set in statistics for segments, that are changed by repetition editor.
      • For post-editing time it is unclear, how it is set

      Solution

      If segments are changed by (automatic or manually triggered) repetition editor, then

      • Levenshtein distance should be set for all changed repetitions to the same value as master segment
      • Post-editing time should be set in dependency of how repetitions are processed: 
        • The complete post-editing time will always be recorded for the master segment. 
        • No Repetion Processing: Nothing saved per repetition since not changed
        • Automatic repetition processing: 0 for all changed repetitions
        • Manual repetition processing: The time the users spends in the repetition editor is recorded, divided by the amount of processed segments. The result is stored as post editing time to the repetitions.

       

            Assignee:
            Thomas Lauria
            Reporter:
            Marc Mittag [Administrator]
            Aleksandar Mitrev
            Stephan Bergmann, Sylvia Schumacher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: