Collaborating to ready evergreen for massachusetts libraries


Published on

Evergreen conference 2012 presentation on the three consortia participating in the MassLNC project.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Share decisions – Elizabeth’s talking points on shared decisions that needed to be made when consortia were forming and going through the same experience.Mutual support – sharing of scripts, testing acquisitions and serials.
  • Libraries are now empowered to make their systems what they want them to be. Constraints on funding, constraints on time, constraints on what the community thinks is useful. You can always customize it, but may not be able to make it part of core Evergreen. Or you can just do a new front end. And sometimes an enhancement isn’t needed; just learning a new way of doing things.
  • Not faulting the vendor, because if it is something that only fills the needs of a few libraries, it isn’t a wise investment to put that money into development. Network is empowered, but also greater responsibility in meeting members needs.
  • This is all good because in addition to taking control of are own systems, Massachusetts also has a strong voice in the community and whatever direction it may take.
  • Collaborating to ready evergreen for massachusetts libraries

    1. 1. Collaborating to Ready Evergreen for Massachusetts Libraries Kathy Lussier, MassLNC Project Coordinator Massachusetts Library Association Conference May 10, 2012
    2. 2. The Massachusetts Evergreen Project• What have the MassLNC consortia been doing for the past 2 years?• What does the switch to open source software mean for libraries?• Working with the greater Evergreen community.• MassLNC’s future
    3. 3. Background• Joint Application for $412,000 LSTA Grant. • C/W MARS • MVLC • NOBLE• Investigate and select a single open source Integrated Library System.• Jointly develop the system to better meet local needs.• Mutual support system.
    4. 4. MassLNC Libraries Go Evergreen• MVLC live on Evergreen since May 31, 2011.• C/W MARS and NOBLE going live on May 29, 2012.
    5. 5. A new model for collaborationaround Evergreen
    6. 6. MassLNC Pre-Migration Activities• Shared decisions• Mutual support• Shared development
    7. 7. Evergreen Development• Iterative process of identifying and prioritizing needs.• Monitoring of development from other Evergreen libraries.• Communication with Evergreen community about development plans.• Open RFP’s to find contractors.
    8. 8. Some MassLNC sponsored projects• Major cataloging enhancements.• Support for texting call numbers and hold notices.• Enhancements to Syrup academic course reserves systems.• Improved scoping in the public catalog.• General staff client improvements.• Improvements to the newly-developed acquisitions system.
    9. 9. Challenges• The public catalog was a moving target throughout the project.
    10. 10. Traditional Evergreen Catalog
    11. 11. New Evergreen Catalog
    12. 12. Challenges• The public catalog was a moving target throughout the project• Release schedules• Small vendor community
    13. 13. Highlights• Greater communication among 3 participating networks.• Working collaboratively with greater Evergreen community. • Development partnerships lead to greater savings.• Seeing wishes turned into functionality. • MVLC post-migration punchlist – 46 requests for enhancements; 25 have been addressed or are in the works.
    14. 14. What does the switch to open source software mean for libraries?• Libraries gain control over their systems • Functionality • Use of funds • Who supports the system• But there are constraints
    15. 15. Changing ways networks provide services• In the past, new ideas sometimes led to dead ends because a vendor was unwilling to make the necessary development happen.• Now, the decision lies in the network’s hands.
    16. 16. About the Evergreen Community• Evergreen is a member of the Software Freedom Conservancy. • Holds assets on behalf of Evergreen.• A two-year-old Oversight Board formed to safeguard and govern the interests of the larger Evergreen user and developer communities.• Maturing development cycles
    17. 17. Participation in the community• Community involvement is a key component to success with OSS. • For Evergreen support • For bug fixes & development • For building partnerships
    18. 18. MassLNC participation at all levels• Core Committer – Thomas Berezansky, MVLC• Chief Bug Wrangler – Jason Stephenson, MVLC• Evergreen Oversight Board member – Kathy Lussier, MassLNC• Various levels of participation in Documentation Interest group, Reports Interest Group, Cataloging Interest Group.
    19. 19. MassLNC’s Future• Business Planning Task Force formed to set future direction of project.• Opportunity to assess what is needed to support continued cooperation.• Will continue with central coordinator.• All networks committing funds to continue development.• New governance structure begins July 1.
    20. 20. Questions?