Category: ILS/LSP

eXtensible Catalog (XC) OAI Toolkit Released

The eXtensible Catalog project has released the eXtensible Catalog (XC) OAI Toolkit.

Here's an excerpt from the announcement:

The OAI Toolkit is used to make data stored in an institution's ILS or other repository available for harvesting via OAI-PMH, including other eXtensible Catalog applications. For an ILS, this is accomplished by exporting ILS metadata, converting it from MARC to MARCXML, and loading it into an OAI-PMH compliant repository. The repository (embedded in the OAI Toolkit) makes the data available for harvesting by other XC components.

The OAI Toolkit can be used as part of the XC system, or on its own to enable OAI-PMH harvestability of an existing repository. It is a server application written in Java and is only needed for ILS's and other repositories that do not already have the ability to be act as OAI-PMH Repositories (OAI Servers).

Digital Library Federation Releases ILS Discovery Interfaces Recommendation

The Digital Library Federation has released DLF ILS Discovery Interface Task Group (ILS-DI) Technical Recommendation: An API for Effective Interoperation between Integrated Library Systems and External Discovery Applications.

Here's an excerpt from the announcement:

This document recommends standard interfaces for integrating the data and services of the Integrated Library System (ILS) with new applications supporting user discovery. Such standard interfaces will allow libraries to deploy new discovery services to meet ever-growing user expectations in the Web 2.0 era, take full advantage of advanced ILS data management and services, and encourage a strong, innovative community and marketplace in next-generation library management and discovery applications.

A group of eight professionals from major North American research libraries prepared the recommendation during late 2007 and early 2008. Members of the group surveyed the library community about their needs, made presentations, and held open discussions face to face and online with librarians, developers, and vendors. The group made multiple recommendation drafts and other background information publicly available on the task group's Wiki, and invited comments and suggestions from interested parties.

In March, the DLF convened a meeting that brought together Task Group members and representatives of library system vendors and developers, and produced the "Berkeley Accord", an agreement about the most essential and feasible interfaces to include in an initial set of interfaces. This set of interfaces, called the "Basic Discovery Interfaces", is described in detail in the new ILS-DI recommendation. The recommendation also describes and recommends a variety of other functions to support higher levels of interoperability.

Digital Library Federation and 10 Vendors/Developers Reach Accord about ILS Basic Discovery Interfaces

Ten vendors and application developers have agreed to support standard ILS interfaces that will permit integration and interoperability with emerging discovery services. These interfaces will be developed by the Digital Library Federation's ILS-Discovery Interface Committee. The participants are AquaBrowser, BiblioCommons, California Digital Library, Ex Libris, LibLime, OCLC, Polaris Library Systems, SirsiDynix, Talis, and VTLS.

Here's an excerpt from the announcement:

On March 6, representatives of the Digital Library Federation (DLF), academic libraries, and major library application vendors met in Berkeley, California to discuss a draft recommendation from the DLF for standard interfaces for integrating the data and services of the Integrated Library System (ILS) with new applications supporting user discovery. Such standard interfaces will allow libraries to deploy new discovery services to meet ever-growing user expectations in the Web 2.0 era, take full advantage of advanced ILS data management and services, and encourage a strong, innovative community and marketplace in next-generation library management and discovery applications.

At the meeting, participants agreed to support a set of essential functions through open protocols and technologies by deploying specific recommended standards.

These functions are:

  1. Harvesting. Functions to harvest data records for library collections, both in full, and incrementally based on recent changes. Harvesting options could include either the core bibliographic records, or those records combined with supplementary information (such as holdings or summary circulation data). Both full and differential harvesting options are expected to be supported through an OAI-PMH interface.
  2. Availability. Real-time querying of the availability of a bibliographic (or circulating) item. This functionality will be implemented through a simple REST interface to be specified by the ILS-DI task group.
  3. Linking. Linking in a stable manner to any item in an OPAC in a way that allows services to be invoked on it; for example, by a stable link to a page displaying the item's catalog record and providing links for requests for that item. This functionality will be implemented through a URL template defined for the OPAC as specified by the ILS-DI task group.

Digital Library Federation ILS and Discovery Systems Draft Report

The Digital Library Federation's ILS and Discovery Systems working group has issued a Draft Recommendation investigating issues related to integrated library system and discovery system integration.

Here's an excerpt from the "Introduction":

This document is the (DRAFT) report of that group. It gives technical recommendations for integrating the ILS with external discovery applications. This report includes

  • A summary of a survey of the needs and discovery applications implemented and desired by libraries in DLF (and other similar libraries).
  • A high-level summary of specific abstract functions that discovery applications need to be able to invoke on ILS's and/or their data to support desired discovery applications, as well as outgoing services from ILS software to other applications.
  • Recommendations for concrete bindings for these functions (i.e. specific protocols, APIs, data standards, etc.) that can be used with future and/or existing ILS's. Producing a complete concrete binding and reference implementation is beyond the scope of this small, short-term group; but we hope to provide sufficient requirements and details that others can produce appropriate bindings and implementations.
  • Practical recommendations to encourage libraries, ILS developers, and discovery application developers to expeditiously integrate discovery systems with the ILS and other sources of bibliographic metadata.

White Paper on Interoperability between Acquisitions Modules of Integrated Library Systems and Electronic Resource Management Systems

A subcommittee of the Digital Library Federation’s Electronic Resource Management Initiative, Phase II has released White Paper on Interoperability between Acquisitions Modules of Integrated Library Systems and Electronic Resource Management Systems.

Here's an excerpt from the "Executive Summary":

The following white paper investigates interoperability between the acquisitions modules of integrated library systems (ILS) and electronic resource management systems (ERMS). The first section of the paper features four case studies: UCLA, Cornell University, the Tri-College Consortium of Bryn Mawr, Haverford, & Swarthmore Colleges, and the Library of Congress. Each case highlights the library’s institutional environment, consortium considerations, systems architecture (ILS, ERMS, and link resolver), and electronic resource workflows. . . .

The second part of the paper reports on conversations held with product managers and other relevant staff of the leading ERMS. . . .

The paper concludes with a recap of the general value of ILS/ERMS interoperability and some of the more significant barriers to achieving it. Finally, it is proposed that further discussions among stakeholders take place, and that these discussions focus on establishing agreement on a small set of elements for exchange and on the development of standard identifiers.

Evergreen 1.2.0 Released

Version 1.2.0 of the open-source Evergreen ILS software has been released.

Here's an excerpt from the Frequently Asked Questions:

From a library perspective, what does Evergreen do? What modules or components are available?

Evergreen currently has modules for circulation, cataloging, web catalog, and statistical reporting. Evergreen also supports the SIP2 protocol for self-check and Internet/computer access control.

What does it not do?

Evergreen's Acquisitions and Serials modules are currently under joint development with the University of Windsor. Other features on our roadmap include a Z39.50 server, and telephony and credit card support.