zzz:evergreen_faq_1
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faqs:evergreen_faq_1 [2013/09/17 16:44] – [12. What's the difference between Evergreen and PINES? What's GPLS?] roganh | zzz:evergreen_faq_1 [2020/11/30 13:15] – ↷ Links adapted because of a move operation roganh | ||
---|---|---|---|
Line 4: | Line 4: | ||
*[[faqs: | *[[faqs: | ||
- | *[[faqs:Evergreen FAQ 3|Frequently Asked Questions about Open Source]] | + | *[[zzz_archive: |
- | *[[faqs:Evergreen and Open Source Glossary]] | + | *[[zzz:evergreen_and_open_source_glossary]] |
*[[faqs: | *[[faqs: | ||
*[[faqs: | *[[faqs: | ||
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 | + | Evergreen requires at least some experience with administering a Linux server. |
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 " | + | ===== 9. What is the " |
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) | + | ===== 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' |
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, | 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, | ||
+ | There has been interest in integrating Evergreen with products such as VuFind, Aquabrowser, | ||
+ | ===== 11. How well does Evergreen integrate with other library vendor products? ===== | ||
- | ===== 15. How well does Evergreen | + | We welcome relationships with book vendors, enrichment vendors, and other services. Because |
- | 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, | ||
- | ===== 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), | + | |
- | + | ||
- | + | ||
- | ==== 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: | + | |
- | + | ||
- | + | ||
- | ==== c. All libraries in an Evergreen system have to use the same policy? ==== | + | |
- | + | ||
- | On the contrary, Evergreen' | + | |
- | + | ||
- | + | ||
- | ==== 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" | + | |
- | + | ||
- | + | ||
- | ===== 18. I have more questions... ==== | + | |
- | + | ||
- | Please inquire on our [[http:// | + | |
+ | Please inquire on our [[http:// |
zzz/evergreen_faq_1.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1