Both Students and HR feeds display preferred names. The Name in Use (Preferred Name) Service allows students and employees to specify how their First and Middle names are displayed and modify the punctuation, spacing, and/or capitalization of your last name. If a student or employee had a legal name change which is not being displayed correctly in the White pages, please follow the instructions found in the following document: MyUW - Bug - Setting Preferred Name After a Legal Name Change

Use of the UW-Madison directory (White Pages) is restricted to single online look-up of individuals and departments. It is not intended or designed for large volume, bulk, reporting, or system authentication and/or authorization. The directory queries are monitored for misuse of the directory information and violators will be contacted. A persons listing in this directory does not necessary imply an official relationship with the University of Wisconsin-Madison.

Access Methods

• WWW
• LDAP
• PH
• Finger
• Whois

WWW

The directory is searchable via the World Wide Web at www.wisc.edu/directories/. For privacy, this interface does not display home address information. This interface does a lot of formatting in an attempt to make things simpler. Not all information is represented.

LDAP

The native format for the directory. Allows the most flexibility in formulating queries.

Hostname	ldap.services.wisc.edu
Port	389 (Standard LDAP Port)
Search Base	dc=wisc,dc=edu
Protocol Version	2 or 3

No bind DN or password is needed. Searches return 25 entries maximum.

Example (Using OpenLDAP ldapsearch on MacOS X, other ldapsearch implementations may have slightly different command-lines):

$ ldapsearch -h wisc.edu -x -LLL -b 'dc=wisc,dc=edu' 'cn=bucky badger'
dn: wiscEduEphemeralid=df30a14c4fffa0b518e074f2a30ec824,ou=people,dc=wisc,dc=edu
objectclass: top
objectclass: person
objectclass: organizationalperson
objectclass: inetOrgPerson
objectclass: wiscEduPerson
sn: BADGER
title: MASCOT
wiscedualltitles: MASCOT
mail: bbadger@wisc.edu
wiscedusearchgivenname: BUCKY
wiscedusearchgivenname: BUCKINGHAM
wiscedusearchgivenname: BUCKINGHAM U
ou: INTERCOLLEGIATE ATHLETICS
wiscedualldivisions: INTERCOLLEGIATE ATHLETICS
st: WI
wisceduallemails: bbadger@wisc.edu
wiscedudepartment: INTERCOLLEGIATE ATHLETICS
datasource: Payroll
wiscedusearchsn: BADGER
wiscedusubdept: INTERCOLLEGIATE ATHLETICS
l: MADISON
telephonenumber: (800) GO BADGERS
postalcode: 53711
physicaldeliveryofficename: CAMP RANDALL STADIUM
o: INTERCOLLEGIATE ATHLETICS
cn: BUCKINGHAM U BADGER
wiscedualldepartments: INTERCOLLEGIATE ATHLETICS
displayname: BUCKINGHAM U BADGER
street: 1440 MONROE ST
wisceduallsubdepts: MIDDLEWARE
postaladdress: 1440 MONROE ST$MADISON WI 53711
wiscedudivision: INTERCOLLEGIATE ATHLETICS
givenname: BUCKINGHAM U
wisceduallphones: (800) GO BADGERS
wiscedusearchcn: BUCKINGHAM U BADGER
wiscedusearchcn: BUCKINGHAM BADGER
wiscedusearchcn: BUCKY BADGER
wisceduworkemail: bbadger@wisc.edu
wisceduephemeralid: df30a14c4fffa0b518e074f2a30ec824

cn=bucky badger in the example ldapsearch command line above is actually an LDAP Search Filter, as defined in RFC 2254, and can be arbitrarily complex. For example, to search for the Bucky Badger in Athletics (if there were more than one "Bucky Badger" on campus):

$ ldapsearch -h wisc.edu -x -b 'dc=wisc,dc=edu' \
  '(&(cn=bucky badger)(wiscDduDepartment=INTERCOLLEGIATE ATHLETICS))'

Oracle has a detailed example in their ldapsearch documentation.

Be warned, however, that all attributes are not fully indexed, so your-milage-may-vary if you do not include an indexed attribute (cn, for example) in your search.

PH

A gateway provides CSO/Ph access to the data in the directory. Only the query interface is implemented, all other commands are ignored.

Hostname	wisc.edu
Port	105 (Standard Ph Port)

Example (using nph):

$ nph -s wisc.edu "bucky badger"@wisc.edu
nph: connected to PH server wisc.edu
nph: reading file /usr/local/etc/nphrc...

STATUS INFORMATION:

fake-ph.pl server fake-ph.pl v1.4 (r1.68.2.12)
Mo' betta data.
nph: matched 1 entry
----------------------------------------
ENTRY #1:
                name: BUCKINHAM U BADGER
            building: CAMP RANDALL STADIUM
          department: INTERCOLLEGIATE ATHLETICS
            division: INTERCOLLEGIATE ATHLETICS
               email: bbadger@wisc.edu
               phone: (800) GO BADGERS
               title: MASCOT
          work-email: bbadger@wisc.edu
        work_address: 1440 MONROE ST
                    : MADISON WI 53711
----------------------------------------

Finger

A gateway provides access via the Finger protocol, it is simply a gateway to the Ph query interface.

Hostname	wisc.edu
Port	79 (Standard Finger Port)

Example:

$ finger "bucky badger"@wisc.edu
102:There was 1 match to your request
-200:1:                name: BUCKINGHAM U BADGER
-200:1:            building: CAMP RANDALL STADIUM
-200:1:          department: INTERCOLLEGIATE ATHLETICS
-200:1:            division: INTERCOLLEGIATE ATHLETICS
-200:1:               email: bbadger@wisc.edu
-200:1:               phone: (800) GO BADGERS
-200:1:               title: MASCOT
-200:1:          work-email: bbadger@wisc.edu
-200:1:        work_address: 1440 MONROE ST
-200:1:                    : MADISON WI 53711
200:Ok.

Whois

A gateway provides access via the Whois protocol, it is simply a gatewy to the Ph query interface.

Hostname	wisc.edu
Port	43 (Standard Whois Port)

Example:

$ whois -h wisc.edu "bucky badger"
102:There was 1 match to your request
-200:1:                name: BUCKINGHAM U BADGER
-200:1:            building: CAMP RANDALL STADIUM
-200:1:          department: INTERCOLLEGIATE ATHLETICS
-200:1:            division: INTERCOLLEGIATE ATHLETICS
-200:1:               email: bbadger@wisc.edu
-200:1:               phone: (800) GO BADGERS
-200:1:               title: MASCOT
-200:1:          work-email: bbadger@wisc.edu
-200:1:        work_address: 1440 MONROE ST
-200:1:                    : MADISON WI 53711
200:Ok.

Note: whois "bucky badger"@wisc.edu also works on some platforms. Consult your whois manual for more information.