User Tools

Site Tools


zzz:evergreen_faq_1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
zzz:evergreen_faq_1 [2013/09/17 16:44]
roganh [12. What's the difference between Evergreen and PINES? What's GPLS?]
zzz:evergreen_faq_1 [2020/11/30 13:29] (current)
130.211.96.77 ↷ Links adapted because of a move operation
Line 3: Line 3:
 ===== Also see: ===== ===== Also see: =====
  
-  *[[faqs:Evergreen FAQ 2|Frequently Asked Questions about Evergreen'​s Features and Technical Infrastructure]] +  *[[zzz:evergreen_faq_2|Frequently Asked Questions about Evergreen'​s Features and Technical Infrastructure]] 
-  *[[faqs:Evergreen FAQ 3|Frequently Asked Questions about Open Source]] +  *[[zzz_archive:​faqs:evergreen_faq_3|Frequently Asked Questions about Open Source]] 
-  *[[faqs:Evergreen and Open Source Glossary]]+  *[[zzz:evergreen_and_open_source_glossary]]
   *[[faqs:​Evergreen Feature Request Procedures]]   *[[faqs:​Evergreen Feature Request Procedures]]
   *[[faqs:​Evergreen Roadmap]]   *[[faqs:​Evergreen Roadmap]]
Line 57: Line 57:
 ===== 6. So do I have to be a technical expert to use Evergreen? ===== ===== 6. So do I have to be a technical expert to use Evergreen? =====
  
-Evergreen requires at least some experience with administering a Linux server ​system.  Some libraries contract with [[faqs:​evergreen companies|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 requires at least some experience with administering a Linux server. ​ Some libraries contract with [[faqs:​evergreen companies|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! 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!
Line 82: Line 82:
  
  
-===== 13. What is the "​Evergreen Effect"?​ =====+===== 9. What is the "​Evergreen Effect"?​ =====
  
 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. 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.
  
  
-===== 14. I am interested in using a front end for our library system (sometimes called a discovery interface) ​such as Aquabrowser,​ WorldCat Local, Libraryfind,​ Bibliocommons,​ etc. Can I use one of these with Evergreen'​s back-end functions (cataloging,​ circulation,​ etc.)? =====+===== 10. I am interested in using a front end for our library system (sometimes called a discovery interface)Can I use one of these with Evergreen'​s back-end functions (cataloging,​ circulation,​ etc.)? =====
  
 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. ​ 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.
 +===== 11. How well does Evergreen integrate with other library vendor products? =====
  
-===== 15How well does Evergreen ​integrate ​with other library vendor ​products? =====+We welcome relationships with book vendors, enrichment vendors, and other servicesBecause ​Evergreen ​is open source and openly extensible vendors may find it easier to work with us than with proprietary vendors. ​ A 2010 survey'​s results are available here:  {{:​faqs:​evergreen-compatible_products.pdf|}} or here:  [[faqs:​evergreen_compatible_products_results_survey]] but the list of products ​libraries have used as Evergreen has grown is far too long to be maintained. ​ One vendor was having trouble integrating their enriched content with Evergreen but attended our first Hack-A-Way in 2012 and left with fully functioning code by their programmer being able to work directly with experienced community coders.
  
-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 [[http://​www.surveymonkey.com/​s/​8Z8Y69J|a survey]] of the Evergreen community to identify the products that are compatible with Evergreen. ​ Survey results are available here:  {{:​faqs:​evergreen-compatible_products.pdf|}} or here:  [[Evergreen Compatible Products Results Survey]]. ​ [[http://​www.surveymonkey.com/​s/​8Z8Y69J|The survey]] will remain open so that the community can continue to contribute. 
  
-===== 16. How is Evergreen different from other open source library software? ===== +===== 12. I have more questions... ====
- +
-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.  +
- +
- +
-===== 17. Is it true that... ===== +
- +
- +
-==== a. If I install Evergreen I have to maintain it myself? ==== +
- +
-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 [[faqs:​evergreen companies|an Evergreen support and development company]]. +
- +
- +
-==== b. I have to run Evergreen on a locally-installed server? ==== +
- +
-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). [[faqs:​evergreen companies|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.  +
- +
- +
-==== c. All libraries in an Evergreen system have to use the same policy? ==== +
- +
-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. +
- +
- +
-==== d. Anyone on the same Evergreen system edit a cataloging record? ==== +
- +
-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. +
- +
- +
-===== 18. I have more questions... ==== +
- +
-Please inquire on our [[http://​evergreen-ils.org/​listserv.php|mailing lists]]. If you're shy about posting to a public mailing list, you can send email directly to a few of the Evergreen developers at [[mailto:​feedback@evergreen-ils.org]] and we will get back with you promptly.+
  
 +Please inquire on our [[http://​evergreen-ils.org/​communicate/​mailing-lists|mailing lists]]. If you're shy about posting to a public mailing list, you can send email directly to a few of the Evergreen developers at [[mailto:​feedback@evergreen-ils.org]] and we will get back with you promptly.
zzz/evergreen_faq_1.1379450641.txt.gz · Last modified: 2013/09/17 16:44 by roganh

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.