The University of Texas at Austin- What Starts Here Changes the World
Services Navigation


About the Directory

The University of Texas at Austin White Pages Directory is an LDAP-enabled, universally-available directory published by Information Technology Services that contains public information on current students, faculty and staff.

Data in this directory is updated nightly. Student listings are obtained from the Office of the Registrar. Faculty and Staff listings are obtained from Human Resource Services (HRS).

Every effort has been made to make the contents of this Directory as up-to-date as possible. However, keep in mind that the publishers cannot and do not guarantee or assume responsibility for the following:

  • the complete accuracy of all the information found in the directory,
  • the complete absence of errors or omissions,
  • the presence of any unintentional directory entries.

For more information about this directory, please read our Frequently Asked Questions (FAQs) page which includes details about the information, how it is obtained, and the implementation of this service.


Copyright Information

The contents of this Directory are copyrighted by The University of Texas at Austin. By using the Directory, you agree that you will not reproduce, sell, transfer, or modify any of the information found in response to your search requests or use any such information for commercial purposes, without the prior express written permission and license of The University of Texas at Austin. Unauthorized use and/or abuse is subject to criminal prosecution under both state and federal laws. See also the University's copyright information.

This online directory service is provided by the University to facilitate the research, teaching, learning, and service missions of the University community. Solicitation on University computing and network resources is prohibited by the Rules and Regulations of the University of Texas Board of Regents. Accordingly, the contact information provided in this online directory service may not be used for transmission and distribution of unsolicited e-mail or other commercial purposes.

^Back to Top


Privacy Information

Student information provided in the Directory is based upon publicly available information and comes from the Office of the Registrar. Students may request that their own information not be released by the University. For more information, see Where does the data come from? and What are student privacy rights? on the Frequently Asked Questions page.

Faculty and staff information provided in the Directory is also based upon publicly available information and comes from Human Resource Services (HRS). Faculty and staff members may request that some of their own information not be released by the University. For more information, see Where does the data come from? on the Frequently Asked Questions page.

Security features have been implemented to prevent "trawling" of this Directory. These features may result in searching difficulties for users, but are intended to protect the privacy of University students, faculty, and staff.

See also the University's Web Privacy Policy.

^Back to Top


Systems Configuration

  • OpenLDAP 2.2.x - An open source Lightweight Directory Access Protocol (LDAP) directory server
  • Sun v440 servers with 4 1.2 GHz UltraSparc IIIi processors and 16GB RAM each

Two machines serve as directory servers. Queries coming in from the web gateway, finger gateway, and LDAP clients are balanced across these two machines.

^Back to Top


Directory Standards

LDAP is the standard for Internet directories and provides applications with a consistent view and access method. Standard LDAP schemas have been used where possible. This directory is fully compliant with the EduPerson v1.0 schema released by the Educause/Internet2 EduPerson Task Force. This EduPerson schema is designed to facilitate collaborative efforts across institutions of higher learning.

This Directory stores each person's record in a “flat and wide” schema and not an organizational structure. Access Control Lists are used to restrict access and visibility to records and attributes of students, faculty and staff who have requested such restrictions. The information in this Directory is updated only by an extract service from the Enterprise Directory and contains only information approved for public release.

This version of the Directory service includes a major upgrade to the internal directory software. Many things have been changed in the way the Directory is configured. Please let us know of any difficulties you encounter by sending e-mail to iadteam@lists.cc.utexas.edu.

There are a variety of methods to access the Directory. The most common is through our Web gateway. However, the Directory is also available via Finger and through the use of the Lightweight Directory Access Protocol (LDAP).

  • Web: http://www.utexas.edu/directory/
  • Finger: finger "john doe"@directory.utexas.edu
  • LDAP: various clients including e-mail clients and browsers such as MS Internet Explorer and Netscape
    • server: directory.utexas.edu
    • port: 389
    • base: dc=directory,dc=utexas,dc=edu
    • maximum entries returned: 50

^Back to Top


Ways to Search

The most basic way to perform a search is to type in a person’s name, e-mail address or phone number in the search box and then hit the ‘Search’ button. Queries are not case-sensitive. The Directory will attempt to match what you type with data that exists in the directory and display a list of relevant results.

Use the "All of UT" option to search the entire UT Austin directory. Because UT has a community of approximately 70,000 people, you may get back too many matches or you may hit search limits. (Search results are limited to 50 entries.) In those instances, you might try to make your query more specific or restrict the scope covered by your search to “Students” or “Faculty/Staff.”

Advanced Searches

The needs of most users will be met through a basic search. However, advanced searches may also be performed allowing users to employ an array of more sophisticated directory features.

Complex Searches

You can also create your own complex searches. The rules are as follows or just skip to the examples:

<filter> ::= '(' <filtercomp> ')'
<filtercomp> ::= <and> | <or> | <not> | <simple>
<and> ::= '&' <filterlist>
<or> ::= '|' <filterlist>
<not> ::= '!' <filter>
<filterlist> ::= <filter> | <filter> <filterlist>
<simple> ::= <attributetype> <filtertype> <attributevalue>
<filtertype> ::= '=' | '~=' | '<=' | '>='

The '*' character can be used to determine attribute existence or as a wild card. The '~=' causes sounds like matching.

Attributes types which can be searched for:

  • utexasEduPersonPubAffiliation (affiliation - student, faculty and/or staff)
  • cn (common name – first name last name)
  • givenName (given name - first name)
  • sn (surname - last name)
  • mail (electronic mail address)
  • telephoneNumber (office phone number)
  • utexasEduPersonOfficeLocation (office location)
  • homePhone (home phone number)

    For Students only:
  • utexasEduPersonClassification (classification)
  • utexasEduPersonMajor (major)
  • utexasEduPersonSchool (college/school)

    For Faculty and Staff only:
  • utexasEduPersonPrimaryTitle (job title)
  • utexasEduPersonHighestDegree (degree)
  • utexasEduPersonPrimaryOrgUnitName (organizational unit - department or college)

Examples:

This would match names sounding like "jane doe". Note, if there is a single attribute value assertion, then the outer '(' ')' are not required. Also, the “sounds like” uses a phonetic matching algorithm and may produce unexpected results.

This would search for all persons whose e-mail addresses started with "doe".

This would search for a freshman with "john" anywhere in their name (it would match first name Johnathan and last name Johnson).

This would search for someone whose last name is "Doe" and who has a home phone number ending in "3241".

This would search for someone whose name starts with "Jim" or "James" and is an "Accounting" major of some type.


Sometimes your search filter will not be detailed enough to get past the size limit (remember, with 70,000 people at UT Austin, you need to be specific). You may find the need to add additional distinguishing attributes to your search. For example, if you are only looking for students, limit the scope of your search to “Students.” It is best to put your most specific attribute furthest to the left, and least specific to furthest to right. Queries are evaluated left to right (parentheses do affect ordering) and the database has a limited number of hits it can store.

Pretty complicated huh? Well, it lets you ask some pretty complex questions. Remember, you can always just type what you are looking for in the search dialog and let the default filters attempt to find people for you.

^Back to Top


Known Issues

  • When a "size limit exceeded" response is received from a query, not all the search results have been returned to the user. There are too many matches to return. Receiving this message should be a user's cue to perform a more detailed search. However, users may be unaware that this is their next step.

^Back to Top


  Updated March 03 2008
  Send comments to help@its.utexas.edu or call (512) 475-9400
  Established August 24 1993