Skip to end of metadata
Go to start of metadata

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

SourceAttributeFormatLifecycleNotes
WorkdayLegal NameLAST, FIRSTUpdates not provided after the employee separatesMaintenance: payroll coordinator or Payroll Office
SDBLegal NameLAST, FIRSTRecord updates are provided after the student stops attendingMaintenance: Registrar's office
SDBDirectory NameLast, FirstOnly provided when the student is registeredNormally is lower case version of Legal Name
Identity.UWPublish FlagY|NUpdates not provided after the employee separatesFor directory data only. Additional directory publishing flags are not available in PDS or PWS but do affect the available Employee Whitepages data elements.
SDBPublish FlagY|NOnly provided when the student is registeredFERPA release flag: "student directory data" which includes of more student attributes than what is published in the directory
VARIOUSLegal NameFirst
(Middle)
Last
VariesAs of 3/2015 Identity Registry supports 15 other sources of identity Data.
Identity.UW or UW NetID Manage pagePreferred NameFirst
Middle
Last
Once provided the user may update but not delete preferred name attribute3 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

  1. Preferred First Name + Preferred Middle Name + Preferred Last Name
  2. Employee legal name in First + Last order (if published)
  3. 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

  1. Preferred First Name
  2. Employee legal first name (if published)
  3. Student whitepages first name (if published)

sn - the family name of a person

  1. Preferred Last Name
  2. Employee legal last name (if published)
  3. 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)

  1. Preferred First Name + Preferred Middle Name + Preferred Last Name
  2. Employee legal name in First + Last order
  3. Student whitepages name in First + Last order
  4. Registered Name Rollup
    1. First Active record in priority order
    2. First Inactive record in priority order

uwEWPName - Employee whitepages name (last, first)

  1. Preferred Lastname, Preferred First Name Preferered Middle Name
  2. Employee whitepages name: Last, First

uwSWPName - Student whitepages name (last, first)

  1. Preferred Lastname, Preferred First Name Preferered Middle Name
  2. Student whitepages name: Last, First

uwRegisteredName - Registered first name (first)
uwRegisteredSurname - Registered last name (last)
cn - Common Name (first last)
sn - Surname (last)

  1. First active Identity Registry record in priority order
  2. First inactive Identity Registry record in priority order

1 Comment

  1. Thanks, Eric! Very useful when we need to understand possible hiccup...