Entity Resolution Results

If the results from Senzing don't look correct, you may need to review and change your mappings for one or more data sources. 

Locate your data sources and click on MAPPING to open the mapping screen for the source to review and change. 

Assuming you find changes to the mapping are required, start to make those changes. A pop up will display informing that changing the mapping will result in a purge of the Senzing repository and the data sources will need to be reloaded. When changing mappings the data needs to be purged and entity resolved again, taking into account the new mappings.

Click Purge Repository

You can then change the desired mappings and reload the data sources.

Some things to consider:

1. Are the fields you mapped sparsely populated? For instance, if you're hoping the date of birth field will assist in making matches, ensure that column isn't mostly empty.
   
   
2. Did you map the entire name or the entire address? It might be that address line1 was mapped, but not the address city, state or postal code. Perhaps you should have mapped to the full address field because the entire address is in one field.
   
   
3. Did you map a field that doesn’t belong to the entity? For instance, on a list of contacts for a company, there are two entities. The contact is one entity and the company they work for is another. Typically, the address belongs to the company, but the phone number, especially the mobile phone, belongs the individual. In this case, you must decide which is the entity you really want to resolve and map only those columns that define that entity.
   
   In this instance you can add the data source again and re-map the attributes for the other entity not mapped the first time around.