Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
phasefx:faq [2014/05/21 10:14] – [6. How do I configure Evergreen?] phasefx | phasefx:faq [2020/12/02 04:40] – ↷ Links adapted because of a move operation 185.104.216.237 |
---|
====== Frequently Anticipated Questions ====== | ====== Frequently Anticipated Questions ====== |
| |
This is a work in progress. If you have suggestions or would like a wiki account to help out, please send an email to <docs@evergreen-ils.org>. The [[faqs:evergreen_faq_1|original FAQ's]] are still available. If you have questions not covered here, please see [[phasefx:faq#where_can_i_get_help_with_evergreen_have_questions_answered_etc|FAQ #2]]. :-) | This is a work in progress. If you have suggestions or would like a wiki account to help out, please send an email to <docs@evergreen-ils.org>. The [[zzz:evergreen_faq_1|original FAQ's]] are still available. If you have questions not covered here, please see [[phasefx:faq#where_can_i_get_help_with_evergreen_have_questions_answered_etc|FAQ #2]]. :-) |
| |
| **Update:** We've used what's here as the basis for a [[http://evergreen-ils.org/frequently-anticipated-questions/|top-level F.A.Q.]] menu entry under About Us on the website. |
| |
===== About Evergreen ===== | ===== About Evergreen ===== |
=== Scalability / Designed to handle complexity === | === Scalability / Designed to handle complexity === |
| |
Evergreen is a complicated piece of software, but that complexity allows it to handle and mask complexity in turn. It was originally designed for [[http://en.wikipedia.org/wiki/PINES|PINES]] which, by some measures, is one of the largest public library consortia. Organizational units (whether they be physical or abstract) can be expressed in a tree-like hierarchy, where policy and other information can be defined at specific org units and inherited by descendants in the hierarchy. Certain functionality also allows you to arbitrarily group org units and other entities outside of that hierarchy. | Evergreen is a complicated piece of software, but that complexity allows it to handle and mask complexity in turn. It was originally designed for [[http://en.wikipedia.org/wiki/PINES|PINES]] which, by some measures, is one of the largest public library consortia. Organizational units (whether they be physical or abstract) can be expressed in a tree-like hierarchy, where policy and other information can be defined at specific org units and inherited by descendants in the hierarchy. Certain functionality also allows you to arbitrarily group org units and other entities outside of that hierarchy. Hierarchies and inheritance also play a role with permissions. |
| |
Evergreen can scale to meet the needs of load and performance, and is built with a [[http://en.wikipedia.org/wiki/Service_oriented_architecture|service-oriented architecture]] that can be configured in [[http://en.wikipedia.org/wiki/Cluster_(computing)|clusters]]. It supported [[http://en.wikipedia.org/wiki/Cloud_computing|"cloud computing"]] before that became a buzz word. | Evergreen can scale to meet the needs of load and performance, and is built with a [[http://en.wikipedia.org/wiki/Service_oriented_architecture|service-oriented architecture]] that can be configured in [[http://en.wikipedia.org/wiki/Cluster_(computing)|clusters]]. It supported [[http://en.wikipedia.org/wiki/Cloud_computing|"cloud computing"]] before that became a buzz word. |