Get Out Of The Frying Pan


Published on

Slides that accompanied a lively, hands-on session by Lori Ayre and Cheryl Gould at Evergreen International Conference 2009.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Get Out Of The Frying Pan

  1. 1. Get Out of the Frying Pan! Lori Bowen Ayre [email_address] Cheryl Gould [email_address] Evergreen Conference 2009 Athens, Georgia
  2. 2. but don’t get into the fire…
  3. 3. It’s cool that Evergreen is free and that you can see the source code. But.
  4. 4. The best part is…. you are in control
  5. 5. With an Open Source Library System…
  6. 6. You decide what gets built.
  7. 7. You decide how it works.
  8. 8. You decide how you work.
  9. 9. The All Powerful “Vendor”
  10. 10. Why it doesn’t work for us… <ul><li>Each product limited to one support option </li></ul><ul><li>market too small </li></ul><ul><li>built on old, nasty code </li></ul><ul><li>development is years behind need </li></ul><ul><li>data locked up </li></ul><ul><li>inflexible – too few customization options </li></ul>
  11. 11. [more]...why it doesn’t work for us <ul><li>RFP process doesn’t ensure libraries make the right choices </li></ul><ul><li>migration process is so horrific, there is no recourse once a move has been made </li></ul><ul><li>Standards issues </li></ul>
  12. 12. Learned Helplessness
  13. 13. Imagine if people working in libraries actually felt their ideas about how to do things made a difference?
  14. 14. Imagine eliminating “waste” (muda) of staff work effort Muda ( 無駄 ) is a Japanese term for activity that is wasteful, doesn't add value or is unproductive.
  15. 15. Imagine being able to optimize the user experience A Library Product:
  16. 16. Imagine being able to roll out a new service quickly! Sweet! My book is ready! “ Text-a-Circ”
  17. 17. Now is the time to take back the POWER we have ceded to the Vendors
  18. 18. Key to Firefox Success: Community Involement! <ul><li>Mozilla </li></ul><ul><li>Lessons Learned </li></ul><ul><li>Embrace the chaos and organize a chorus </li></ul><ul><li>Listen to your community </li></ul><ul><li>Lead your community </li></ul><ul><li>Let your community play and experiment </li></ul>37% of the code contributed to Firefox since November ’06 has come from the community
  19. 19. Evergreen is a work in progress. We need to help build it.
  20. 20. Ways to contribute to Evergreen Suggest improvements Increase participation Contribute new code Co-Sponsor development Develop documentation Organize Evergreen communities Do usability testing Manage communities of interest (e.g. customers, catalogers, circ staff) Identify inefficiencies Conduct user need assessments Optimize workflow Troubleshoot existing code Raise money Beta Test new releases Design screens Write specifications Create and test third party add-ins
  21. 21. Step One Stop talking about what The Vendor can do and start talking about what WE can do
  22. 22. More first steps… <ul><li>Encourage every user to think critically about how the software works – encourage them to imagine doing things differently </li></ul><ul><li>Provide a mechanism for exploring alternative approaches (what if we tried…..) </li></ul><ul><li>Capture good ideas and get them to your contributors and your developers </li></ul><ul><li>Develop new resource-sharing relationships with other libraries (people are resources too!) </li></ul>
  23. 23. The Beginning