Bring Federated Data Under YOUnite Control

A key feature of the YOUnite Data Hub is the capacity to manage all the federated data in your eco-system.   For 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 domain and property(ies) lives.    

Several things need to happen in order to facilitate that: 

1. 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".
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 have been created for each of the applicable data end points.  See the Adapter SDK <insert link to SDK documentation> 
5. Each data domain and property needs top be "mapped" to its location in the source data.   
6. Establish  key actors in the process of mapping. This includes the DGS and the individual zone data stewards. <insert link to data role page(s)>

This process is quite extensive and requires careful planning. 

For a each federated domain:

1. Create a master list of entities (AMJ QUESTION: What is an entity?) 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 unique <AMJ NOTE: HUH?!?>
   4. Create 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 These lists will be used in the "POST /drs/dr-uuid/map" step below.
2. POST /drs - Once the master list is established, <AMJ NOTE:  Need a contextual paragraph on what the POST is for> 
   1. POST /drs for each entity in the domain
      1. 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 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. 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)
4. Validation

Manually Adding New DRs

Manually Mapping Entities to DRs