Matching – MDM’s “Secret Sauce”

digg digg this | del.icio.us del.icio.us | reddit Reddit | StumbleUpon Stumble It!

I wrote a new guest article, published yesterday, on Infoglide Software’s Identity Resolution Daily blog.  My previous articles are here and here.  

Here’s an excerpt of the new article: 

Few areas in master data management (MDM) are as critical as identity resolution. Just yesterday, I was working with a client on a matching issue where their customer (a car dealership) was matched to a veterinary clinic because the business names both contained the city and the client had somehow entered the address of the vet clinic in their customer record.

This situation (a “false positive” if ever there was one) is far too common. While the current generation of MDM platforms has come a long way in the last five years, identity resolution is one of the most difficult problems to solve, especially when both your source data and the hub or referential source you’re matching to have data quality issues.

Click on “Matching – MDM’s “Secret Sauce”” to read the rest of the article.

Tags: , , , ,

One Comment on “Matching – MDM’s “Secret Sauce””

  1. Douglas Wood 03/27/2009 at 11:31 am #

    Great post, Dan. You’ve hit the nail on the head once again. Try as they might, vendors of simple math-based matching software do not qualify as identity or entity resolution solutions. Only an engine with an extensive library of algorithms, coupled with non-obvious relationship analysis and rules/decision processing can form a solution.

    Thank you for correctly pointing out that, when it comes to true identity resolution, the ‘math’ simply doesn’t add up.

%d bloggers like this: