People OU - Staff

The campus Directory contains records for all active UC Berkeley personnel designated 'active' in the HCM system, including personnel on 'leave' and Emeritus faculty.

Authoritative Data for Staff

The campus Human Capital Management (HCM) system is the authoritative source of all employee data in LDAP. The campus Directory pulls data from HCM nightly.

Types of Employees

The CalNet Directory currently supports the following employee "roles":

  • Academic Employee
  • Staff

Account Creation - When do records enter LDAP?

  • Employees are added to the Directory the day after they are added the HCM system.
  • The Directory will pick up records for staff added to HCM a maximum of 3 month prior to the employee's start date.
  • Please note that the Directory does not pick up address information from HCM. Employees must update their own contact information in the Directory, including campus phone number, address, and working title.

Expiration - When do active staff records expire?

An employee's LDAP record expires 24 hours after the job record is terminated in HCM.

Grace periods - how long do records remain active after expiration?

Please visit the Grace Periods page for information on how long records remain in ou=people after a record is expired.

Staff affiliations - How to determine if someone is a staff member?

  • Please see the People OU Affiliations page for information on how to use LDAP affiliations to determine if a someone is an employee.
  • The Employee Criteria page also has information on verifying employee status in the Directory.

Public and Private Attributes

The CalNet team sets LDAP attributes as public or private in accordance with applicable requirements, such as the Federal Education and Privacy Rights Act (FERPA). Please visit the People Attribute Schema page for a table listing LDAP attributes, the data owner, and whether a particular attribute is public or private.

Sample LDAP Entries for Staff

Many UC Berkeley staff members have additional affiliations with the campus, such as a student or alumni affiliations. Please see the LDAP People Entry Structure page for samples of a person entry with multiple affiliations as well as information on staff address and job appointment sub-entries.
https://calnetweb.berkeley.edu/calnet-technologists/ldap-directory-service/how-ldap-organized/people-ou/people-ou-staff
calnetweb.berkeley.edu
crawl=CC-MAIN-2019-18
43002
application/http; msgtype=response
sha1:KFCGKYHH7TYNHC5UJ5PBTQVATI7RJVEQ
<urn:uuid:e2be48bd-ffff-432c-bdd5-a96d9dda68fc>
2019-04-18T19:11:04Z
23.185.0.1
text/html
sha1:446XAL3EFJ75ZU3TXQ5G6A7U6AGMBNSK
<urn:uuid:7098024d-d50f-4062-8a2a-b8f9f90ad9da>
https://calnetweb.berkeley.edu/calnet-technologists/ldap-directory-service/how-ldap-organized/people-ou/people-ou-staff
response
<urn:uuid:19effa21-480a-40d1-a771-c63e93d88064>
isPartOf: CC-MAIN-2019-18
publisher: Common Crawl
description: Wide crawl of the web for April 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-169-175-90.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/