Our customer (person) data source is MDM which generates a unique person/party identifier for each identified or matched person. I am new to DV and trying to figure out how to best comply with core principle of DV which is built around business key concept.
Above mentioned party identifier (long numeric key) is not a business key. Business does not reference when searching for customer (person). But, that what we get from the source (MDM).
If you think about what would be the business key for person: Social Security Number in USA, combin
ation of first, last names, date of bir
th and etc… But, not all of them are readily , consistently and legally available. A typical problems that MDM supposed to solve. Therefore, my question is do I use a long MDM generated key as my business key in the HUB
? It seems that it is a wrong thing to do.
But, If I use natural keys (names, date of bir
th , address and so on) as my business key(s) in a HUB
then I will have to build and implement all those complex matching, de-duplication processes
in DV myself . We have MDM for that and paid a ton of money for it.
Is anybody out there had a similar dilemma?
As I said I am new to DV and will appreciate any recommendations.