Feature Request

Add to the task overview KPI window:

• Average TQE after pre-translation
• Average TQE at the end of a workflow step (analog to levenshtein in a workflowstep regarding the logic)
• Average TQE at the moment (so in the current status of all tasks in the current filtering)

Open question: how to treat NULL qualityScore?

two possible semantics:

• NULL means "no TQE available", so exclude from AVG
• NULL means "not evaluated yet", and affected segment count should still include the segment, but TQE KPI should average only evaluated segments

Testing

Use 

t5 statistics:sqlite:init --re-create --aggregate

to fill statistics on existing tasks. 

Use

t5 dev:fake-tqe TASKID

to calculate faked TQE values for a task ID. 

Important: The faker calculates as TQE the length % between source and target. So if target is not changed in length, TQE will be the same on re-run. By changing the target length in different steps different TQEs per step can be produced.