Entity Resolution Results

If the results from Senzing don't look correct and you need to change your initial mappings, simply delete a data source and re-add it. You'll be happy to notice Senzing retained all your prior mappings for that data source.

You can then change the desired mappings and reload. Here are some things that you might want 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 or postal code. Or 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 actually define that entity.
   
   In this instance you can add the data source again and re-map the attributes for the other entity not correctly mapped the first time around.