To fully leverage the YOUnite ecosystem, organizations need to fully understand the following areas of integration:
- Operational - Manage : Managing 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 . This functionality can also be built into the organization's own applications.
- Data Stewardship and Governance - Create : Creating data domains and manage managing scope (ACLs) . These requests are made using the YOUnite API.
- Creating and mapping source entities to YOUnite data records. This can be done with the YOUnite API. Adaptors also perform the creating and mapping tasks over the YOUnite 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.
Retrieving Data Records: The YOUnite API has an endpoint for retrieving data records (both federated data records and those stored in YOUnite). This endpoint is generally used by applications that don't have access to a source system that is connected to YOUnite through an adaptor or when the adaptor doesn't support a data domain required by the application.
Once the operational and data governance resources are created and source records are mapped to YOUnite data records (items 1 -through 3 from above), a functioning YOUnite MDM ecosystem performs three primary tasks using both the YOUnite message bus and API interfaces:
...