Migration Management Group
17 May 00 (Final Version)

These requirements must be met for an LMS system to be considered by Yale University Library.

  1. The system is fully operational, i.e., all major library operations are supported including Acquisitions; Serials Control; Cataloging; Authority Control; Bibliographic, Holdings and Authority Record Export; Circulation and Course Reserves; the Online Public Catalog.
  2. The system has been fully operational throughout a semester and across a fiscal year in an academic research library within the United States that has a bibliographic database of at least 1 million records.
  3. A client base must exist within the United States or Canada. The client base must include major academic research libraries. Support offices must exist within the United States.
  4. The system must scale to 10 million bibliographic records, 2.0 million authority records, 1200 staff and public workstations.
  5. The system must by design provide 7x24x360 (i.e., 7 days/week, 24 hours/day, 360 days/year) online availability.
  6. System performance reliability in stable sites averages 99% of scheduled availability.
  7. The system must be capable of operating in and conforming to the requirements of DOD 5200.28-STD security level B2: (http://www.antionline.com/archives/text/rainbow_books/orange.html#HDR3.2). Conformance to security level B2 must include access controls incorporating public key infrastructure (PKI).
  8. The system must use a contemporary database management system. Oracle is the preferred RDBMS since it is the University standard.
  9. If custom client software is included with the system, it must run under Windows NT 4.0 or its successors.
  10. The system must include conversion programs for major NOTIS files.
  11. The system must provide a flexible development environment by providing APIs or source code to facilitate integration of: locally developed applications; third party software; web-based electronic resources; data exchange with external systems such as acquisitions vendors and bibliographic utilities; and interoperability with other Yale systems.
  12. The system must provide graphical, web-based interfaces and sophisticated Z39.50 services.
  13. Full support of all non-roman scripts is preferred, and some level of support must be operational. At least one non-roman script must be partially functional. Implementation must be Unicode based. Full functionality includes at least support of Japanese, Arabic, Chinese, Korean, Persian, Hebrew, Yiddish, and the ability to display, easily enter the script through the keyboard, search and index in the script. If full support is not yet implemented the vendor must demonstrate that full support is a high priority development project with a well-defined, credible implementation schedule.
  14. The system must compare favorably to current NOTIS system functionality.
  15. The system must maximize productivity for staff and readers. It must empower staff with self-service functions (e.g., report definition and generation) and productivity tools. It must empower readers through better searching tools and self-service functions.
  16. The system vendor must be willing to share its financial information and business plan with Yale University Library.


 Return to LMS Migration