Web Administration: Projects
Authenticated UF Phonebook field specification
Background
To comply with FERPA and other various statutes, the CIO has proposed updating the UF Phonebook. Under this proposal, a distinction will be made between queries made by the general public (i.e. anonymous users) and members of the UF community (e.g. faculty, staff, and students).
The proposed Phonebook will display fields depending on affiliation with the university. The current UF Phonebook displays many fields which will be removed from the view presented to the general public when this proposal is implemented. The Phoneobook application will continue to display information based on the data stored in the UF Directory and provided via UF LDAP. Individuals remain responsible for their specific data in the UF Directory.
Some individuals have statutory barriers to their data being available, including police officers and students who have requested Buckley Amendment protection. These individuals are said to have “legislative protection” privacy enabled, meaning their records are protected. The underlying UF LDAP system does not acknowledge the existence of protected records to any query without administrative privileges.
For acknowledged entries, a baseline set of fields will be presented, including name and official university contact information, but excluding the official email address. In addition, depending on the affiliation of the requester, some additional fields will be presented. For a more detailed presentation of fields available in UF LDAP, see the authenticated UF LDAP field specification.
Fields
The following fields will be provided:
| Target → / Requester ↓ | Faculty, staff, or employee | Student | Other affiliations |
|---|---|---|---|
| Anonymous user | (M) Baseline fields, (M) Primary email, (E) Other contact data | No data [1] | (M) Baseline fields, (M) Primary email, (E) Other contact data |
| Faculty, staff, or employee | (M) Baseline fields, (M) Primary email, (E) Other contact data, (E) Home contact data | (M) Baseline fields, (M) Primary email, (E) Other contact data, (E) Home contact data | (M) Baseline fields, (M) Primary email, (E) Other contact data, (E) Home contact data |
| Student | (M) Baseline fields, (M) Primary email, (E) Other contact data, (E) Home contact data | (M) Baseline fields, (E) Primary email, (E) Other contact data, (E) Home contact data | (M) Baseline fields, (M) Primary email, (E) Other contact data, (E) Home contact data |
| Other affiliations | (M) Baseline fields, (M) Primary email, (E) Other contact data | (M) Baseline fields, No additional data | (M) Baseline fields, (M) Primary email, (E) Other contact data |
Key:
- Baseline fields: name, official university contact information, and other fields, but excluding the official email address
- Target: the primary affiliation of the person whose data is returned by the query
- Requester: the primary affiliation of the requesting person
- Primary email: UF business email address
- Other contact data: mobile (cell) number, fax number
- Home contact data: home phone number, home address
- M = mandatory. Elective privacy no longer applies to these fields. The data in these fields will be published. Consider changes to the UF Directory and Gatordex to remove elective privacy flags from these fields.
- E = elective. Elective privacy applies as currently implemented in the UF Directory, Gatordex, and Phonebook. Users may elect to publish or not to publish the data fields via Gatordex.
Notes:
- For anonymous queries, any person with the affiliation of 'student' will not be included in the results.
- When a user logs in and views her own record, she sees all fields published to the UF LDAP system including those marked private in Gatordex. This is due to the nature of UF LDAP.
Affiliation:
Affiliation has a very precise meaning to the data systems of the university. A person may have more than one affiliation with UF recorded in the UF Directory. Only the primary affiliation is used to determine data presented in the Phonebook application. For this document, the term staff represents a primary affiliation of ‘staff’ or ‘employee’, and the term other represents a primary affiliation of ‘member’, ‘affiliate’, ‘alumni’, or ‘pre-applicant’. Additional information about affiliation can be found in the authenticated UF LDAP field specification.
Authenticated UF LDAP field group mappings
UF LDAP field groups have different meanings depending on the affiliation of subject. For students “official university contact information” typically means the local home information. For faculty, staff, and employees “official university contact information” is typically business information.
Baseline field set includes the UF LDAP field groups: infrastructure, administrative, basic person, official university contact, and POSIX account information.