CUNY Unique Identifier Naming Convention
Total Page:16
File Type:pdf, Size:1020Kb
CUNY Unique Identifier Naming Convention The Enterprise Federated Directories working group, comprised of members of the Standards and Infrastructure subcommittees along with other technical experts from CIS and CUNY campuses, held its first meeting on January 12 and developed the following recommendation. The group recommends that the IT Steering committee adopt the following as the University naming convention for individual person account names: GivenFirstName.LastName<nnnn> GivenFirstName the individual’s full given first name as documented in official records. Required separator between GivenFirstName and LastName fields. If there is only one name, the period separator is not used. LastName the individual’s last name as documented in official records. <nnnn> an optional numeric value for resolution of identical GivenFirstName.LastName pairs across the university. The number begins at 1 with no leading zeros assigned to the first occurrence of a duplicate name pair and increments by one for each further occurrence of that name pair. Single Name: In the case of individuals with only one name, that name will be taken to be the LastName and the period separator will be omitted. Hyphenated Name: The hyphen character is allowed and will be included in the name field. Character Set: Only the hyphen and the period separator are supported. Other special (non-alphabetic or numeric) characters are not supported. The name fields can contain only lower-case alphabetic characters contained in the US- ASCII character set, plus the hyphen character. The numeric value suffix used to resolve namespace collisions can contain only the digits 0-9 Lower Case: Names will be represented in lower case characters. Length: Valid identifiers will have no more than 128 characters total length. Further Comments: The committee recognizes the desire to personalize identities and understands that individuals may wish to use an on-line identity other than the name resulting from applying the naming convention to official records. The committee anticipates the ability to create multiple unique alias identifiers for each individual as a technical means to address this desire and will include this feature in further specification of the Enterprise Federated Directory. .