MDR Mapping

Every MDR has a unique way of identifying the CIs that it manages. Those identifiers are seldom synchronized across MDRs. For example, when referencing a specific Contact CI, different MDRs can use the national identity number, telephone number, license number, or Employee ID; all refer to the same person. The process of associating these disparate identifiers with the same unique identifier (UUID) maintained in the MDB is named mapping. Mapping occurs automatically when data is imported using GRLoader when the CI contains the <mdr_name> <mdr_class> and <federated_asset_id> tags. Mapping can also be accomplished manually through the Administration functions in the user interface. A CI that has no mappings associated with it is named unfederated. Every CI is automatically mapped to global MDRs using the UUID as the federated_asset_id.