Purpose
This document describes the data sources and algorithms used to compute the values of name attributes in Directory Services, including the Whitepages Directory and Person Directory.
Contents
Overview
Because there are several different use cases for name attributes, the values vary between directories services based on data source, algorithm, and intended uses. The current design (editor – or future; see status above) for computing values and publishing data has all data proxied to the directories through the Identity Registry, as it masters at least one of the attributes in the directories (editor – at least one of values?).
Data Sources
Source | Attribute | Format | Lifecycle | Notes |
---|
Workday | Legal Name | LAST, FIRST | Updates not provided after the employee separates | Maintenance: payroll coordinator or Payroll Office |
SDB | Legal Name | LAST, FIRST | Record updates are provided after the student stops attending | Maintenance: Registrar's office |
SDB | Directory Name | Last, First | Only provided when the student is registered | Normally is lower case version of Legal Name |
Identity.UW | Publish Flag | Y|N | Updates not provided after the employee separates | For directory data only. Additional directory publishing flags are not available in PDS or PWS but do affect the available Employee Whitepages data elements. |
SDB | Publish Flag | Y|N | Only provided when the student is registered | FERPA release flag: "student directory data" which includes of more student attributes than what is published in the directory |
VARIOUS | Legal Name | First (Middle) Last | Varies | As of 3/2015 Identity Registry supports 15 other sources of identity Data. |
Identity.UW or UW NetID Manage page | Preferred Name | First Middle Last | Once provided the user may update but not delete preferred name attribute | 3 Name parts |
Whitepages Directory
LDAP stores: ou=Students, ou=People, o=University of Washington, c=US
LDAP stores: ou=Faculty and Staff, ou=People, o=University of Washington, c=US
Records only appear in the above LDAP stores if the associated publishing flag is set. If an individual appears in both the attributes in each record are identical.
Attributes
cn - typically the person's full name
- Preferred First Name + Preferred Middle Name + Preferred Last Name
- Employee legal name in First + Last order (if published)
- Student whitepages name in First + Last order (if published)
givenName - holds the part of a person's name which is not their surname nor middle name
- Preferred First Name
- Employee legal first name (if published)
- Student whitepages first name (if published)
sn - the family name of a person
- Preferred Last Name
- Employee legal last name (if published)
- Student whitepages last name (if published)
Person Directory Service (PDS aka eds.u.washington.edu)
LDAP store: ou=People,dc=personregistry,dc=washington,dc=edu
Attributes
displayName - single field to represent the user (first last)
- Preferred First Name + Preferred Middle Name + Preferred Last Name
- Employee legal name in First + Last order
- Student whitepages name in First + Last order
- Registered Name Rollup
- First Active record in priority order
- First Inactive record in priority order
uwEWPName - Employee whitepages name (last, first)
- Preferred Lastname, Preferred First Name Preferered Middle Name
- Employee whitepages name: Last, First
uwSWPName - Student whitepages name (last, first)
- Preferred Lastname, Preferred First Name Preferered Middle Name
- Student whitepages name: Last, First
uwRegisteredName - Registered first name (first)
uwRegisteredSurname - Registered last name (last)
cn - Common Name (first last)
sn - Surname (last)
- First active Identity Registry record in priority order
- First inactive Identity Registry record in priority order
1 Comment
Eugene Sherman
Thanks, Eric! Very useful when we need to understand possible hiccup...