Evergreen (software)

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]

Evergreen
Developer(s)Georgia Public Library Service (GPLS) Public Information Network for Electronic Services (PINES) and the Evergreen Community
Initial releaseSeptember 2006 (2006-09)
Stable release
3.4 / October 2, 2019 (2019-10-02)
Repository
Written inC, Perl, XUL, JS
Operating systemLinux
PlatformCross-platform
Available inEnglish
TypeIntegrated library system
LicenseGNU General Public License
Websiteevergreen-ils.org

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. 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 in 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.[14]

Other Evergreen implementations in North America:[15]

  • Beauregard Parish Library (Louisiana, 6 branches)
  • BC Libraries Cooperative - Sitka (consortium of 92 multitype libraries, 150+ branches in BC and Manitoba)
  • Consortium Of Ohio Libraries COOL (11 libraries)
  • C/W MARS (Massachusetts, 155 libraries)
  • Evergreen Indiana (126 libraries)
  • Kenton County Public Library (Kentucky, 3 libraries)
  • King County Library System (Washington, 50 libraries)
  • Library of Virginia (Evergreen Virginia) (9 libraries)
  • Maine Balsom (10 libraries)
  • Michigan Evergreen (6 libraries)
  • Mohawk College Library (3 libraries)
  • NC Cardinal (North Carolina, 161 libraries and growing)[16]
  • Missouri Evergreen (29 Libraries)
  • Niagara Libraries (Ontario, 11 libraries),
  • North of Boston Library Exchange (NOBLE) (Massachusetts, 28 libraries)
  • North Texas Library Consortium (rural area outside Fort Worth, 17 libraries),
  • PaILS is the Pennsylvania Integrated Library System (ILS), over 100 libraries[17],
  • Pioneer Library System (Upstate New York between Rochester and Syracuse, 42 libraries),
  • Project Conifer (Ontario, 20 libraries)
  • Sage Library System (Northeast Oregon, 60 libraries)
  • SCLENDS (South Carolina, 72 libraries)
  • SPARK (Pennsylvania, 110 libraries and growing)
  • SPRUCE (Manitoba, Canada, 8 libraries)
  • Traverse Area District Library (Michigan, 6 libraries)

Features

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

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

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

Other open source Integrated Library Systems (ILS)
gollark: æ stupid embeds not working.
gollark: https://wikimedia.org/api/rest_v1/media/math/render/svg/9480572a575787e9ba36b2668328734298a421aa
gollark: WRONG! It is https://wikimedia.org/api/rest_v1/media/math/render/svg/9480572a575787e9ba36b2668328734298a421aa.
gollark: Wow, that's almost exactly what Wikipedia says.
gollark: I heard that tensors were things which transformed like tensors, but it wasn't very helpful.

See also

References
  1. http://lj.libraryjournal.com/2006/12/ljarchives/evergreen-your-homegrown-ils/ Weber, J (2006). "Evergreen: Your Homegrown ILS", "Library Journal", 131(20).
  2. http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen_libraries List of known sites running Evergreen
  3. http://www.mlcnet.org/cms/sitem.cfm/library_tools/michigan_evergreen/ Archived 2010-09-25 at the Wayback Machine Michigan Evergreen
  4. http://www.in.gov/library/evergreen.htm Evergreen Indiana
  5. http://sitka.bclibraries.ca/ Archived 2008-04-18 at the Wayback Machine British Columbia Sitka
  6. SCLENDS. SCLENDS. Retrieved on 2017-04-14.
  7. https://esilibrary.com/who-we-are/about-equinox/#sthash.BdYAzVBX.dpbs
  8. http://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_companies Evergreen Companies
  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. Rylander, Mike. "Evergreen 2007". Equinox Software. Retrieved 10 November 2016.
  12. Hamby, Rogan. "Evergreen 2009: Not Just Code". Equinox Software. Retrieved 10 November 2016.
  13. Charlton, Galen (26 August 2016). "Evergreen 2012: ownership and interdependence". esilibrary.com. Retrieved 10 November 2016.
  14. https://wiki.evergreen-ils.org/doku.php?id=governance:eob-minutes-2019-04-24
  15. Open Source ILS Continues to Expand. ALA TechSource. Retrieved on 2013-08-29.
  16. "NC Cardinal: sharing library resources and expanding opportunities". Statelibrarync.org (2013-08-16). Retrieved on 2014-03-22.
  17. According to PAILS website https://sparkpa.org/ retrieved on June 10th, 2019
  18. https://evergreen-ils.org/frequently-anticipated-questions/
  19. https://wiki.evergreen-ils.org/doku.php?id=eg_developer_overview
  20. https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:angjs_to_ang_migration
  21. https://evergreen-ils.org/evergreen-3-0-development-update-1/
  22. About BiblioteQ. biblioteq.sf.net. Retrieved on 2015-02-13.
  23. About Opals - Opals. Opals-na.org. Retrieved on 2013-08-29.
  24. FOLIO. Retrieved on 2020-03-03.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.