CUD Service Users can contribute to or consume data from key or Primary Data Systems (PDS) such as Student Records System, University HR System, Alumni Relations System etc. Users are classified as following with respect to their association with PDS.
- Attribute Release Policies enable the Data Controllers to determine the access privileges of users to access or view attributes
- CUD ID provides a means to match and reconcile data with records stored in other Primary Data Systems
- Data Controllers may choose to function as CUD data consumers by performing queries against CUD offering the same set of benefits to them.
Users query the data and retrieve information stored in CUD. CUD data consumers can query CUD data and obtain a result, or set of results, about the user records. By using CUD, they can benefit in the following ways:
- Get access to authoritative data using a single source
- Data Controllers may configure the type, frequency and result format of queries made to CUD
- Data is verified to ensure that the data format is as expected, preventing unforeseen results for Data Controllers and their systems
- Data Controllers can determine data provenance using the meta data returned with queries
- Attributes that are not stored in CUD can be requested using the Foreign Key
All data consumers and data controllers are required to sign a Service Level Agreement. This is to ensure that CUD reflects the same or more restricted release policies of all parties. For example, to be able to use the University Card photo, a data owner is required to agree to a particular clause. Hence, CUD uses the same statement as the Card Office, including it in the Terms of Usage for Data Consumers.