Background

OpenTM2 saves each segment pair separately to a TM, as long as the context is NOT the same (context: filename + segmentNr).

This makes sense regarding the internal DB structure of openTM2, since this is its way to save different attributes for segments in the OpenTM2 internal DB format.

Yet in the interface this gets very annoying in the long run for users, as multiple 103-100%matches are shown for the same TM.

Implementation

On level of the openTM2 resource combine all matches for a segment to one match with

• match rate >= 100% 
• the same target

Take the highest match rate as match rate.

Take the target and the attribut values of the match with the highest match rate.

Except for documentName and documentShortName: Merge the values of those matches to one value, separated by "; "

Implement a opentm2 specific config switch that decides, if for 100%-Matches that differ in the target multiple matches are shown or not shown. If they are not shown, the target of the match with the highest match rate is shown. If the match rate is the same, the match with the newest change date is shown.