Fuzzy Lookup: Quality versus Performance
The candidate selection process (which determines which TM matches will be returned and scored during the fuzzy match lookup) returns a number of candidates which is based on a configurable option. There are two such options. One controls the number of candidates considered during the leverage process. The other controls the number of candidates considered during the Browser Workbench and translation kit export lookup processes. By default, the two settings are not equal. The leverage option is set to return 5 matches, while the other option is set to return 20 matches.
# The maximum number of fuzzy results requested by the BWB and export code.
max_bwb_results=20and
# The maximum number of fuzzy match candidates that are returned from database
max_fuzzy_results_in_asset_lookup=5
Setting the browser workbench setting to return more candidates than the leverage process can result in the user finding a better match for a segment when looking at matches in the translation workbench as compared to the scoping information. This can be useful for your translator who wants the best possible matches available. However, this can lead to somewhat confusing situations in which the best available match found during the leverage process is different from the best match available to the translator in the workbench. In the most extreme case, a segment may be leveraged at less than a 100% match, while the workbench results may show a 100% entry. While this can be slightly confusing, any discrepancy will be in the translator's favor; the translator will always see results that are equal to or better than the leveraged score.
You should never set max_bwb_results to be lower than max_fuzzy_results_in_asset_lookup as this can result in the translator not receiving the matches that correspond to the scoping information.
If you want to ensure consistency between the leverage process (for example, scoping results) and the matches users will see in the workbenches, these two values should be set to the same value. At the same time, raising the value of the max_fuzzy_results_in_asset_lookup will slow down the leverage process. Therefore, you should be very cautious when raising this setting.