Cornell University Library Staff Web Page

Back to LMS Committee Page | StaffWeb Index

Library Management System Evaluation Committee

Why Replace the Current LMS?

We have long discussed a Single Point of Entry to Cornell's information space, digital and non-digital, and the need to integrate our services with the collection for a full-service digital library. A new LMS package might not solve all the design questions surrounding the SPOE, but it could move us significantly in that direction.

The new LMS should provide opportunities to improve the OPAC:

1. Obviate the technical constraints and policies imposed by NOTIS, including record length and display limits.
2. Provide flexibility for local customization and accommodation of new resources
3. Add new features long desired by staff and users, including location-based searching, and access to other databases and files.
4. Allow increased services to patrons, as well as friendlier interfaces

From a staff perspective, we desperately need a system that will:

1. allow full use of the information system capabilities, including the ability to provide reports without use of a programmer
2. provide improved processing and management of fund accounting and better control of income from various sources
3. provide individual password-based system security
4. allow electronic data interface with external vendors and systems as well as other university departments
5. provide "missing modules" such as bindery, a/v booking, as well as improvements in marginally functioning modules.
6. allow better automation of data import/export functions, as well as dynamic indexing of all records

In addition, we need to replace the current system to respond to the declining CIT support for legacy systems. Although CIT will gladly continue to support legacy systems, we might end up paying the entire bill which is now shared by all administrative systems. As more and more systems move off the mainframe computer the overhead cost per remaining customer goes up. This increased per customer cost is what is driving the loss of support for legacy systems. From the Library's point of view it would be horrific if we were the last mainframe customer and had to pay all the support costs. If the Libray can get equivalent computer support for the same money by buying new technology, then it is a good investment.

Also in decline is vendor support for a product with no current sales. This may be the most important reason to switch to a new system. After this summer's experience with implementing 6.2 and later 6.3.1, we have some serious concerns about Ameritech's continuing support. Ameritech/NOTIS was not immediately responsive to our needs nor were they able to consistently track reported problems. While the most egregious problems were resolved in 6.3.1, too many remain.Cornell has a world class library system and it should be running world class software to enhance the value of the library system. The library's computer systems are what the military would call a "force multiplier." It enhances the value of the physical library at a small cost compared to the cost of the library. If a modern system can be found that is at least functionally equivalent to NOTIS and that can support a library system as large as Cornell's, Cornell should switch systems.

In summary, we need to replace the current system in order to:

1. Reduce effort involved in individual tasks
2. Give CUL staff the tools to work most efficiently
3. Stop building "accessory" systems to do essential work
4. Control the ever expanding need for programmers
5. Respond to the declining
   1. CIT support for legacy systems
   2. Vendor support for a product with no sales
   3. Availability of programmers with obsolete skill set

Back to LMS Committee Page | StaffWeb Index

rev. 4/2/97 dih