Evergreen (software)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Evergreen
Evergreen (software) logo.jpg
Developer(s)Georgia Public Library Service (GPLS) Public Information Network for Electronic Services (PINES) and the Evergreen Community
Initial releaseSeptember 2006; 15 years ago (2006-09)
Stable release
3.6.2[1] / 18 February 2021; 15 months ago (18 February 2021)
Repository
Written inC, Perl, XUL, JS
Operating systemLinux
PlatformCross-platform
Available inEnglish
TypeIntegrated library system
LicenseGPL-2.0-or-later
Websiteevergreen-ils.org

Evergreen is an open-source integrated library system (ILS), initially developed by the Georgia Public Library Service for Public Information Network for Electronic Services (PINES), a statewide resource-sharing consortium with over 270 member libraries.[2]

Beyond PINES, the Evergreen ILS is deployed worldwide in approximately 1,800 libraries, and is used to power a number of statewide consortial catalogs.[3][4][5][6][7]

In 2007,[8] the original Evergreen development team formed a commercial company around the software, Equinox Software, which provides custom support, development, migration, training, and consultation for Evergreen. Equinox Software was later supplanted by the Equinox Open Library Initiative, a non-profit. As of 2014, several more companies and groups also provide support and related services for Evergreen.[9]

History[edit]

Evergreen was developed by the Georgia Public Library Service (GPLS) to support 252 public libraries in the Public Information Network for Electronic Services (PINES) consortium.[10] Development began in June 2004 when state librarian Lamar Veatch announced in an open letter that after reviewing options available, GPLS decided to develop its own library automation system. GPLS believed it could develop a system customized to fit its needs better at a lower cost than the fees currently being paid.[11] Programmers in the GPLS developed the project for two years, and PINES successfully completed the transition to Evergreen on September 5, 2006. In the next two years, the PINES consortium increased to over 270 libraries and five other systems in the United States and Canada implemented Evergreen.

The software started receiving contributions from other libraries and developers in 2007.[12] 2009 saw the first Evergreen International Conference.[13] In 2012, the community joined the Software Freedom Conservancy and formed an oversight board.[14] In 2019 the Evergreen Community elected an Evergreen Project board as part of their transition to a stand-alone non-profit organization.[15]

Other Evergreen implementations in North America:[16]

Features[edit]

Development priorities for Evergreen are that it be stable, robust, flexible, secure, and user-friendly.

Evergreen's features include:

  • Circulation: for staff to check items in and out to patrons
  • Cataloging: to add items to the library's collection and input information, classifying and indexing those items. Evergreen is known for an extremely flexible indexing system that allows for a high level of customization and by default uses Library of Congress MODS[19] as its standard.
  • Online public access catalog (OPAC): a public catalog, or discovery interface, for patrons to find and request books, view their account information, and save book information in Evergreen "bookbags." The OPAC received a makeover in early 2009 with the new, optional skin, Craftsman. There is also an optional Children's OPAC. Various patron services such as paying bills by PayPal and Stripe, optional retaining of circulation history, book bags and more.
  • Self Service - Evergreen comes with self checkout and registration options that can be activated by the libraries.
  • OPAC exposes structured web data by schema.org standards to aid discovery by major search engines.
  • Acquisitions: for staff to keep track of those materials purchased; invoices, purchase orders, selection lists, etc.
  • Authorities
  • Serials
  • Web based staff client that is OS independent
  • Added Content services Chillifresh, Content Cafe, Novelist, OpenLibrary and Syndetics natively supported with others supportable.
  • Native APIs for writing custom clients.
  • Statistical Reporting: flexible, powerful reporting for retrieval of any statistical information stored in the database.
  • SIP 2.0 support: for interaction with computer management software, self-check machines, and other applications.
  • Search/Retrieve via URL and Z39.50 servers

Evergreen also features the Open Scalable Request Framework (OpenSRF, pronounced 'open surf'), a stateful, decentralized service architecture that allows developers to create applications for Evergreen with a minimum of knowledge of its structure.[20]

Languages[edit]

The business logic of Evergreen is written primarily in Perl and PostgreSQL, with a few optimized sections rewritten in C. The catalog interface is primarily constructed using Template Toolkit with some JavaScript. The staff client user interface is written in Mozilla's XUL (XML + JavaScript) before 3.0 and is a web based staff client built using AngularJS and related technologies as of 3.0. Python is used for the internationalization build infrastructure. EDI functionality for the acquisitions system prior to 3.0 depended upon Ruby but no longer does.[21] AngularJS interfaces are now being transitioned to Angular and all new interface work is being done in Angular.[22]

Requirements[edit]

Evergreen runs on Linux servers and uses PostgreSQL for its backend database. The staff client used in day-to-day operations by library staff runs on Microsoft Windows, Macintosh, or Linux computers and is built on XULRunner, a Mozilla-based runtime that uses the same technology stack as Firefox and allows for a browser-independent offline mode. The online public access catalog (OPAC) used by library patrons is accessed in a Web browser. As of version 3.0 the web based staff client was promoted to production use and the XUL based staff client that required local machine installation began being phased out.[23]

Other open-source integrated library systems[edit]

See also[edit]

References[edit]

  1. ^ https://evergreen-ils.org/security-releases-evergreen-3-4-6-3-5-3-and-3-6-2/.
  2. ^ Weber, J (2006), "Evergreen: Your Homegrown ILS", Library Journal, vol. 131, no. 20.
  3. ^ "List of known sites running Evergreen", Evergreen ILS.
  4. ^ Michigan Evergreen, MLC net. Archived 2010-09-25 at the Wayback Machine
  5. ^ "Evergreen", Library, Indiana.
  6. ^ Sitka, British Columbia libraries. Archived 2008-04-18 at the Wayback Machine.
  7. ^ SCLENDS. Retrieved on 2017-04-14.
  8. ^ "About Equinox", Who we are, ESI library.
  9. ^ "Companies", Evergreen.
  10. ^ Breeding, M. (2007). Next-generation flavor in integrated online catalogs. Library Technology Reports, 43(4) 38-41.
  11. ^ Breeding, M. (2008). Major open source ILS products. Library Technology Reports, 44(8) 16-31.
  12. ^ Rylander, Mike. "Evergreen 2007". Equinox Software. Retrieved 10 November 2016.
  13. ^ Hamby, Rogan. "Evergreen 2009: Not Just Code". Equinox Software. Retrieved 10 November 2016.
  14. ^ Charlton, Galen (26 August 2016). "Evergreen 2012: ownership and interdependence". ESI library. Retrieved 10 November 2016.
  15. ^ "EOB minutes", Governance, Evergreen ILS, 2019-04-24
  16. ^ Open Source ILS Continues to Expand. ALA TechSource. Retrieved on 2013-08-29.
  17. ^ "NC Cardinal: sharing library resources and expanding opportunities". State library NC (2013-08-16). Retrieved on 2014-03-22.
  18. ^ PAILS, retrieved June 10, 2019.
  19. ^ "Mods", Standards, LoC.
  20. ^ "Frequently anticipated questions", Evergreen ILS.
  21. ^ "EG developer overview", Evergreen ILS.
  22. ^ "Angular JS to Angular migration", Evergreen ILS.
  23. ^ "3.0 development update 1", Evergreen ILS.
  24. ^ About BiblioteQ. Source forge. Retrieved on 2015-02-13.
  25. ^ About Opals. Opals NA. Retrieved on 2013-08-29.
  26. ^ FOLIO. Retrieved on 2020-03-03.

External links[edit]