Reltio Connect

I have a match rule on HCP with fuzzy on first & last name and exact on the address fields. When I run the Reltio match analysis job, it marks some match tokens as overcollisioned with corresponding HCP entity list. What I find is though the first & last names are completely different, these HCPs share a common location. In fact, the location has 300+ HCPs.

Is that what is leading to the token being marked as  overcollisioned? How to handle the scenario given I cannot move HCPs out of that address?

Thanks. 

I think we'd need some more information to help you.  What's the tokenezation class for the name attributes?  Assuming this has been set up correctly, I don't believe you will get the issue.  Can you share that?

I have a match rule on HCP with fuzzy on first & last name and exact on the address fields. When I run the Reltio match analysis job, it marks some match tokens as overcollisioned with corresponding HCP entity list. What I find is though the first & last names are completely different, these HCPs share a common location. In fact, the location has 300+ HCPs.

Is that what is leading to the token being marked as  overcollisioned? How to handle the scenario given I cannot move HCPs out of that address?

Thanks. 

Thanks for the reply. We're using DoubleMetaphoneMatchToken & DoubleMetaphoneComparator on first & last name. Also, both the attributes are marked with ignoreInToken=true.

I think we'd need some more information to help you.  What's the tokenezation class for the name attributes?  Assuming this has been set up correctly, I don't believe you will get the issue.  Can you share that?

I have a match rule on HCP with fuzzy on first & last name and exact on the address fields. When I run the Reltio match analysis job, it marks some match tokens as overcollisioned with corresponding HCP entity list. What I find is though the first & last names are completely different, these HCPs share a common location. In fact, the location has 300+ HCPs.

Is that what is leading to the token being marked as  overcollisioned? How to handle the scenario given I cannot move HCPs out of that address?

Thanks. 

Hi,

I think your problem is the ignoreInToken.  See the documentation: https://docs.reltio.com/en/reltio/what-does-reltio-do/what-reltio-does-at-a-glance/data-unification-and-mdm-at-a-glance/data-unification-and-mdm-in-detail/reltio-match-and-merge/match-group-elements---description-and-configuration/rule-element/ignoreintoken.

if it is 'true', then the token is NOT generated.  I think you need this to create the uniqueness in the token that would differentiate your matches and prevent the over collision.

Thanks for the reply. We're using DoubleMetaphoneMatchToken & DoubleMetaphoneComparator on first & last name. Also, both the attributes are marked with ignoreInToken=true.

I think we'd need some more information to help you.  What's the tokenezation class for the name attributes?  Assuming this has been set up correctly, I don't believe you will get the issue.  Can you share that?

I have a match rule on HCP with fuzzy on first & last name and exact on the address fields. When I run the Reltio match analysis job, it marks some match tokens as overcollisioned with corresponding HCP entity list. What I find is though the first & last names are completely different, these HCPs share a common location. In fact, the location has 300+ HCPs.

Is that what is leading to the token being marked as  overcollisioned? How to handle the scenario given I cannot move HCPs out of that address?

Thanks. 

You're spot on. We removed ignoreInToken and the issue is gone.

Thanks a lot.

Hi,

I think your problem is the ignoreInToken.  See the documentation: https://docs.reltio.com/en/reltio/what-does-reltio-do/what-reltio-does-at-a-glance/data-unification-and-mdm-at-a-glance/data-unification-and-mdm-in-detail/reltio-match-and-merge/match-group-elements---description-and-configuration/rule-element/ignoreintoken.

if it is 'true', then the token is NOT generated.  I think you need this to create the uniqueness in the token that would differentiate your matches and prevent the over collision.

Thanks for the reply. We're using DoubleMetaphoneMatchToken & DoubleMetaphoneComparator on first & last name. Also, both the attributes are marked with ignoreInToken=true.

I think we'd need some more information to help you.  What's the tokenezation class for the name attributes?  Assuming this has been set up correctly, I don't believe you will get the issue.  Can you share that?

I have a match rule on HCP with fuzzy on first & last name and exact on the address fields. When I run the Reltio match analysis job, it marks some match tokens as overcollisioned with corresponding HCP entity list. What I find is though the first & last names are completely different, these HCPs share a common location. In fact, the location has 300+ HCPs.

Is that what is leading to the token being marked as  overcollisioned? How to handle the scenario given I cannot move HCPs out of that address?

Thanks.