Integrated library systems and library services platforms

Reference article · 5 min read

Public libraries run on a system residents rarely hear named. The integrated library system, or ILS, holds the catalog, the patron file, and the circulation record, and it also carries money: orders, invoices, fund encumbrances, and subscription renewals. For a city, county, or district library it is the department's system of record, connected to finance, the identity directory, the public website, the self check machines in the lobby, and often a statewide resource sharing network.

The current generation of these products is usually called a library services platform, or LSP. An LSP is generally multi-tenant software sold as a subscription, with a vendor maintained layer of shared bibliographic and knowledge base data, and with print and electronic materials in one workflow instead of a separate electronic resource management module. Look past hosting and examine what changes in data access, reporting, and release control.

What separates an ILS from a library services platform

Upgrades. A traditional ILS may run on library servers or be vendor hosted, with upgrades the library schedules. An LSP is upgraded on the vendor's cadence for all tenants, so ask how much notice you get, whether a test tenant sees releases first, and whether you can defer.
Shared metadata. Most LSPs maintain a community zone of shared bibliographic records and electronic holdings, with a local layer for your holdings and edits. Be clear about which records you own outright and which you only link to.
Configuration instead of code. Direct database access generally goes away, and reporting shifts to vendor analytics and APIs. If staff rely on local SQL queries or scripts, plan replacements before cutover.

The data that has to move

Bibliographic and authority records. Catalogs are still built on MARC 21 under RDA cataloging rules, with linked data work under BIBFRAME advancing but not yet replacing MARC in production. Expect to clean local practice: nonstandard fields, duplicates, and headings that no longer match authority files.
Holdings and items. Call numbers, locations, item types, statuses, and the matrix tying borrower type to item type and loan rule. Open holds and items in transit need an agreed cutover approach.
Patron records. Barcodes, contact information, expiration dates, blocks, and balances. Decide deliberately what borrowing history moves. Most states have statutes protecting the confidentiality of library records, and their terms differ, so confirm the current rule with counsel and your state library agency.
Financial records. Open orders, encumbrances, invoices, and a fund structure mirroring the agency chart of accounts. Time cutover against fiscal year close so encumbrances do not land in the wrong year.

Circulation, acquisitions, and electronic resources

Circulation configuration is where policy becomes software: loan periods, renewal limits, holds and paging logic, notices, and fine or fee handling. Acquisitions runs on electronic ordering and invoicing with book vendors over EDI, on shelf ready processing profiles, and on funds the finance office recognizes. Electronic resource management adds license terms, activation dates, a knowledge base of subscribed titles exchanged in KBART format, an OpenURL link resolver, and COUNTER usage statistics, which SUSHI can harvest automatically.

The discovery layer patrons actually use

Staff modules and the public interface are different products even when sold together. The discovery layer indexes your catalog alongside a central index of article and ebook content, shows real time availability, and places holds.

Coverage. Ask whether the content you subscribe to is in the central index, and what a patron sees when it is not.
Accessibility. Ask for a current accessibility conformance report, then test the public interface with assistive technology rather than accepting the document at face value.
Privacy. Searches, saved lists, and personalization create records. Ask which third party analytics or advertising scripts the interface loads by default and whether they can be turned off.

Self check, RFID, and interoperability

Self check units, RFID pads, and payment kiosks generally reach the circulation system over SIP2, a de facto standard rather than a formal one. It predates modern security assumptions, so confirm how sessions are encrypted or tunneled and keep those devices on a segmented network. NCIP, a NISO standard, supports resource sharing and third party circulation. Z39.50 and SRU support catalog search and copy cataloging, and OAI-PMH lets a statewide service harvest your metadata. Ask which are native, which cost extra, and whether API calls are rate limited.

Shared and consortium catalogs

Many libraries share a catalog with neighbors, a county system, or a statewide network. Models range from a single shared tenant to separate systems joined by a union catalog and resource sharing protocols. The hard parts are governance rather than software: who may edit a shared record, whether loan rules are uniform, how floating collections and courier delivery are funded, and how costs shift when one member's usage grows. Put those terms in the joint agreement, with an exit provision stating what data a departing member takes.

What to ask for in the solicitation and the contract

Full export of bibliographic, holdings, patron, and financial data in standard formats, on request during the term and at termination, at no extra fee.
Documented APIs included in the subscription, with stated rate limits and notice before breaking changes.
Privacy terms: named subprocessors, data location, no secondary use of patron data, breach notice, and deletion at term end.
Migration scope in writing: test loads, field mapping responsibility, acceptance criteria, and the freeze window.
Pricing mechanics stated plainly, including what drives the fee and a cap on renewal increases.

HQT advises state and local agencies on system evaluation, integration, and data migration for enterprise applications, including library systems.

Frequently asked questions

What is the difference between an integrated library system and a library services platform?

An ILS is the traditional catalog, circulation, and acquisitions system, often installed on library servers or hosted by the vendor for a single customer. A library services platform is usually multi-tenant cloud software with a shared layer of bibliographic and knowledge base records, and it handles print and electronic materials in the same workflows. The practical differences show up in upgrade control, database access, and reporting rather than in the basic library functions.

What library data has to be migrated to a new system?

Bibliographic and authority records, holdings and item records, patron records, open holds, and financial data including open orders, encumbrances, and invoices. Each category needs field mapping, test loads, and acceptance review by the staff who use it. Decide early what borrowing history you intend to carry over, because retention choices interact with state law on the confidentiality of library records.

Will our self check machines and RFID equipment still work after a migration?

Usually yes, because most self check, RFID, and payment kiosk products connect over SIP2, which nearly every circulation system supports. Confirm the specific version and configuration, whether the connection can be encrypted or tunneled, and whether the new vendor charges extra for the interface. Test with the actual devices in a sandbox before go live rather than relying on a compatibility claim.

Are patron borrowing records protected when the catalog moves to the cloud?

State law, not the hosting model, governs the confidentiality of library records, and most states have statutes on the subject whose terms differ. Moving to a cloud platform does not change the obligation, but it does mean the contract has to carry it: no secondary use of patron data, named subprocessors, breach notice, and deletion at the end of the term. Confirm current requirements with your counsel and your state library agency.

Should our library join a shared or consortium catalog?

A shared catalog can lower per library cost, widen what patrons can borrow, and pool cataloging work, but it requires agreement on record editing, loan rules, delivery, and cost allocation. Review the governance documents before evaluating the software. Include an exit provision so a member that leaves can take its bibliographic, item, and patron data in standard formats.