1 / 20

Shared Library Management System

Shared Library Management System. Report on the RFI from the Shared ILS Team (SILST) Summer 2011. History and Context. Shared ILS discussion has deep roots Part of conversation since merger (2003) Shared ILS part of Strategic Agenda (2006)

beck
Download Presentation

Shared Library Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Shared Library Management System Report on the RFI from the Shared ILS Team (SILST) Summer 2011

  2. History and Context • Shared ILS discussion has deep roots • Part of conversation since merger (2003) • Shared ILS part of Strategic Agenda (2006) • First Shared ILS Team (2010) – total cost of ownership • Related to work of other committees • Exploration of emerging next gen systems • WSU Spokane/Riverpoint pilot of OCLC Web-scale Management Systems (WMS) • Open Library Environment (OLE) partner • Sage/Evergreen implementation • Shared ILS RFI (2011)

  3. Advantages of a Shared ILS • Shared database maintenance • Integrated consortial lending • Lower system administration costs • Potential for collaborative tech services • Collaborative collection development • Shared electronic resources management • Leading edge technology

  4. SILST – Charge and Timeline Charge: • Develop and issue a Request for Information (RFI), evaluate responses, and engage with respondents as appropriate to clarify and explore responses • Recommend a procurement process and timeline for a shared ILS • Develop an initial projection of staffing needs • Recommend next steps Timeline: • February 2011 Issue RFI • March 31, 2011 RFI responses due • June 10, 2011 Final report and recommendations due • July 13-14, 2011 Council votes on recommendations

  5. SILST Members John F. Helmer (Chair), Orbis Cascade Alliance Natalie Beach, Chemeketa Community College Beth Blakesley, Washington State University Rachel Bridgewater, Reed College Mark Dahl, Lewis and Clark College Bill Jordan, University of Washington

  6. Why an RFI? • RFI is intended to gather information to decide what action to take next • Not attempting to pick a vendor, but to determine current state of the market • Are there ILS vendors whose business and product plans, and strategic focus, intersect with the Alliance's Agenda? • Conversational and exploratory:  • "Here's where we want to go, how can you help us?" • "What have we missed?" • If we go to procurement, are we likely to get strong, viable responses from multiple vendors?

  7. Who Responded to the RFI Vendor [Product]: • ByWater Solutions [Koha] • Electronic Online Systems International [EOS.Web] • Equinox Software, Inc. [Evergreen] • Ex Libris(USA) [Alma] • Innovative Interfaces, Inc. [Sierra] • LibLime [ArchivalWare DLS/Koha] • OCLC Online Computer Library Center, Inc. [WMS] • Serials Solutions [Summon/360 Resource Management Consortium Edition] • SirsiDynix [Symphony] • The Library Corporation (TLC) [Library•Solution]

  8. What We Learned • Active and competitive market • Some alignment with Alliance goals: • Lowering total cost of ownership • Facilitating collaborative tech services • Wide variation in advancement level of products • New features/loss of old features • Development opportunities

  9. A Second Look…

  10. What We Wanted to Know More About • Cross system functionality • Summit • Collaborative tech services • Partners in related consortia • Funding • Implementation and timing

  11. Evergreen: “designed as a reaction to the limitations of then current integrated library systems for multiple library systems to share a common catalog” • Highlights: • Open source community development focus • "Equinox provides full-service implementation, support and development services as well as full training and consulting services migrating to Evergreen." • Traditional circulation, cataloging, acquisitions • Discovery, ERM not available at this time, but could be developed

  12. Alma: “a cloud-based, unified resource management system for print, electronic resources and digital collections” • Highlights: • Open data with “community catalog” • Streamlining workflows across resource types • Beyond MARC • Business analytics • Long-term preservation • Back office accompaniment to Primo discovery platform

  13. Sierra: “Sierra is the Open Services Platform that provides complete ILS functionality with the power and scale of modern software architecture.” • Highlights: • Open access/service oriented architecture/library choice • Trusted workflow • Enhanced administration and reporting • Quicker device adoption • Resource independence • Integration of print/electronic resource workflows • Developer community • Cloud or local deployment

  14. Web-Scale Management Services: “the first Web-based, cooperative library management service” • Highlights: • Scalable, Web-based platform for all basic library management functionality • Reduced Total Cost of Ownership (TCO)  • Platform for all types of materials, regardless of format or method of acquisition • Network effects, sharing data  • Concentrated data, bibliographic, item, vendor, and library registries and repositories • Sophisticated Service-Oriented Architecture (SOA)  • OCLC Cooperative Platform

  15. SILST Recommendations • Proceed with procurement • Alliance should lead procurement process (Model 1) Full Report: http://bit.ly/SILST-Rpt

  16. Next Steps • Council will consider SILST recommendations If approved: • Board forms a procurement team • Board acts on team's recommendations and may appoint a negotiation team • Board recommends next steps to Council • Final purchase decision made by Council

  17. Potential Timeline

  18. Unknowns and Challenges • Procurement and broad member involvement • Migration and staffing • Governance • Technical services • Systems support • Non-members

  19. Questions?

  20. Image Credits Slide #1 – Orbis Cascade Alliance, http://www.orbiscascade.org/index/name-and-logo Slide #3 – AnimationLibrary, http://www.animationlibrary.com/sc/259/Excitement/ Slide #5 – Paul Sherman, http://www.wpclipart.com Slide #10 – Clker.com, http://www.clker.com/clipart-15943.html Slide #11 – #15 a. OCLC, http://www.oclc.org/ (edited) b. Ex Libris, http://www.exlibris.co.il/ c. Equinox Software, http://www.esilibrary.com/esi/ d. Evergreen, http://evergreen-ils.org/ e. Innovative Interfaces, http://www.iii.com/ (edited) Slide #16 – Clip art licensed from the Clip Art Gallery on DiscoverySchool.com, http://school.discoveryeducation.com/clipart/clip/question.html Slide #21 – H. Varlan, http://www.flickr.com/photos/horiavarlan/4273168957/

More Related