All members present.

We discussed the David Ruddy's (Cornell) upcoming visit in connection with the DPubS project on May 18th. We are development partners for this project. Our agreement is to install the beta version of the software, mount some of our e-journal content using the software, and return a report on how the software compares with our experience using the Open Journal System publishing software. The anticipated production release of this publishing platform is late summer of this year. Jody asked whether we should appoint a project team for this "legacy" project. The consensus of the group was that this is not needed for such a limited activity and that a report to the DLSC would be adequate.

We returned to our conversation of a few months ago about how we might go about developing and implementing a content management approach as we redesign the library's web presence. The discussion was wide ranging and included the following points and questions:

• we need to educate ourselves about content management systems
• we may not need or want to implement a full-blown content management system at this point, rather we might just want to develop cascading style sheet(s) and consistent html coding standards. This could facilitate moving to a CMS at some future point, should we decide to do so.
• we need to research our options.
• we can get information from the web advisory committee of ALA about their experience.
• how would a CMS or taking a content management approach enhance the user's experience?
• how would we provide training for web editors?
• can we develop a consistent look and feel and information architecture for the libraries?
• would we sort through existing web pages (10,500+) or would we just start from scratch (most felt strongly that the latter approach is preferable).
• could we get a report on the decision processes of other ARL sites?
• can we get a report from our Heard Web site update project to help in these discussions?