Support DESK

Follow

Configuration UI - Compare Tab

Previous Article matchIT Hub Index Next Article

Compare Tab

Compare_Config.png

Phonetic Compare Options

Algorithm The phonetic algorithm used when scoring. There are five choices available: soundIT, Loose_SoundIT, Dynamic_SoundIT, Soundex, None.
(Algorithm) for first name Optionally specify a different algorithm to compare first names (‘none’ means use the same as the main Algorithm setting.
Loose threshold When the Dynamic_SoundIT algorithm is in use, this property controls the threshold at which soundIT is switched to Loose soundIT.

Fuzzy Compare Options

Algorithm The fuzzy algorithm used when scoring. There are two choices available: matchIT_Fuzzy, Damerau_Levenshtein.
Maximum edit distance The maximum number of differences between the two strings. (Applicable to Damerau_Levenshtein only)
Minimum score The minimum fuzzy score. (Applicable to Damerau_Levenshtein only)

Address Compare Options

Match box number and postcode When enabled, two compared addresses score Sure if they contain matching postal box numbers and postcodes.
User premise range When enabled, this will allow addresses to contain premise ranges.
Loose fuzzy premise match When enabled, additional fuzzy premise matching is performed.
Match delivery points When enabled, this will prevent two addresses from matching when both contain two postal codes but different delivery point codes and the addresses score below the minimum threshold.
Match DP threshold See match delivery points, above.
Default DPSs See match delivery points, above.
Ignore premise suffix When enabled, this will allow two premises to match regardless of whether one or both has an apartment- or flat-type suffix (for example, 12 and 12a).

Name Compare Options

Prevent mrs matching miss When enabled, then two compared names will not match if one has a title of Mrs and the other a title of Miss.
Fuzzy match non-normalized names When enabled (the default), this will cause additional matching checks to be performed on names using the non-normalized name matching fields.
Blank name company matching When two records contain no addressee names, this setting will allow the names to achieve a score depending on what's available in the job title and company name fields.
  • 0 - Off
  • 1 - On if either name blank
  • 2 - On when both names are blank
Initial match equivalent Controls how an initial matches a name that's equivalent to the given firstname. For example, when comparing Rebecca Smith and B Smith, then the B could be considered a match for Becky, which is a common abbreviation (or equivalent) of Rebecca.
Cross match initial to name When enabled (the default), and the first letter of a firstname matches the middle initial (for example, "Richard Smith" and "John R Smith") then the names will be considered a possible match.
Fuzzy match initials Controls how similar-sounding initials (M/N, S/F, and G/J) can be matched. When set to 'full' (the default), then one name's initial is permitted to match the first letter of the other name's firstname (for example, "M Smith" versus "Neil Smith"). When set to 'initialsOnly', then only initials are permitted ("M Smith" versus "N Smith"). A setting of 'noMatch' disables such matches.
Initial match forename Controls the result achieved when an initial matches the first letter of a firstname. This defaults to 'equal', so that B Smith versus Bob Smith will achieve the same result as Bob Smith versus Bob Smith (i.e. 'equal' for the firstnames). Reducing this setting to 'approx' or 'contains' will reduce the resultant name score in order to distinguish such matches.
Fuzzy match forename Used to prevent different recognized firstnames from fuzzy matching. For example, ordinarily Ron and Roy will fuzzy match.
Previous Article matchIT Hub Index Next Article
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Please sign in to leave a comment.