Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Entities in the systems and services attached to the YOUnite adaptors need to be linked mapped to YOUnite data records. The process is called linking mapping entities to MDM or "linking"mapping" and it needs to be performed on all federated data domains. It is assumed that an organization has already reviewed the YOUnite Implementation Overview and have completed the steps up to "Bring Federated Data Under YOUnite Control". These steps include but are limited to:

  • Define data domains - very important for this process are understanding the uniqueness rules
  • Develop adaptors
  • Establish key players in the DGO such as An understanding of a data domain's uniqueness rules is essential for this step
  • Develop adaptors for the federated data domains - See the adaptor SDK
  • Establish key actors in the process of mapping. This includes the DGS and the individual zone data stewards.

This process is quite extensive and thus needs to be planned out well:requires careful planning. 

For a each federated domain being linked:

  1. Create a master list of entities that need to be mapped to YOUnite:
    1. Identify all systems that have adaptors that contain entities of this domain type
    2. Typically, one system has the entire set of entities but the entire set can be a composite of two or more systems
    3. Ensure that all entities in all systems meet the uniqnuess rules
      1. This may require cleaning data in the systems to ensure that all entities are unqiue
    4. Create the a list of all entities with all of the uniqueness rule values. This will be used in the "POST /drs" step below.
    5. Create an entity list for each adaptor adaptor These lists will be used in the "POST /drs/dr-uuid/map" step below.
  2. POST /drs - Once the master list is established,Validate
    1. POST /drs for each entity in the domain
      1. this creates
      an entity
  3. For each adaptor, link
      1. a YOUnite data record (DR) for each entity
      2. After this step is completed YOUnite only contains the uniqueness rules and none of the DRs are mapped to any of the systems or services attached to the adaptors.
      3. (TODO: Show an example of a script that POSTs DRs)
  4. POST /drs/dr-uuid/map  For each adaptor, map the entities in the systems and services attached to the adaptors to the DRs
    1. (TODO: example script
  5. Validation


Manually Adding New DRs

Manually Mapping Entities to DRs