Match Specification (Match Command)

DSFreddie · Post by **DSFreddie** » Mon Jan 02, 2012 10:13 pm

Hi All,

Request your help in resolving an issue in one of the Match Command Column PREFIX. As per the below Prefix values & the Match Specification defined, the following 2 records shouldnt be considered as groups.

1000 JUSTIN MS
1000 JUSTIN MR

I am using the Comparison Type CHAR The m-prod/u-prob values given are 0.9/0.01.

Can you pls tell me what I am missing here ? Let me know incase of questions.

Note : I am using IIS 8.5 version.

Thanks,
Freddie

BI-RMA · Post by **BI-RMA** » Tue Jan 03, 2012 5:01 am

Please be aware that MatchCommands will only be applied to members of the same block.

You will have to look at the values for qsmatchweight to find out how important QualityStage considers the difference between your two records to be, given the specification you provided for all MatchCommands.

QualityStage is designed to identify duplicates in spite of certain misspellings on columns used in MatchCommands.

If You want strict distintion between "MS" and "MR" on the column PREFIX, use the column as a blocking column.

rjdickson · Post by **rjdickson** » Tue Jan 03, 2012 11:00 am

A better option is to use 'Critical Misssing OK' on the name prefix column. Using this option means you do not need to block on the prefix.

'Critical Missing OK' means that populated values must be identical for the match to be valid. Any disagreement of populated values will immediately, regardless of any other factors of weight or overrides, treat the pair as a mismatch. The 'Missing OK' means that one or both can be blank, and the records will be treated as normal.

This functionality is under the 'Special Handling' button at the top of the match designer.

ray.wurlod · Post by **ray.wurlod** » Tue Jan 03, 2012 2:34 pm

I agree with Robert. Another technique that accomplishes a similar result is to provide a disagreement weight override, so that disagreement drags the composite weight substantially lower.