Linking YOUnite Data Records to Entities at the Source Systems

The capacity to manage all the federated data in your ecosystem is a key feature of the YOUnite Data Hub. In order to manage every data domain and data property, YOUnite needs to know where that data domain and property(ies) live.    

TODO - Need to cover the alternative to proactively mapping data records and that is organically mapping as data events occur.

To facilitate YOUnite's managing of your federated data, the following assumptions are made:

1. Your organization has already reviewed the YOUnite Adoption Plan and has completed the steps up to Step 13: "Bring Federated Data Under YOUnite Control".
2. Each application or service (source system) has been identified and registered to YOUnite through an adaptor. See Managing Adaptors for how to register and manage an adaptor.
3. Data Domains have been identified and understood for this ecosystem. See Data Domains.
4. Adaptors have been created for each of the applicable source systems. Adaptors are developed using the Adaptor SDK.
5. Each data record for a given data domain has been "linked" from its location in the source system to YOUnite.   
6. Key actors in the process of mapping have been established. This includes the DGS and the individual Zone Data Stewards (see the section on "Zones" in Zones, Users, Groups, Roles and Permissions).

Mapping for Federated Domains

The mapping process is quite extensive and requires careful planning. Use the following steps to assist your mapping process.

For a each federated domain:

1. Create a master list of all entities in the source systems 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 uniqueness rules (for more on uniqueness rules see Data Domains).
      1. You may need to clean system data to ensure all entities are unique <AMJ NOTE: HUH?!? - MF> - Inspect the entities stored on the source systems and ensure they are unique when the uniqueness rules are applied to them. If there are conflicts (i.e. dupes) either the source system entities that are raising the exception need to be modified or the uniqueness rules for the domain need to be re-evaluated.
   4. Create a list of all entities with all of the uniqueness rule values. This will be used in step 2, "Creating YOUnite Data Records," below.
   5. Create an entity list for each adaptor. These lists will be used in step 4, "Create Links to the YOUnite Data Records," below.
2. Create YOUnite Data Records. Once the master list is established, YOUnite data records for each domain need to be created by using the POST /drs request.
   1. POST /drs for each entity in the domain.
      1. This creates a YOUnite data record for each entity.
      2. After this step is completed YOUnite only contains the uniqueness rules and none of the data records are mapped to any of the systems or services attached to the adaptors.
      3. (TODO: Show an example of a script that POSTs DRs)
3. Pause the adaptors.
4. Create links to the YOUnite Data Records. For each adaptor, map the entities in the systems and services attached to the adaptors to the data records,
   1. (TODO: example script)
5. Validation.
6. Transition the adaptors to "Play" or "Play Read Only."

Manually Adding New DRs

Manually Mapping Entities to DRs