5. Affiliations Manager
Affiliations Manager is intended to enable units of the University to assert an affiliation with a unit. These affiliations supplement those asserted by central data systems such as University card and HR. Affiliations suitable for adding to CUD in this way must be:
- Of interest to more than one unit within the University
- Actively managed by the Unit which asserts the affiliation (unmanaged affiliations will expire automatically)
- Suitable to be available as part of the CUD attribute set to all authorised users of CUD
- The affiliations asserted can be used as criteria in searches of CUD
- Affiliations are added to person records in CUD, as these records are constantly updated management of the life cycle of an affiliation is made easier
- Affiliations can be shared between multiple units
Affiliations Manager displays Affiliation lists which have been asserted over which you have administration rights (the creator of an Affiliation list automatically has administration rights over it). No such lists are shown in the example below. A button is provided to enable a new Affiliation list to be created.
Affiliations in CUD take the form <status>@<unit> both parts of this must be selected from the drop-down lists provided. Additional statuses can be requested (a process for this is being developed at the moment). Units are defined by PRAC, and only those over which you have administrative rights are available for you to choose from.
- Upload a file for matching (using a similar process to that used for Simple Matching)
- Download a file containing exact matches that have been made
- Upload a file containing exact matches, including a CUD ID for each record. This file can be obtained from Simple Matching, or using the matching functionality provided by Affiliations Manager
- People who are asserted to have the affiliation and on whose CUD records the affiliation is included
- A button to use in order search for individual people and add them to the affiliation list
- The results of a matching upload once processed by CUD, these should be checked and manipulated such that each record uploaded is matched to a single record in CUD
- Records contained a matching upload which could not be matched against CUD. You are encouraged to check carefully whether these people exist but have not been found for any reason
- If you are sure that a person does not currently exist in CUD (e.g. people external to the University), but you wish to assert an affiliation for the person, you may add them to CUD as a special case
Here a file is uploaded for matching. Please note that each time a file is uploaded for matching all records which have previously been uploaded for matching are deleted before the upload is processed. Confirmed members of this affiliation are not affected.
The column headings must be left as they are in the sample. Add as much data as you are able. Please note that the fields that can be provided are limited, but this is likely to be extended during the early adopter phase.
Here we have removed one of the matches, as a match had already been made for that object. We then download a file of exact matches, so ignoring the record with multiple matches. This example this consists of a single record, complete with the CudID.
That file can then be uploaded to confirm membership of the affiliation list. At this point the affiliation is added to person documents in the CUD data store and so can be used in search terms and retrieved by authorised CUD users. The lists of matched records awaiting checking and unmatched records are cleared at this point. New lists may then be uploaded for matching.
If you are absolutely sure that the an un-matched person does not exist in CUD or in any of the primary data sources that supply data to CUD, you may add the person as a special case. The affiliations list, it's owner and administrators will be recorded as the source of data for this person.