1 / 11

Directories in a Multi-Campus Environment Melissa Wauford, Jeanne Hermann University of Tennessee

Directories in a Multi-Campus Environment Melissa Wauford, Jeanne Hermann University of Tennessee. About UT. Campuses in Knoxville, Memphis, Chattanooga, and Martin Research Institutes in Knoxville & Tullahoma Satellite offices state-wide 44K Students & 15K faculty/staff. Environment.

teneil
Download Presentation

Directories in a Multi-Campus Environment Melissa Wauford, Jeanne Hermann University of Tennessee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Directories in a Multi-Campus EnvironmentMelissa Wauford, Jeanne HermannUniversity of Tennessee

  2. About UT • Campuses in Knoxville, Memphis, Chattanooga, and Martin • Research Institutes in Knoxville & Tullahoma • Satellite offices state-wide • 44K Students & 15K faculty/staff

  3. Environment • Separate IT organizations at each campus • Ongoing integration of IT organizations at Knoxville and Memphis • State-wide Financial/HR system • New SAP system implementation concurrent with directory development • Separate student systems for each campus (Knoxville and Tullahoma integrated)

  4. Directory Design Goals • Distributed directory that appears and behaves as a unified directory • Permit local administrative control of campus sub-trees • Uniquely identify each person state-wide • Reflect multiple campus associations to permit robust authorization services at the application level

  5. Namespace Design

  6. Unique Identifier (NetID) • Integrate state-wide HRIS with campus-based SIS data • Must be maintained centrally • Getting political buy-in from campuses • Distributed local NetID assignment • Support different longevity policies • Staff vs. student • Per campus

  7. Person Registry • “Thin” registry for NetID assignment • Name • ID numbers (including SSN) for matching • Web interface for campus-level lookup/update • Batch loading of data from HRIS and SISes

  8. Schema Design • person (locality attribute for office location) • inetorgperson • eduperson • tneduperson (tnstudentcampus, tnemployeecampus) • [campus]eduperson (campus SIS information)

  9. Multi-campus attributes • l (locality) • Office location (city) • Differentiate Memphis employee in Knoxville from Knoxville employee in Memphis • tnEmployeeCampus • Multi-valued to reflect split appointments • tnStudentCampus • Multi-valued to reflect students taking classes at more than one campus

  10. Issues • Out-of-the-box applications with limited authorization capabilities • “Search base” methods not able to handle multi-campus associations • Directory mastering • Currently using single-mastered server – move to multi-mastering? • Whose data wins when loading directory from, say, HRIS and two campus SISes

  11. References • Melissa Wauford <mwauford@utk.edu> • Jeanne Hermann <jhermann@utmem.edu> • Dewitt Latimer <dewitt@utk.edu> • tennessee.edu directory • LDAP lookup servers - ldap.tennessee.edu • User interface - http://www.utk.edu/ph

More Related