Organizations To fully leverage the YOUnite ecosystem, organizations need to integrate their applications into the YOUnite ecosystem. There are several different fully understand the following areas of integration:
- Operational - Manage zones, users, groups, roles and permissions. These requests are made using the YOUnite API. The YOUnite UI is an example of an application that consumes the YOUnite API and makes operational and Data Governance requests on behalf of the logged in user but this functionality can be built into the organization's own applications.
- Data Stewardship and Governance - Create data domains and manage scope (ACLs). These requests are made using the YOUnite API.
- Creating and mapping source entities to YOUnite data records. This can be done with either the YOUnite API. Adaptors also perform the creating and mapping tasks over theYOUnite message bus.
- Integrating data and keeping source entities in sync. This is managed by adaptors connected to the YOUnite message bus.
- Receiving notifications of data record changes so that applications can initiate their own work flows.
The YOUnite API can also act as an operational data store for retrieving records. This is generally used for systems that are not connected to YOUnite through an adaptor or when the adaptor doesn't support a data domain required by the service.
Once the operational and data governance resources are created and source records are mapped to YOUnite data records (1-3 from above), a functioning YOUnite MDM ecosystem performs three primary tasks using two separate both the YOUnite message bus and API interfaces:
| Primary Task | Description | Interfaces Used |
| Data Integration | Generally business logic in adaptors is kept to a minimum the sole purpose of adaptors is to both detect changes in source entities and publish them to YOUnite and to subscribe to changes published by other adaptors and process them by updating entities in the source system attached to the adaptor. | Adaptors connected to both source systems and the YOUnite message bus. |
| Governance | Scopes can be managed manually by the DGS and the Zone Data Stewards (ZDSs) or they can be managed programmatically by applications when well defined events occur. For example, if a customer signs up for a new service, scope can be set so that data in a source system that already contains the customer's data is granted to a system that holds customer records for the new service. | YOUnite API |
| Notifications | Changes in data can trigger events in applications and services. YOUnite allows applications and services to register for events so that they can be notified when changes occur allowing the services and applications to start their own workflows. | YOUnite API |
| Operational Data Store | This is generally used for systems that are not connected to YOUnite through an adaptor or when the adaptor doesn't support a data domain required by the service. | YOUnite API |
...
See the /drs endpoint in the YOUnite API.
TODO: Update this so the art is consistent and move it to the MB Overview page
...