Directory Services Update for IT Council, August 16, 2001

 

Accomplishments-to-date

·         Directory Services hardware is up and running.

o         “marquette" – registry machine

o         “leif” – directory query machine

o         “marcopolo” – directory applications machine

o         “meriwether” – replicated/backup machine

·         Human Resources System, Student Information System and uniquid data extracts are running regularly as is the process that logically builds attributes from source system data.  Testing is in process.  Some modifications continue to be made as issues are identified and resolved.

·         The Directory build process (building directory attributes from the registry database) has been programmed.  “Metamerge” is the tool used for this process.  It provides a mechanism for moving data from one format to another.  We hope to use this for other processes such as populating the Active Directory from the Enterprise Directory.

·         White pages programming (back-end and front-end) is almost complete.  Extensive testing will begin within the next two weeks.  We are using “Cocoon,” a web publishing framework that utilizes XML and XSLT stylesheets.

·         Data analysis of the completed registry and directory has uncovered many issues that are being addressed either through programming or through the Steering Team.  This analysis continues.

·         ACLs for anonymous query and authorized services have been defined and tested.  Refinement continues.

·         UMS is piloting a Systems Office instance of the directory using the Enterprise Directory’s schema, registry and directory build processes.

·         The Directory Project and the Printed Directory Project are collaborating to verify data and produce the individual listings for the 2001-2002 printed directory.

·         Meetings and presentations with various University and Campus groups have been held and continue to be held.  These include ITI, Library Deans, SIS Governance, Central Sys Ops Management (scheduled for 8/21), HR Council (scheduled for 8/17), TotalComm, IT Council, IT Support Community Event, Housing/BuffOneCard, Continuing Ed, ITS Senior Managers, etc.

·         Directory Policy has been written and approved by IT Council and the Chancellor’s Executive Committee.  (see http://www.colorado.edu/committees/DirectoryServices/)

·         Communication Plan has been written and is underway.

 

Open Issues and Challenges

·         Working with and cleaning up already-identified data problems.

·         Designing an ongoing process for data error resolution and correction.

·         Solidifying affiliation definitions.

·         Finding/hiring a Directory Manager.

·         Establishing a Directory Governance Board

 

On the Horizon

·         Go live of phase one:  tentatively scheduled for October 1 (Core Team and Steering Team have requested that implementation be no sooner than September 15th).

·         Subsequent phases will include:

o         Central authentication scheme

o         Additional data (building and room, building address, ISO, faculty research, faculty degrees)

o         Additional object classes (for example, organization)

o         Self-update

o         Directory framework for Calendaring

o         Directory enabled email

o         Directory framework for account management