libraryOS

libraryOS is an open-source operating system designed to run library and information-management services. It provides an integrated platform for cataloging, circulation, digital asset management, and public access, with open APIs and a modular service architecture that can run on commodity hardware or in cloud environments. The project emphasizes interoperability with library standards and ease of deployment in multi-branch ecosystems.

History: The project began as a cooperative research effort by library consortia in the early 2010s, with public releases beginning around 2015. Development continues under the stewardship of the LibraryOS Foundation and an international community of libraries, vendors, and researchers. As of 2024, several major library deployments have migrated from traditional integrated library systems to libraryOS for core workflows.

Architecture and features: libraryOS uses a service-oriented architecture with a minimal kernel layer and isolated services. Core services include authentication and authorization, cataloging, acquisitions, circulation, digital object management, and a search/indexing service. Data is stored in a relational metadata store for MARC/Dublin Core mappings, while digital assets are kept in object storage. The platform exposes REST and GraphQL APIs, supports containerization with Docker/Kubernetes, and can be deployed in on-premises data centers or cloud environments. It emphasizes accessibility, multilingual interfaces, and granular permissions.

Standards and interoperability: libraryOS implements MARC21, Dublin Core, MODS, METS, and PREMIS for metadata and preservation metadata, along with Z39.50/SRU for discovery. It supports IIIF for images and manifests; authentication and identity management via OAuth 2.0, LDAP, and single sign-on.

Use and ecosystem: libraries deploy libraryOS to unify cataloging, circulation, and access services across branches. The project publishes release notes, contributes to community standards discussions, and maintains connectors to discovery layers and digital repositories.

Reception and outlook: Proponents cite streamlined workflows, stronger metadata consistency, and better long-term preservation; critics note setup complexity and a learning curve. Ongoing work focuses on cloud-native deployment, scalability, and expanding connector ecosystems.