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

faqs:evergreen_faq_1 [2013/09/17 16:54] – [b. I have to run Evergreen on a locally-installed server?] roganhzzz:evergreen_faq_1 [2022/02/10 13:34] (current) – external edit 127.0.0.1
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 94: Line 94:
 ===== 11. How well does Evergreen integrate with other library vendor products? ===== ===== 11. How well does Evergreen integrate with other library vendor products? =====
  
-We welcome relationships with book vendors, enrichment vendors, and other services. Because 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:  [[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 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.
  
-===== 17. Is it true that... ===== 
  
 +===== 12. I have more questions... ====
  
-==== a. If I install Evergreen I have to maintain it myself? ==== +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.
- +
-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]]. +
- +
- +
- +
-==== 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. +
- +
- +
- +
-===== 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. +
zzz/evergreen_faq_1.1379451288.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.