LLMpediaThe first transparent, open encyclopedia generated by LLMs

Evergreen (ILS)

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Expansion Funnel Raw 90 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted90
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Evergreen (ILS)
NameEvergreen (ILS)
DeveloperEquinox Software, Pennsylvania Highlands Community College, Georgia Public Library Service
Initial release2006
Programming languageC, Perl, JavaScript
Operating systemUnix-like
LicenseGPL

Evergreen (ILS) is an open-source integrated library system originally developed for consortium-scale public library operations. It provides cataloging, circulation, acquisitions, patron account management, reporting, and interlibrary loan capabilities used by libraries, consortia, archives, and special collections. Evergreen has been adopted internationally and integrates with discovery layers, digital repositories, and preservation platforms.

Overview

Evergreen integrates core library services with cataloging standards and networked resource sharing, drawing on designs influenced by Carnegie Mellon University, Georgia Public Library Service, Pennsylvania Highlands Community College, Equinox Software, King County Library System, and Indiana State Library. Its architecture supports standards such as MARC21, Z39.50, SRU, HTTP, and SQL. Evergreen interoperates with discovery systems like VuFind, Blacklight, and Primo, and with digital preservation systems such as DSpace, Islandora, and Fedora (software).

History and Development

Development began when the Georgia Public Library Service commissioned a system to replace proprietary platforms used by the Georgia PINES consortium, with significant contributions from Equinox Software and academic partners at Pennsylvania Highlands Community College and Utah State University. Early pilots involved consortia including PINES and King County Library System, with codebases influenced by earlier systems such as Koha and enterprise solutions from SirsiDynix and Innovative Interfaces. Evergreen’s governance evolved through entities like the Evergreen Community, regional consortia such as Georgia PINES, Texas State Library and Archives Commission, and national projects funded by organizations including the Institute of Museum and Library Services and OCLC cooperative programs. Major milestones include releases that added SIP2 support for integration with systems deployed by Bibliotheca, implementation of ILS APIs to work with SIP2, and internationalization for consortia in Canada, United Kingdom, Australia, and New Zealand.

Architecture and Technical Features

Evergreen’s backend is a relational database-centric system typically using PostgreSQL with server components written in C (programming language), Perl, and JavaScript. It employs web servers such as Apache HTTP Server and nginx and integrates authentication with LDAP, CAS, and OAuth providers like Shibboleth and Auth0. Evergreen supports standards like MARC21, Dublin Core, Unicode, ISO 27001-compatible practices, and protocols such as Z39.50 and SRU/SRW. Scalability has been demonstrated with deployments using clustering technologies from Linux, FreeBSD, and containerization via Docker and orchestration with Kubernetes. Performance tuning often uses tools from pgAdmin, Nagios, Prometheus, and ELK Stack (Elasticsearch, Logstash, Kibana). Evergreen’s API endpoints allow integration with applications built on Ruby on Rails, Django, AngularJS, React, and Node.js.

Functionality and Modules

Core modules include cataloging compatible with MARC21 and authority control tools akin to those used by Library of Congress systems, circulation handling fines and holds similar to features in SirsiDynix Symphony and Innovative Sierra, acquisitions for vendor workflows like Baker & Taylor and EBSCO, and serials control supporting publishers such as ProQuest and Gale (Cengage) products. Evergreen supports interlibrary loan protocols used by OCLC WorldShare and union catalogs like COPPUL and CARL. Reporting leverages SQL queries and integration with analytics platforms including Tableau and Metabase. Patron services connect with authentication directories used by institutions like Harvard University, University of California, and public systems such as New York Public Library via protocols adopted by consortia including PINES and Prospector.

Deployment and Use Cases

Evergreen has been deployed by public library consortia, academic libraries, and special collections projects across regions including United States, Canada, United Kingdom, Australia, and New Zealand. Notable large-scale consortia implementations include Georgia PINES, King County Library System, and provincial projects inspired by networks such as BC Libraries Cooperative and Library and Archives Canada initiatives. Use cases span workload distribution for multi-branch systems, union catalogs for regional consortia, integration with digital repository platforms like DSpace and Islandora, and custom discovery experiences built with Blacklight and VuFind. Evergreen deployments often coordinate with local infrastructure providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform for hosting, backups, and disaster recovery.

Community and Governance

Evergreen is stewarded by a global community including developers from Equinox Software, regional library authorities such as Georgia Public Library Service, community contributors from institutions like Pennsylvania Highlands Community College, and users from consortia exemplified by PINES and others. Governance includes working groups inspired by models from organizations like Apache Software Foundation and Linux Foundation, and funding collaborations with bodies including the Institute of Museum and Library Services and philanthropic initiatives similar to Knight Foundation. Community communication occurs via mailing lists, issue trackers on platforms like GitLab and GitHub, and annual conferences modeled after gatherings such as Code4Lib and Open Repositories.

Category:Integrated library systems