Evergreen (software) explained

Evergreen
Developer:Georgia Public Library Service (GPLS) Public Information Network for Electronic Services (PINES) and the Evergreen Community
Programming Language:C, Perl, XUL, JS
Operating System:Linux
Platform:Cross-platform
Language:English
Genre:Integrated library system
License:GPL-2.0-or-later

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.[1]

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

In 2007,[7] 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.[8]

History

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.[9] 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.[10] 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.[11] 2009 saw the first Evergreen International Conference.[12] In 2012, the community joined the Software Freedom Conservancy and formed an oversight board.[13] In 2019 the Evergreen Community elected an Evergreen Project board as part of their transition to a stand-alone non-profit organization.

Other Evergreen implementations in North America:[14]

Features

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

Evergreen's features include:

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.[19]

Languages

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.[20] AngularJS interfaces are now being transitioned to Angular and all new interface work is being done in Angular.[21]

Requirements

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.[22]

Other open-source integrated library systems

See also

External links

Notes and References

  1. .
  2. .
  3. . Web site: Archived copy . 2019-08-13 . 2010-09-25 . https://web.archive.org/web/20100925090927/http://mlcnet.org/cms/sitem.cfm/library_tools/michigan_evergreen/ . bot: unknown .
  4. .
  5. . Web site: Archived copy . 2008-04-23 . 2008-04-18 . https://web.archive.org/web/20080418180812/http://sitka.bclibraries.ca/ . bot: unknown . .
  6. http://sclends.org/ SCLENDS
  7. .
  8. .
  9. Breeding, M. (2007). Next-generation flavor in integrated online catalogs. Library Technology Reports, 43(4) 38-41.
  10. Breeding, M. (2008). Major open source ILS products. Library Technology Reports, 44(8) 16-31.
  11. Web site: Rylander. Mike. Evergreen 2007. Equinox Software. 31 May 2023. 19 November 2018. https://web.archive.org/web/20181119090827/https://esilibrary.com/evergreen-2007/. bot: unknown.
  12. Web site: Hamby. Rogan. Evergreen 2009: Not Just Code. Equinox Software. 31 May 2023. 16 June 2018. https://web.archive.org/web/20180616030316/https://esilibrary.com/evergreen-2009-not-just-code/. bot: unknown.
  13. News: Charlton. Galen. Evergreen 2012: ownership and interdependence. 31 May 2023. ESI library. 26 August 2016. 12 April 2018. https://web.archive.org/web/20180412145640/http://esilibrary.com/evergreen-2012-ownership-and-interdependence/. bot: unknown.
  14. http://www.alatechsource.org/blog/2011/04/open-source-ils-continues-to-expand.html Open Source ILS Continues to Expand
  15. https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
  16. .
  17. https://www.westchesterlibraries.org/about-wls/member-libraries/list-of-member-libraries/ "List of Member Libraries"
  18. .
  19. .
  20. .
  21. .
  22. .
  23. http://biblioteq.sf.net About BiblioteQ
  24. http://www.opals-na.org/ About Opals
  25. https://www.folio.org/ FOLIO