Problem

With the KPI feature the user can look at the average Levensthein distance per segment. Multiple filters can be used, even on segment basis like match rate values. This makes it complicated to interpret the returned values.

Solution

As we already need the value of "counted segments" for the average Levenshtein distance, we should give out this value, too, to that the user can see the numer affected by the current filtering.

Label: EN: Segment count for Ø

Tooltip: EN: Total number of segments for average calculation of Post-editing time and Levenshtein distance

Add below all KPIs an additional info:

Number of evaluated segments in current filtering: 

And add number.