One of the functions of the Core User Directory is to store affiliations with units of the University that people have. Affiliations in CUD are scoped in the form status@affiliation, where status can be "Student", "Staff", etc., and affiliation is the name of the unit where the person has that status. The data source that declared the affiliation, a start date, and an end date are stored. Affiliations are declared by both centrally administered systems, such as Student Records and Human Resources, and by units themselves. A single person may have multiple affiliations.
The Affiliations Manager (AM) enables unit administrators to manage lists of people affiliated with units for which they are administratively responsible. Affiliations defined within AM are limited in scope to the unit within which they are associated. They supplement affiliations declared by other sources. They are stored on individual person documents within CUD, supplementing affiliations declared by other sources. Scoped affiliations are part of the CUD Attribute Set and so can be used for building queries used for extracting data from CUD.
- Define a status within a unit of the University, this will be represented as a scoped affiliation in the form status@affiliation where status could be, for example, "Faculty member" and the affiliation will be the unit name. The status can be defined locally, but the unit must already be recognised within the University
- Upload a locally held list of people to be considered for inclusion in a list. The list is uploaded as a CSV file with a fixed minimum set of fields and an unlimited user-defined set of fields. The data is then automatically matched against data held in CUD
- Review (in a web interface or using a downloaded file) the matches made by CUD
- Confirm membership of the affiliation (in a web interface or file upload)
- Add people to CUD where they do not match an existing record, with the affiliation stored on their person document
- Remove people from an affiliation list as their status changes
- Compare affiliations derived from centrally administered systems with those defined locally
- Affiliations are stored in a centrally supported service
- An unlimited number of affiliations can be stored
- Affiliations are searchable by all registered users of CUD
- Data administrators are able to maintain lists of people affiliated with their units in a form in which records are linked to consolidated person documents held in CUD. This eases the task of maintaining accurate data
- Additional data for members of an affiliation list may be stored, and is visible only to administrators of that list
- Affiliations may be used to define groups in the forthcoming Groupstore service, and so could be used for access control
You will need to register as a user of the CUD service by contacting email@example.com