Campus Directory Organizational Units (OU) and LDAP Structure

Data in the Campus Directory is divided into "Organizational Units" (OUs) based on function and/or purpose. An OU is also referred to as a "bucket," "branch," or "node."

Top-Level Directory Root

The OUs directly beneath the top-level Directory root or suffix entry "dc=berkeley,dc=edu" are:

Image-based organizational structure

People OU	ADVCON People OU (alumni)	PreSIR OU	Guests OU	Expired People OU
			Sponsored Guests Student-Delegates

Additional images of organizational tree

Applications OU	Org Units OU	Authorizations OU	Campus Groups OU

People (ou=people,dc=berkeley,dc=edu)

The 'people' branch contains all LDAP entries representing students, staff, and affiliates of the University of California, Berkeley. Please see the links below for details on how data is represented in LDAP for these groups:

• People OU - Students (KB0015478)
• People OU - Staff (KB0015674)
• People OU - Affiliates (KB0015670)
• Primary LDAP Person Entry Details (KB0015645)

PreSIR People (ou=presir people,dc=berkeley,dc=edu)

When do students move from the PreSIR OU to the People OU?

Students admitted for Fall move from OU=PreSIR People to OU=People two days after they submit the Statement of Intent to Register (SIR) and pay the fees online. If the student chooses to pay by check, the record will move to OU=People once the Admissions office has cleared the check. Spring students who enroll in the Fall Program for Freshman will also be moved to the PeopleOU once they are enrolled, subject to having paid fees as indicated above.

Advcon People (ou=advcon people,dc=berkeley,dc=edu)

The ADVCON OU contains records for people who have only alumni affiliations. Alumni affiliations are provided by University Development and Alumni Relations.

The data in the 'ou=advcon people' container is restricted. Developers wanting access to alumni information must request a Privileged LDAP Bind, and the request must be approved by University Development and Alumni Relations. If an alum has any other active campus affiliation (employee, student, etc), their record will be located in OU = People.

Guest OU (ou=guests,dc=berkeley,dc=edu)

Sponsored Guest data is stored in the campus directory (LDAP) and is therefore the authoritative source of all Sponsored Guest data. This OU is used to store users who are identified as short and long-term guests. Account information is added to the LDAP under ou=guests and is assigned the affiliate type: GUEST-TYPE-SPONSORED.

Available Guest Attributes

dn: uid=NNNNNNN,ou=guests,dc=berkeley,dc=edu
objectClass: berkeleyEduPerson
uid: NNNNNNN
berkeleyEduAffiliations: GUEST-TYPE-SPONSORED
displayName: MyUCB Guest
ou: guests

For information on eligibility, see: CalNet Sponsored Guests (KB0015299).

Expired People (ou=expired people,dc=berkeley,dc=edu)

The 'expired people' branch contains an archive of LDAP "people" entries representing individual users whose affiliation(s) with the University have completely expired. Once an expired user has exceeded their allowed "grace period," the entry is moved from 'ou=people' to 'ou=expired people' for archival purposes.

Applications (ou=applications,dc=berkeley,dc=edu)

The "applications" branch contains the privileged binds of services that have applied for special access to restricted Directory data. Developers may request a privileged bind by following the Applying for Directory Access (KB0015642) process.

Organizational Units (ou=org units,dc=berkeley,dc=edu)

The CalNet Directory includes a complete hierarchical representation of the entire UC Berkeley campus organizational unit structure. This information is accessed by privileged application binds. The data structure is refreshed nightly from the Enterprise Data Warehouse (EDW).

The entire Org Unit structure resides in the node ou=org units,dc=berkeley,dc=edu. This node serves as a container to encapsulate the entire structure within a logically named branch. Within this branch resides the ou=UCBKL Campus Root node, the base of the entire UC Berkeley Organizational Tree.

Each unit entry is based upon the berkeleyEduOrgUnit objectclass, which includes berkeleyEduOrgUnitProcessUnitFlag, berkeleyEduOrgUnitHierarchyString, and berkeleyEduOrgUnitParent.

Example Search Filters and Settings

Table displays example search and search-base details.

To search for...	search-base	scope	filter
All Process Units	ou=org units,dc=berkeley,dc=edu	subtree	(berkeleyEduOrgUnitProcessUnitFlag=*)
Units under 'VPUEI'	ou=org units,dc=berkeley,dc=edu	subtree	(berkeleyEduOrgUnitParent=VPUEI)
Units directly beneath 'VRIST'	ou=VRIST,ou=AVCIS,ou=UCBKL,ou=org units,dc=berkeley,dc=edu	one	(ou=*)