I am working on consolidating customer data exist in two different databases.
I setup match specification in below way.
block commnds are
MatchfirstnameNYSIIS_USNAME
MatchPrimaryname_USNAME
STATE_CD
ZIP CODE
match command
Matchfirstname_USNAME (Mprob 0.9 , Uprob 0.1 , Param1 850)
MatchPrimaryname_USNAME (Mprob 0.9 , Uprob 0.1 , Param1 850)
ADDRESS1 (Mprob 0.8 , Uprob 0.1 , Param1 700)
ZIP CODE (Mprob 0.6 , Uprob 0.1 , Param1 500)
Comparision type for all the columns is UNCERT
when I do TestALLPasses , below data combination showing as mater and duplicates record
firstname | Last Name | ZIP | STATE | address1 | weight
DAVID | Robin | 19382 | FL | 501 W Street Rd | 62.33
DAVID | Robin | 19382 | FL | 1119 S New St | 23.68
As per our requirement when there is no match in address , we need to consider as a different record . but now quality stage generating 1 master and duplicate record . Please help me how can i fix this?
Match specification - incorrect classification
-
- Participant
- Posts: 29
- Joined: Sun Jul 22, 2007 3:25 pm
Match specification - incorrect classification
Vijaya K Dasari
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 29
- Joined: Sun Jul 22, 2007 3:25 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Sounds like you need to invest in some training, or at least in some time reading the manual. Match and clerical cutoffs serve different purposes. Please research that and post your findings back here.
Yes, I do know the answer, but my philosophy is to help you to help yourself. If I simply give you the answer you won't learn as effectively.
Yes, I do know the answer, but my philosophy is to help you to help yourself. If I simply give you the answer you won't learn as effectively.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 29
- Joined: Sun Jul 22, 2007 3:25 pm
Hi Ray,
here are my findings . please let me know if i am wrong.
match cutoff is used identify match records . record pairs with compositer weight
more than cutoff are reliable match.
clerical cutoff is used identify posible match records . record pairs with compositer weight
more than clerical cutoff are possible match.
record pairs whose composite weight between match cutoff and clerical cutoff are clerical.
here are my findings . please let me know if i am wrong.
match cutoff is used identify match records . record pairs with compositer weight
more than cutoff are reliable match.
clerical cutoff is used identify posible match records . record pairs with compositer weight
more than clerical cutoff are possible match.
record pairs whose composite weight between match cutoff and clerical cutoff are clerical.
Vijaya K Dasari
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Almost but not quite. Records with composite weight below clerical cutoff are non-matches (residuals), at least for that pass. Otherwise good. Clerical cutoff must be set <= match cutoff.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.