“Evergreen (software)”的意思、由来-开放百科全书

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]

Features

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

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.^[16]

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 depends upon Ruby support but work targeting 3.0 or later will remove this to handle EDI generation natively.^[17]

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 due for release in late 2017 the technical preview of the web based staff client will be promoted to production use and the XUL based staff client that required local machine installation will begin being phased out. ^[18]

Other open source Integrated Library Systems (ILS)

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/ Michigan Evergreen
4. ^http://www.in.gov/library/evergreen.htm Evergreen Indiana
5. ^http://sitka.bclibraries.ca/ 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. ^{{cite web|last1=Rylander|first1=Mike|title=Evergreen 2007|url=https://esilibrary.com/evergreen-2007|website=Equinox Software|accessdate=10 November 2016}}
12. ^{{cite web|last1=Hamby|first1=Rogan|title=Evergreen 2009: Not Just Code|url=https://esilibrary.com/evergreen-2009-not-just-code|website=Equinox Software|accessdate=10 November 2016}}
13. ^{{cite news|last1=Charlton|first1=Galen|title=Evergreen 2012: ownership and interdependence|url=http://esilibrary.com/evergreen-2012-ownership-and-interdependenc|accessdate=10 November 2016|work=esilibrary.com|date=26 August 2016}}
14. ^Open Source ILS Continues to Expand. ALA TechSource. Retrieved on 2013-08-29.
15. ^"NC Cardinal: sharing library resources and expanding opportunities". Statelibrarync.org (2013-08-16). Retrieved on 2014-03-22.
16. ^https://evergreen-ils.org/frequently-anticipated-questions/
17. ^https://wiki.evergreen-ils.org/doku.php?id=eg_developer_overview
18. ^https://evergreen-ils.org/evergreen-3-0-development-update-1/
19. ^About BiblioteQ. biblioteq.sf.net. Retrieved on 2015-02-13.
20. ^About Opals - Opals. Opals-na.org. Retrieved on 2013-08-29.

External links

Evergreen source code repositories

"Evergreen: Your Homegrown ILS - An in-house team successfully competes with commercial vendors in the library automation sphere" Library Journal article

"Librarians stake their future on open source"

5 : Science software for MacOS|Science software for Windows|Linux library and information science software|Free library and information science software|Free software programmed in Perl