Reltio Connect

Hi Ujjwal, 

In Reltio we have options to use match cleansers for the match rule, which does not change the actual data but perform cleansing as needed on the fly while matching. One such cleanser available is "String Replacement Cleanser". Based on your use case, it seems like a good fit. Here is  the documentation for String Replacement Cleanser | Reltio

In this approach, you create a text file with the strings or characters (or their regex representation) that you want to replace during matching. Like in the attached sample I have used the below: 

\s=>\.=>\$=>

What this means is the String/regex provided in the left side of => syntax will be replaced with what has been provided in the right side. So in our use case, we will use null value on the right side to effectively eliminate the string. 

Once you have the file prepared, you will need to raise a support ticket to get this file uploaded in the relevant Reltio S3 bucket and get a public link for the file. You will then use that same link in your match group config as explained in the documentation. 

Let me know if it helps or if you need any further clarification. 

Hello,

We actually just ended up using the StringCharactersComparator. which looks to do the same thing. We will deploy the cleanser as well if testing proves otherwise. 

Thanks for the help!

Hi Ujjwal, 

In Reltio we have options to use match cleansers for the match rule, which does not change the actual data but perform cleansing as needed on the fly while matching. One such cleanser available is "String Replacement Cleanser". Based on your use case, it seems like a good fit. Here is  the documentation for String Replacement Cleanser | Reltio

In this approach, you create a text file with the strings or characters (or their regex representation) that you want to replace during matching. Like in the attached sample I have used the below: 

\s=>\.=>\$=>

What this means is the String/regex provided in the left side of => syntax will be replaced with what has been provided in the right side. So in our use case, we will use null value on the right side to effectively eliminate the string. 

Once you have the file prepared, you will need to raise a support ticket to get this file uploaded in the relevant Reltio S3 bucket and get a public link for the file. You will then use that same link in your match group config as explained in the documentation. 

Let me know if it helps or if you need any further clarification. 

Hi Ujjwal, 

In Reltio we have options to use match cleansers for the match rule, which does not change the actual data but perform cleansing as needed on the fly while matching. One such cleanser available is "String Replacement Cleanser". Based on your use case, it seems like a good fit. Here is  the documentation for String Replacement Cleanser | Reltio

In this approach, you create a text file with the strings or characters (or their regex representation) that you want to replace during matching. Like in the attached sample I have used the below: 

\s=>\.=>\$=>

What this means is the String/regex provided in the left side of => syntax will be replaced with what has been provided in the right side. So in our use case, we will use null value on the right side to effectively eliminate the string. 

Once you have the file prepared, you will need to raise a support ticket to get this file uploaded in the relevant Reltio S3 bucket and get a public link for the file. You will then use that same link in your match group config as explained in the documentation. 

Let me know if it helps or if you need any further clarification. 

Should this be automatically taken care of by Fuzzy matching? Why we need to cleanse before matching as all these should be caught by Fuzzy rule