Matching on Data in Multiple Languages

Reltio Match Engine supports matching data in the following languages: Chinese, Korean, Japanese and Arabic.

The Match Engine converts non-Latin data used in matching to Latin before matching. This enables matching engine to match data in any language or even across different languages.

How does matching on multiple languages work?

The Match Engine converts text from one script to another. The letters are exchanged in a predictable manner. This matching can accurately represent the characters of a source alphabet using characters of a target alphabet. The matching on multiple languages represents the characters, accurately and clearly. It is not essentially concerned with representation of the sounds.

You can assign a matching engine to the attribute inside a match group.

The Configuration of Match Engine example explains how the Match Engine can be configured.

Example: Configuration of Match Engine
{
                    "uri": "configuration/entityTypes/HCP/matchGroups/HCPbyTransLiterator",
                    "label": "HCP by transliterated Name",
                    "type": "suspect",
                    "rule": {
                        "and": {
                            "exact": [
                                "configuration/entityTypes/HCP/attributes/NonLatin_Name"
                            ],
                            "cleanse": [
                                {
                                    "cleanseAdapter": "com.reltio.cleanse.impl.TransliterateCleanser"
                                    },
                                    "attributes": [
                                        "configuration/entityTypes/HCP/attributes/NonLatin_Name"
                                    ]
                                }
                            ]
                        },
                        "matchTokenClass": "com.reltio.match.token.ExactMatchToken"
                    },
                    "matchServiceClass": "com.reltio.businesslogic.match.providers.internal.InternalMatchService"
                }

The Assigning a Match Engine example illustrates how you can assign a match engine to the attribute inside a match group.

Example: Assigning a Match Engine

 {
   "uri": "configuration/entityTypes/HCP/matchGroups/HCPbyTransLiterator",
                    "label": "HCP by transliterated Name",
                    "type": "suspect",
                    "rule": {
                        "and": {
                            "exact": [
                                "configuration/entityTypes/HCP/attributes/NonLatin_Name"
                            ],
                            "cleanse": [
                                {
                                    "cleanseAdapter": "com.reltio.cleanse.impl.TransliterateCleanser",
                                    "cleanseAdapterParams": {
                                        "transliteratorCommand" : "Any-Latin"
                                    },
                                    "mappings": [
                                        {
                                            "attribute": "configuration/entityTypes/HCP/attributes/NonLatin_Name",
                                            "cleanseAttribute": "configuration/entityTypes/HCP/attributes/NonLatin_Name"
                                        }
                                    ]
                                }
                            ]
                        },
                        "matchTokenClass": "com.reltio.match.token.ExactMatchToken"
                    },
                    "matchServiceClass": "com.reltio.businesslogic.match.providers.internal.InternalMatchService"
                }

Match rule can be configured to match with any specific attribute using multi-language matching.