In Continuation with previous blog: Matching & Merging: Equals Vs Token Equals (Part 1)
Through this blog, I will try my best that this difference between Equals Vs Token Equals is easily understood by everyone and how scores get affected and come different than what we have set in case of Function = Token Equals.
Working with function “Token Equals“
At this point of time you know that for executing Matching, you need to define Transformation, Rule and Strategy.
Open MDM Data Manager, Go to Matching Mode:
1. Define a Transformation :
2. Define a Rule : Here in this Rule “Matching Material Description”, I have included Transformation just created above and set Function = Token Equals and other parameters as shown in below screen-shot.
3. Define a Strategy now : Here in this Strategy, I have included the Rule “Matching Material Description” as created above and set other parameters as shown in below screen-shot.
Now coming to Data Manager: Record Mode
Now, I have four records for which there is value for field Material Description as shown below:
Since we have set Rule Property Function = Token Equals, it will treat these 3 tokens as separate (distinct) token. Lets see how it shows score when we execute Strategy
After executing the strategy: In matching Mode, we get the following scores
Now you are wondering with Material Description “Lexan IP 300” we have the right Score 100 which we defined during Rule but what about other two records how the score 20 is coming for Material Desciption “Lexan ID 900” and how it is showing score 50 for Material Description “Lexan IP 600” since we have not set these scores during defining Rule.
Logic is pretty simple:
1stly in Function “Token Equals” each Token is considered as separate token (identity) unlike Function “Equal” where these 3 tokens considered as single individual token.
2ndly it gives score basis on the below formula:
Score = Success * Number of Unique Matching Tokens / Total Number of Unique Tokens
Now let’s see score for each of these Material Description:
For Material Description : “Lexan IP 300” with “Lexan IP 300”
Number of Unique Matching Tokens: 3 (Lexan, IP and 300)
Total Number of Unique Tokens: 3 (Lexan, IP and 300)
So Score: 100* 3 / 3 = 100.
For Material Description: “Lexan ID 900” with “Lexan IP 300”
Number of Unique Matching Tokens: 1 (Lexan)
Total Number of Unique Tokens: 5 (Lexan, ID, IP, 300 and 900)
So score: 100* 1 / 5 = 20
For Material Description: “Lexan IP 600” with “Lexan IP 300”
Number of Unique Matching Tokens: 2 (Lexan and IP)
Total Number of Unique Tokens: 4 (Lexan, IP, 600 and 300)
So score: 100* 2 / 4 = 50
My primary objective is to show Score calculation through these blogs. So I hope now you would not wonder if you find Matching score different than you defined in Rule if you are using Property, Function = Token Equals.
MDM Data Manager Reference Guide