![Open Source Library System Software: Libraries Are Doing it For Themselves Lori Bowen Ayre [email_address] METRO Webinar October 13, 2009](https://image.slidesharecdn.com/ayreoslslibrariesaredoingitforthemselves-091023123035-phpapp02/85/Open-Source-Library-System-Software-Libraries-Are-Doing-it-For-Themselves-1-320.jpg)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (9)
Similaire à Open Source Library Software Help Libraries Take Control
Similaire à Open Source Library Software Help Libraries Take Control (20)
Plus de loriayre
Plus de loriayre (20)
Dernier
Dernier (20)
Open Source Library Software Help Libraries Take Control
- 1. Open Source Library System Software: Libraries Are Doing it For Themselves Lori Bowen Ayre [email_address] METRO Webinar October 13, 2009
- 2. Why are we here?
- 4. Diverse Customer Services Needed!
- 5. “ One of the great advantages of an Open Source Library System (OSLS) is the ability to empower staff and optimize the user's experience by getting involved in improving the software.”
- 6. Involvement = Write Code
- 7. “ Coding” is just one way to be involved… Increase participation Contribute new code Co-Sponsor development Develop documentation Organize Koha communities Do usability testing Create and test third party add-ins Manage communities of interest (e.g. customers, catalogers, circ staff) Write specifications Conduct user need assessments Optimize workflow Troubleshoot existing code Raise money Beta Test new releases Design screens
- 8. You decide what gets built. Write specifications Conduct user need assessments Co-Sponsor development
- 9. You decide how it works. Design screens Do usability testing
- 10. You decide how you work. Manage communities of interest (e.g. customers, catalogers, circ staff) Beta Test new releases Optimize workflow Design screens Conduct user need assessments
- 12. Step One: Read
- 16. Follow #koha on Twitter
- 17. Follow @esilibrary on Twitter
- 18. Step Two: Lurk * To lurk, joining is required
- 20. Koha Mailing Lists http:// koha.org /about/get-involved/mailing-lists/
- 24. Bug# 3342 Summary: Changes to holds priority list should be logged for accountability. Component: Hold Request Description: [ reply ] Opened: 2009-06-19 15:11 When a library staff member changes a hold priority or moves a hold up or down the list, the change information should be logged to encourage accountability. Log information should include: - Which user did it - Date/Time stamp - Which Patron was moved and to which priority. Reporter : Liz Rea < [email_address] > Assigned To : Galen Charlton < [email_address] >
- 26. Evergreen is still a tadpole…
- 27. Step 3: Test Drive
- 30. In case your head is exploding…..
- 31. Help is on the way!
- 39. Let me know how I can help! [email_address] (707) 763-6869 http:// galecia.com
Notes de l'éditeur
- 2 nd of 2-part series on OSLS Part 1 defined Open Source software licensing Open Source Library Software Examples
- our long-term goal provide services to our customers services they want and need Not easy to do when….<hands tied>
- working with our hands tied behind our backs Using software designed in the 80’s and 90’s Very few improvements have been made Not responsible to library requests for changes <and we need to make changes – diverse customers>
- many different needs to address Standards: children, literacy, lifelong learning, reading for enjoyment New needs: new Americans, baby boomers, Millennials, gamers How much of what you do involves using software? prevented from offering a service due to software? How easy is it to change procedures? OS software gives us the ability to control our environments.
- Quote from the description of this webinar We can do this because – with OSS - we have control over our own software environment When the software doesn’t support what we want/need to do, we can change it Focus today is on getting involved What’s that mean when talking about designing and supporting software?
- Getting involved is not just about writing code In fact, code writing is just a small part
- Write code Fundraise for development efforts Co-sponsor development (Liblime Development Exchange) Develop documentation or build a system of managing documentation Manage a Koha community (consortia…, large public libraries, small rural libraries, law libraries) Test release candidates Do usability testing - provide usability guidance Manage a community of interest (customers, catalogers, circ staff, acquisitions, serials, ILL/Resource sharing, digital asset managers) Create or test 3 rd party add-ins Optimize workflow (and suggest changes to the software that would support that) Troubleshoot existing code Write software specifications Identify what users needs (staff and the public) Design screens Get more people involved!
- Co sponsor development Conduct user need assessments Write specs
- Usability testing Design screens Write specs Decide what procedures need to be supported
- Conduct user need assessments Manage communities of interest Catalogers Customers circ staff Design screens Beta test Optimize workflow
- So, you think you might like to get involved in an Open Source Library System project?
- If you do nothing else…. Sign up for the Koha and Evergreen general discussion lists <more things to check out>
- Koha Mailing lists: General bugs Developers Patches Translations zebra Windows users Portuguese community Brazil community French, German, and Spanish Lists
- General Documentation planners, technical writers, trainers, documentation contributors, etc. participating in or interested in following the progress of the Evergreen documentation project. Technical Discussion List patches and technical discussions Evergreen SVN commit list This list tracks the full diff of every commit to the Evergreen Subversion repository.
- Koha uses bugzilla (as to many other open source projects) to… <interesting to poke around bugzilla>
- Reported: owen of nelsonville public Assigned to: french developer Paul Poulain Summary Comments (can be several)
- Note the “component” field Here a NEKLS library staffperson addresses the Hold functionality Release Manager (Galen) gets assigned to work on it <more on Holds>
- Create you own custom reports to track something specific I created report of Holds Related Enhancement Requests Who’s involved Status of requests Who’s doing what When will it get done (next release? On hold? Unassigned? Need more info?) <head exploding?>
- Not quite as many things going on with Evergreen Newer, just launched in 2007 Still a tadpole (with forelimbs) – not metamorphosized yet You’ll know when it has matured into a full adult open source project when there is a place for the community of users and the community of developers to interact more directly. One ways this is done is via “bugzilla”
- You can hire a commercial service provider to help you with the “getting involved” part.
- Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?
- Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?
- Sure commercial service providers are nice Familiar model “The Vendor” But…other models…
- Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?
- PINES did the impossible – created their own ILS SITKA took what PINES did and expanded on it, build a support organization Michigan created an opportunity for the willing NEKLS established a resource sharing and support organization around Koha NYS Boards of Cooperative Educational Services did the same with OPALS What about us?