Reltio Connect

Hello community, 
Very new to Reltio so please point me to the thread if this was already answered.

We have a situation where the source systems have to mask the names and addresses of individuals due to CCPA. The logic they use is as follows:
Joe Smith post masking becomes 12000768 12000768
Dana Hue post masking becomes 12000968 12000968 and so on..
and there addresses are set to one common address. 

Due to this, these masked records are shown as potential matches as the names are very similar and addresses are the same and we don't want them to match. 

I am wondering if there is a setting where I can say:
Exclude from matching
when
first name is a number
    and
last name is a number 
    and 
address 1 = 123 main street

Appreciate your help.

@Haresh Joshi thanks for posting. I haven't forgot about this question. I'm looking for someone to answer. Hold tight! ​

Hi Heresh,

Are all of your names masked or just some?  If they are all masked I would recommend using the exact operator as fuzzy matching will not be able to add value through the mask.

If you have a mix of masked and unmasked names in your dataset I would consider creating a new attribute for the masked names and using it for matching masked names to other masked names.

@Joel Snipes

Hi Joel,
We have a mix and we don't want these masked records to match. Currently all these records show in Potential Match ​section and someone has to go and manually mark them 'not a match'. Hence we are looking at options to exclude all masked records from matching or even showing up in potential match queue.

The way you normally filter potential matches from a rule is the equals operand, but it does not have the ability to identify numeric vs the character strings.

If you aren't willing to update your data model and move the masked names to another attribute I have one other idea.

You can use the match cleanser to use regex to identify masked attributes and output a string like "masked". Then use notEquals("masked") to filter all masked attribute from the potential matches.

@Joel Snipes thanks a lot. I will give this a try. ​

@Joel Snipes I worked with our developers to discussed the idea of creating a new attribute for the masked records but their concern is that since the new attribute will be set at the whole profile level we may miss out on future legit matches.  

Let me explain with an example:

Let's say we have a profile Mary Smith that has 2 non-ov records. one from Salesforce and another from oracle. We mask only the non ov records from salesforce. So if we set the masked flag for this profile, we might miss out matching Mary Smith with a future record if we get a new record such as Marie Smith. 

Let me know if it makes sense. Any thoughts?