The hybrid MDM model

After you decide that one of the hybrid MDM scenarios meets your business needs, begin by defining your virtual MDM model and mapping it accurately to the appropriate physical MDM domain. It is strongly recommended that you start with the default Party model (Party.imm) provided with IBM® InfoSphere® MDM.

Mappings create correspondences between virtual MDM attributes and physical MDM attributes. Most of the mappings that you need are defined already and provided with InfoSphere MDM Advanced Edition. Use the InfoSphere MDM Workbench and begin with the default mapping for your hybrid MDM solution. As needed, you can add more attributes to the mapping, or remove unnecessary attributes from the mapping.

Modify the mapping whenever you introduce a new attribute type in the virtual MDM model that you want to include in the persisted enterprise view in physical MDM. The mapping between virtual MDM and physical MDM Party models uses the InfoSphere MDM Workbench and leverages an XSD representation of the data structures of each model. As the models change, for example, when you have data additions or extensions, the XSD representation of these models might be changed. The changes can then be considered and mapped.

In general, when you are creating a mapping between virtual MDM and physical MDM attributes, you must include in the mapping all attributes that are defined as business keys. Use the provided transcode XSLT function for mapping new attribute types to physical MDM business objects are already mapped (for example, if you want to add a new virtual MDM attribute for a new Party Identification type.

After updating the virtual MDM model and mapping attributes between virtual MDM and physical MDM, define the matching algorithm. The matching algorithm aids in the de-duplication of your data. As a final step, choose a single composite view of the virtual MDM entities that you want to persist as the "golden record" in physical MDM.