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.
...
- 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".
- 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>
- Data Domains need to be identified and understood for this eco-system <insert link to data domain documentation page>
- 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>
- Each data domain and property needs top be "mapped" to its location in the source data.
- 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.
...