This is an old revision of the document!
Evergreen is an open-source, scalable integrated library system. Like many ILSes Evergreen features an online public access catalog and staff client. Features include circulation, cataloging, billing, reporting, acquisitions, serials and much more. As open source software Evergreen's features and support are driven by it's users.
Open source software is a term used for licenses that allow for copyright holders to allow their creations to be free to download, free to use, free to view, and free to adapt and improve. Evergreen is released under the GPL (GNU Public License) v2 and many of the documents associated with it are released under Creative Commons licenses. Community members are encouraged to give back to the community the benefits of their work if they build on top of Evergreen.
Open-ILS was an early name for the Evergreen project, and is still used internally in the software. The project website now uses evergreen-ils.org.
We have no idea. Evergreen grows every month with new installations and with no requirement that they centrally register we are always finding out about new and surprising places that Evergreen is used from large public libraries in the United States to small academic libraries in the middle east.
No. While Evergreen was designed for a large consortium, it is also implemented in single libraries. Evergreen's configuration allows for libraries with very flat structures (a single building) to complicated multi-system, multi-branch with sub branch organizations.
Because Evergreen can be used on one or more server "bricks" it means you can run a small library on a single brick or install more to support larger organizations. This also allows for the growth of libraries - the larger you get you can just add more bricks.
Evergreen requires at least some experience with administering a Linux server. Some libraries contract with a company that offers Evergreen support, development, migration, and other services for their Evergreen installations. Some libraries are fully hosted by commercial companies. Some libraries have implemented Evergreen entirely on their own and maintain their own installations. Some libraries perform their own data migrations and then contract with a company for support.
Evergreen also has a strong and growing developer community dedicated to its health and long-term sustainability. One Evergreen user even installed it to manage his home library!
In 2005, the library automation system for PINES, the lending network for Georgia Public Library Service (GPLS), was rapidly failing. GPLS and PINES approached other library software vendors, but every system evaluated, whether proprietary or open source, fell short in one way or another, usually due to fundamental design issues.
A few of the vendors GPLS met with admitted that they couldn't handle PINES' requirements, and didn't want to try.
GPLS decided that instead of pointing fingers at vendors or complaining about the limitations of legacy software, their developers would write the kind of system we want our users to experience. Since then, Evergreen has been expanded and redefined by a constantly growing community that still includes GA PINES among many others.
Early on, Evergreen's developers and stakeholders made a strategic decision that the new system would be owned and developed by the library community.
As librarians and library advocates, we believe in the power of information-sharing and openness. We believe that there should be an option for libraries to be self deterministic as an alternative to proprietary options and that the economic model provided by open source models works. We have watched our beliefs turn into reality as libraries from across the United States and Canada have contributed to the Evergreen project. As the community has grown and become invested in Evergreen the project has grown from scrappy start up to a large established and stable entity, just like a business with a large customer base. As every library improves the community experience - adding code, documentation, doing presentations, answering questions on online, we all benefit. There are a lot of ways to add value to the community and that is the purely selfish reason for open source - instead of paying dividends to a corporation our efforts go back into improving our own experience.
Libraries on large, shared Evergreen systems find that resource-sharing can significantly increase. We speculate this is because Evergreen was designed around the resource-sharing needs of very large consortia, making resource-sharing easier and more visible for users and librarians alike.
We welcome these partnerships! We wrote Evergreen so it would easily interface with other products, including catalog front-ends. Since our code is open source, there are no non-disclosure agreements to sign and no mysteries to the functions driving our interoperability, making it feasible to harness Evergreen's formidable strength to a wide variety of interfaces.
There has been interest in integrating Evergreen with products such as VuFind, Aquabrowser, WorldCat Local, Libraryfind, Bibliocommons, etc… These projects are driven by community members with an active interest so to find out the current status of these it's best to contact the community and find out if anyone (library or vendor) is currently maintaining such combinations.
We welcome relationships with book vendors, enrichment vendors, and other services. Because Evergreen is open source and our code is readily viewable, and because of our service-oriented architecture, vendors may find it easier to work with us than with proprietary vendors. In May 2010, Equinox Software, Inc. conducted a survey of the Evergreen community to identify the products that are compatible with Evergreen. Survey results are available here: evergreen-compatible_products.pdf or here: Evergreen Compatible Products Results Survey. The survey will remain open so that the community can continue to contribute.
Evergreen was designed from the ground up to meet the needs of a very large (more than 270-member) library lending consortium whose members collaborate but are not in lockstep on policies. Evergreen needed to be able to handle large indexing and transaction loads while supporting highly-configurable policies for each member library.
You can maintain it yourself (or more often, with a team of developers), but you do not have to. First of all, if you have installed Evergreen, you can turn to its development community for assistance. Second, you can also contract with an Evergreen support and development company.
If your consortium is providing Evergreen, all you will ever need to install locally is our friendly staff client (available for Windows, Mac, and Linux). Some companies also provide a hosted version of Evergreen for libraries that need or prefer to use an externally-hosted server and a very high level of external support.
On the contrary, Evergreen's elegantly rich permissions behavior can free your library from software-driven staff and user policies. Some libraries in Evergreen networks have elected to share similar policies for circulation, to make things easier for their users. However, you will find that the policy structure in Evergreen is flexible and powerful enough to handle almost any workflow configuration you could think up.
No, this is not true. While it would be possible to configure Evergreen this way, in practice, we don't know of any Evergreen system where "just anyone" can edit a cataloging record.