Page Comparison

A key feature of the YOUnite Data Hub is the The capacity to manage all the federated data in your eco-system.   For ecosystem is a key feature of the YOUnite Data Hub. In order to manage every data domain and data property (AMJ NOTE: DOMAIN AND PROPERTY NEED TO BE HYPER LINKED TO A DEFINITION IN THE GLOSSARY) , YOUnite needs to know where that data domain and property(ies) liveslive.    

Several things need to happen in order to facilitate that: 

...

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 Implementation OverviewAdoption Plan and have has completed the steps up to Step 13: "Bring Federated Data Under YOUnite Control".
2. Each application or service connected to YOUNite needs to be identified and registered as a data end point (AMJ NOTE: I made up the term "data end point" -INSERT whatever the appropriate term is) with the appropriate metadata. See <insert link to that page> 
3. Data Domains need to be identified and understood for this eco-system <insert link to data domain documentation page>
4. Adapters- or APIs- need to (source system) has been identified and registered to YOUnite through an adaptor. See Managing Adaptors for how to register and manage an adaptor.
5. Data Domains have been identified and understood for this ecosystem. See Data Domains.
6. Adaptors have been created for each of the applicable data end points.  See the Adapter SDK <insert link to SDK documentation> Each data domain and property needs top be "mapped" to source systems. Adaptors are developed using the Adaptor SDK.
7. Each data record for a given data domain has been "linked" from its location in the source datasystem to YOUnite.   
8. Establish  key Key actors in the process of mapping have been established. This includes the DGS and the individual zone data stewards. <insert link to data role page(s)>

...

1. Zone Data Stewards (see the section on "Zones" in Zones, Users, Groups, Roles and Permissions).

Mapping for Federated Domains

Anchor
mappingFederatedDomains mappingFederatedDomains

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 entities (AMJ QUESTION: What is an entity?) 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 uniqnuess rulesThis may require cleaning data in the systems to ensure that 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 the "POST /drs" step step 2, "Creating YOUnite Data Records," below.
   5. Create an entity list for each adaptor. These lists will be used in the "POST /drs/dr-uuid/map" step below.
POST /drs -
2. 1. step 4, "Create Links to the YOUnite Data Records," below.
3. Create YOUnite Data Records. Once the master list is established, <AMJ NOTE:  Need a contextual paragraph on what the POST is for> 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 This creates 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 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)
   POST /drs/dr-uuid/map  For
4. Pause the adaptors.
5. Create links to the YOUnite Data Records. For each adaptor, map the entities in the systems and services attached to the adaptors to the DRsdata records,
   1. (TODO: example script)
6. Validation.
7. Transition the adaptors to "Play" or "Play Read Only."

Manually Adding New DRs

Manually Mapping Entities to DRs