Generated by GPT-5-mini| Koha | |
|---|---|
| Name | Koha |
| Developer | Wellcome Trust; MARC standards contributors; International Federation of Library Associations and Institutions |
| Released | 1999 |
| Programming language | Perl (programming language); SQL; HTML |
| Operating system | Linux; FreeBSD; Microsoft Windows (through virtualization) |
| Platform | Linux servers; Apache HTTP Server; MySQL/MariaDB |
| License | GNU General Public License |
Koha is an open-source integrated library system originally developed in the late 1990s that provides circulation, cataloging, acquisitions, serials, patron management, and reporting functions for libraries. It emerged from collaborative development motivated by practical needs within public and academic institutions and has since been adapted by a broad spectrum of libraries across continents. The software’s design emphasizes standards compliance, modularity, and community-driven governance.
Development began in 1999 when staff at Horowhenua Library Trust and contractors engaged with the New Zealand library sector to replace proprietary systems, drawing on practices from the Library of Congress and the British Library for cataloging standards. Early releases incorporated elements of the MARC standards and Z39.50 interoperability protocols used by the National Library of New Zealand and other national services. Community contributors included librarians and technologists from institutions such as the University of Canterbury and the State Library of New South Wales. Over time, stewardship shifted among various commercial service providers and volunteer groups similar to development models used by projects like Debian and Mozilla Firefox. Major milestones parallel broader open-source milestones exemplified by Red Hat and the Apache HTTP Server project, including formalization of release processes and internationalization efforts inspired by multicultural initiatives in Canada and India.
The system supports bibliographic workflows informed by Anglo-American Cataloguing Rules-era practice and integrates classification schemes like the Dewey Decimal Classification and the Library of Congress Classification. For metadata, it supports MARC21 and related formats used by institutions such as the National Library of Australia and the Bibliothèque nationale de France. Discovery functionality can be extended to provide OPAC interfaces compatible with protocols used by the OCLC network and regional consortia such as SIRSI Corporation-associated catalogs. Circulation modules implement patron policies modeled on public institutions like New York Public Library and academic practices seen at Harvard University and University of Oxford. Acquisitions and serials modules allow workflows found in systems adopted by the British Library and national consortia in Ireland. Reporting and analytics export to formats familiar to administrators at organizations such as the World Bank for grant reporting or cultural ministries in Germany and Brazil.
The core architecture uses a three-tier design comparable to stacks employed by projects like LAMP and MEAN (software stack), relying on Perl (programming language) for business logic, SQL databases such as MySQL or MariaDB for storage, and Apache HTTP Server or NGINX for delivery. Interoperability employs standards including SRU/SRW and Z39.50 to exchange records with systems at institutions like the Library of Congress and regional catalogues such as Europeana. Web interfaces are constructed with HTML and client-side scripting paradigms used by jQuery-based applications and modern RESTful APIs similar to those provided by GitHub and Twitter (service). Authentication and authorization options may integrate with identity providers such as LDAP directories used by universities including Stanford University and federations like eduGAIN. Scalability patterns mirror deployments at large consortia like DPLA and national libraries that adopt clustering and virtualization practices influenced by VMware and Kubernetes.
Deployments range from single-branch public libraries to multi-branch consortia resembling federations like Sierra (library system) networks and national programs in Estonia and Finland. Implementation projects often involve professional service firms, university IT departments such as those supporting University of Toronto libraries, and volunteer groups akin to contributors to LibreOffice and OpenStreetMap. The community organizes through mailing lists, issue trackers, and conferences similar to gatherings hosted by Eprints and Duraspace, while governance includes representatives from regional user groups modeled on the governance structures of Debian and Apache Software Foundation. Training and documentation have been produced by libraries and organizations comparable to INASP and regional library associations like the American Library Association.
Adopters include municipal and academic libraries, national bibliographic services, and consortia across Oceania, Europe, Africa, and the Americas. Prominent implementations have been reported in library networks comparable to those run by Auckland Council libraries, university systems similar to University of Waikato, and national projects paralleling initiatives in Iceland and Sri Lanka. Cultural institutions and special libraries with domain-specific needs—akin to those at the Smithsonian Institution and corporate archives like IBM Archives—have also used the system. Large-scale migrations to the software have been undertaken by consortia resembling regional clusters in Canada and national services in parts of Africa and Asia.
The project is released under the GNU General Public License, aligning its intellectual property model with projects such as Linux kernel and GNU Project software. Development follows a community-driven open-source model with contributions from commercial vendors, academic institutions, and volunteer developers similar to the ecosystems around PostgreSQL and phpMyAdmin. Release management and issue triage use practices established by projects like GitLab and GitHub while localization and translation efforts mirror the work seen in Mozilla Firefox and OpenOffice. This model enables vendor-neutral procurement and collaborative customization favored by public institutions including municipal administrations and university libraries.
Category:Integrated library systems