Directory Services Affiliation Discussion - December 6, 2000

Updated with Core Team Meeting comments from December 11, 2000

Overview

Affiliation describes an individual’s relationship with the university.

Affiliation will be used by the directory for two primary purposes:

· To determine whether services should be granted to the user (check performed via a directory enabled system)

· To determine what information should be displayed and/or made public for the individual associated with the entry.

Three affiliation-related attributes will be carried in the directory:

description

..... affiliation values specific to CU. The most granular definition. Multi-valued.

eduPersonAffiliation

..... broad category of affiliation according to eduPerson’s controlled vocabulary (Faculty, Staff, Student, Alum, Member, Employee, Affiliate). According to eduPerson, “member” is intended to include faculty, staff, student, and other persons with a basic set of privileges that go with membership in the university community (e.g., library privileges). It might be thought of as “member in good standing of the university community.” “Affiliate” is intended to apply to people with whom the university has dealings, but to whom no general set of “community membership” privileges are extended. CU-applicable definitions will be mapped to this vocabulary. Multi-valued

eduPersonPrimaryAffiliation

..... the individual’s predominant affiliation. What the institution would put on a person’s nametag. The value that appears here should also appear in the eduPersonAffiliation attribute.

Affiliation will be determined based upon data from source systems. (For example, at a rudimentary level, if the person’s data comes only from SIS, the person would be considered a student; if from HR, job class will be checked to determine if faculty or staff; if a person falls into more than one category, more complex logic will be required.)

Discussion Results

Draft CU-applicable affiliations are listed below. The list below also indicates whether the affiliate would be applicable for services and/or be included in query results and white pages lookups.

	Affiliation
DISPLAY/QUERY	Admitted Student è Confirmed Student è Parent? è ç Student è ç Staff è ç Faculty è ç Student Employee è ç Retiree è Employee Spouse è Alum è Sponsored è vendor? è contractor? è visiting faculty? è ç Directory-only Conference Attendee è	SERVICE

Additional considerations:

· We should add an attribute to indicate percent time for faculty/staff.

· How will we know if an individual should have service-specific privileges revoked (yet stay in the directory).

· Sponsor information should include who sponsored (currently carried in uniquid notes).

· Affiliates should carry an expiration date (not always needed but particularly applicable to some situations such as conferences).