faqs:feedback_questions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faqs:feedback_questions [2011/08/18 21:27] – [I read on your website that someone used Evergreen in their personal/home library. How would I go about doing that?] phasefx | faqs:feedback_questions [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 4: | Line 4: | ||
- Evergreen will likely be overkill for your needs, but can be fun to play with. | - Evergreen will likely be overkill for your needs, but can be fun to play with. | ||
- Evergreen runs on Linux, so when it comes to system maintenance (performing upgrades, applying patches, backing up data, etc.), it would help to have some familiarity/ | - Evergreen runs on Linux, so when it comes to system maintenance (performing upgrades, applying patches, backing up data, etc.), it would help to have some familiarity/ | ||
- | - Evergreen was built by and for professional librarians, who have specialized jargon, workflows, and legacy data formats. | + | - Evergreen was built by and for professional librarians, who have specialized jargon, workflows, and legacy data formats. |
- There are single libraries that use Evergreen, but Evergreen was built for handling multiple libraries at once, and you can see that in the prevalence of library selector menus. | - There are single libraries that use Evergreen, but Evergreen was built for handling multiple libraries at once, and you can see that in the prevalence of library selector menus. | ||
- Items in Evergreen are typically barcoded, though you could just enter their titles if you don't need to track them physically. | - Items in Evergreen are typically barcoded, though you could just enter their titles if you don't need to track them physically. | ||
- | Disclaimers aside, probably the first thing you should do is download the staff client and connect to one of the [[community_servers|demo servers]]. | + | Disclaimers aside, probably the first thing you should do is download the staff client and connect to one of the [[:community_servers|demo servers]]. |
+ | |||
+ | |||
+ | |||
+ | ===== I was wondering what kind of programming skills are needed to develop the Evergreen ILS. What languages do you have to know and/or what software or other applications do people use to customize this ILS? ===== | ||
+ | |||
+ | Evergreen 2.1 and earlier (circa 2011): | ||
+ | |||
+ | The current OPAC makes heavy use of Javascript (including AJAX) and XML/ | ||
+ | |||
+ | See the page for [[dev: | ||
+ | |||
+ | |||
+ | ==== Wow--that' | ||
+ | |||
+ | The former. There are just a handful of [[contributing: | ||
+ | deep and wide understanding of Evergreen, and they funnel | ||
+ | contributions from others in the development community into what | ||
+ | becomes the " | ||
+ | found in that dev community; some are expert programmers just learning | ||
+ | Evergreen, others are novice programmers helping out with bite-sized | ||
+ | problems, and yet others help out in ways not involving " | ||
+ | all, whether with IT expertise, library domain knowledge, testing, | ||
+ | documentation, | ||
+ | |||
+ | > Would you be able to recommend a path to start learning more? | ||
+ | |||
+ | A disclaimer: you don't have to be a programmer or have programming | ||
+ | staff to use Evergreen, and there are other avenues for getting | ||
+ | customization done (such as hiring folks, or an [[faqs: | ||
+ | within the community to do work for you, or [[: | ||
+ | such that folks want to help you in kind--even simply opening bug | ||
+ | reports can instigate change). | ||
+ | |||
+ | That said, probably the best thing to do is to start by installing | ||
+ | Evergreen (a useful learning experience in and of itself). That can be | ||
+ | found here: http:// | ||
+ | |||
+ | Play with the software in the roles of admin, staff, and patrons, and | ||
+ | find something that gives you an itch to fix or improve. Create a | ||
+ | Launchpad ticket describing the problem and mention that you plan on | ||
+ | working on it (assign it to yourself). Then ask folks on the | ||
+ | OPEN-ILS-DEV mailing list, or on the #evergreen IRC channel, how you | ||
+ | might do that. Folks may point you to the exact file that you'd want | ||
+ | to tinker with, and give you pointers on how to test changes. You | ||
+ | don't have to be a master of Perl or Javascript before you dip your | ||
+ | toes in the water, but some familiarity with programming in general | ||
+ | won't hurt. | ||
+ | |||
+ | If you need to remain anonymous (maybe for fear of retaliation from | ||
+ | your current library vendor), there are ways to do that and still | ||
+ | participate in the community. You can ask at | ||
+ | feedback@evergreen-ils.org for advice in that regard. In general | ||
+ | though, it'd be nice if you just said Hi and introduced yourself on | ||
+ | the dev mailing list and/or in IRC. | ||
+ | |||
+ | Launchpad is our public bug tracker; you'll want to create an account for it: | ||
+ | http:// | ||
+ | |||
+ | Our mailing lists can be found here: | ||
+ | http:// | ||
+ | |||
+ | Information on the IRC chat here: | ||
+ | http://evergreen-ils.org/irc.php | ||
faqs/feedback_questions.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1