Why aren't we seeing a match for FirstName in verify matches API.

Question

We see the following First Name is not finding a match in the verify matches API, we could see that the pair shows as "MatchedbyDocuments" but not an actual match.

"FirstName": [
         {
             "type": "configuration/entityTypes/HCP/attributes/FirstName",
             "ov": true,
             "value": "Theodore",
             "uri": "entities/1UIpyUA/attributes/FirstName/8ND2Eka6"
         }
     ],

"FirstName": [
         {
             "type": "configuration/entityTypes/HCP/attributes/FirstName",
             "ov": true,
             "value": "Ted",
             "uri": "entities/1UIq70g/attributes/FirstName/8ND2FqmE"
         }
     ],

Answer

• Your match is failing from this condition.

"fuzzy": {
                                 "FirstName": {
                                     "match": false,
                                     "ignoreInToken": false
                                 },
                                 "LastName": {
                                     "match": true,
                                     "ignoreInToken": false
                                 }
                             }

• You are using the following matchTokenClass "ExactMatchToken" and "DynamicDamerauLevenshteinDistance". Please re-consider using another "ExactMatchToken".
• Also, consider using a NameDictionaryCleanser for the first name attribute. 
• Another alternate solution would be to create a customized version of the match value using RDM.

The comparator class will consider the values of two attributes as S1 and S2. This comparator counts n, the minimum number of single-character operations (insert, delete, replace) required to convert string S1 to S2 most efficiently. The comparator returns true if n is:

• =0 (that is, the strings are already equal)
• <=1 where the largest raw string length is <=4
• <= 2 where the largest raw string length is > 6 and <=10

For example, to make John equal to jon, n = 1. The comparator returns true.

For example, to make John equal to jonathon, n = 6; the comparator will return false.

• Behaves differently for the Fuzzy operator vs the Exact operators (Exact, ExactOrNull, ExactOrAllNull, and notExactSame). If chosen for Exact, ExactOrNull, ExactOrAllNull, and notExactSame, the comparator’s logic is used for the Exact part of these.
• Can be used for the Fuzzy Comparison Operator.
• Recommended for cases where you wish to compare two strings that might have spelling inconsistencies.
• Typical use cases are matching words that are believed to have spelling errors.
• Supports non-Latin character sets.
• Guidance regarding Match Token Class: FuzzyTextAndNumberMatchToken class. If a match token class is not defined, the FuzzyTextAndNumberMatchToken class is used by default

Resources

• How can I address a problematic suspect match rule (identified in the match analysis tool) that is causing performance problems?
• https://docs.reltio.com/en/explore/get-a-crash-course/get-ready-to-turn-your-data-into-action/learn-about-multidomain-mdm/reltio-match-merge-and-survivorship/match-group-elements---description-and-configuration/rule-element/match-cleansers/name-dictionary-cleanser