Shared E-books from Coast to Coast: Consortial Programs in Florida and the Pacific Northwest
•Descargar como PPTX, PDF•
0 recomendaciones•672 vistas
Sadie Williams (speaker)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (10)
Destacado
Destacado (18)
Similar a Shared E-books from Coast to Coast: Consortial Programs in Florida and the Pacific Northwest
Similar a Shared E-books from Coast to Coast: Consortial Programs in Florida and the Pacific Northwest (20)
Último
Último (20)
Shared E-books from Coast to Coast: Consortial Programs in Florida and the Pacific Northwest
- 1. The Orbis Cascade Alliance 37 academic libraries in ID, OR, & WA – – – – – – – – 6 community colleges 16 private 4-year colleges 14 public 4-year colleges (large & small) 1 Health Sciences institution Total FTE: 258,000 9.2 million titles/28.7 million items Robust interlibrary request/delivery (Summit) Funded by membership dues
- 2. Cooperative Vision & E-books? Strategic Vision: “Many libraries, one collection” • YBP ‘preferred vendor’, enabling sharing of acquisitions information up-stream • Shared ILS will take this vision to next level BUT • Individual libraries purchasing single e-book titles or collections • These e-books not available to other Alliance library users
- 3. Program Milestones 2010 -Ebook Team formed; EBL and YBP recommended as DDA partners Jan-June 2011 • 15 publishers sign up • YBP profile set up (all subjects; $250 cap) • Workflows mapped for discovery options • Training for public & tech service staff July 2011 – LAUNCH!
- 4. Funding • All members participate • Initial funding model patterned on Alliance dues model; later changed to 30% even split/35% FTE/35% materials budget • FY 2012 ($462K) • FY 2013 ($750K) • FY 2014 ($1M) • No increase expected in FY 2015 FY12 FY13 FY14 FY15
- 5. DDA Model • Users discover DDA titles in their local catalog, or the Alliance Group Catalog • Free browse for 5 minutes • A Short Term Loan (STL) occurs if the title is used > 5 minutes, or copy/printing content • STL is a “rental” averaging 14% of list • Title is purchased when a predetermined number of STLs occur; there is a negotiated consortial multiplier (5) • STL trigger can be adjusted (we have gone from 5 to 15), or autopurchasing can be suspended
- 6. Some Statistics (July 2011-June 2013) • 13,608 titles available to users (19,500 at highest count) • ~ 200 new titles added per week • 1,079 titles purchased • 18,222 titles were accessed 265,584 times (this includes free browsing) • 14,601 titles had 118,692 STLs (incl. owned loans) • % of titles with STLs: FY2012 – 49%; FY2013 – 77% • Average # of STLs per title: FY2012 – 2.54; FY2013 – 2.69 • FY2013 STLs (~70K) = 25% of all Summit loans • $1,182,902.48 spent
- 7. From the beginning • • • • YBP selected as Orbis Cascade’s preferred vendor in 2007 Present at ebook discussions from 2009 forward Participated in vendor selection process Orbis Cascade program first consortial DDA program for YBP
- 8. Beyond title profiling • YBP developed profile for DDA title pool working with members of the ebook team • Provided data used in vendor selection process • Provided data used to negotiate multiplier • Continue to provide purchasing history data • Developing new tools to support consortial projects
- 9. Individual library support • Assist libraries in preventing duplication between DDA and approval or firm ordering • Coordinate approval and DDA coverage • Provide consortial purchase history • Provide full scope of publication information, including print, ebook and DDA availability
- 10. New GOBI consortial display
- 11. Getting Started Identified a model Identified a multiplier Built platform support for model Publisher negotiations Target DDA pool size & settings
- 12. Ongoing Support Workflow support Recommend adjustments to settings Usage reports Continuing discussions with publishers
- 13. Current EBL & ebrary Solutions for Consortia 30 programs live in North America LIBRARY Multiplier Limited Loans Easy DDA LIBRARY Act Collectively Spend Separately CONSORTIUM Retrospective DDA LIBRARY LIBRARY Multiplier/Limited Loans
- 14. Lessons Learned
- 15. Challenges • • • • • • Range of experience with ebooks & DDA among libraries Technical issues Access for non-affiliated users not feasible Publishers can change prices, terms on titles Equitable funding formula Controlling costs
- 16. #1 Challenge: GROWING THE PROGRAM IN A STEADYSTATE FISCAL ENVIRONMENT
- 17. What’s Next? • Continue or modify current model? • Eliminating content not under consideration • Looking at access-weighted options for Business/Management, Computer/IT subjects • Explore alternative/additional models? • Shared ownership continues to be strong value • Adjust funding formula to normalize cost-per-use outliers? • Do not want to disincentivize use
- 18. Thank you! For more information, visit the Alliance Ebook Working Group page at www.orbiscascade.org/index/orbis-cascade-alliance-ebookworking-group Linda Di Biase ldibiase@uw.edu Joan Thompson jthompson@ybp.com Jim Bunnelle bunnelle@lclark.edu Sadie Williams sadie.williams@proquest.com
- 19. Considerations for a Consortia Model Publisher Diversity Access or Ownership Size and Budget of Participating Libraries Content Interest Overlap Time and Staff to Manage System Requirements
Notas del editor
- My name is sadiewilliams and I worked with Orbis Cascade during the last two years of their program. Linda asked me to give a brief overview of our role I’ll also talk about the role that Orbis has played as a first step for a number of new consortia modelsOrbis was the first shared-access DDA program at EBL and really a pioneer in helping us develop our consortia ebook models.Once EBL was selected as an aggregator, we worked withOrbisCascde to understand their goals and develop a model that fit. As Linda mentioned, shared ownership and collection building was a high priority. At the time, any consortia ebook model available did not remotely fit their goals. EBL worked closely with Orbis cascade to identify what was important to them, what model they could support and build a model that would not only fit them, but something we felt publishers would accept to some extent – knowing we’d have to start with a pilot.. Once we decided on using the multiplier model in combination with DDA, we had to identify th multiplier. Orbis used the data from YBP to show that they on average had purchased just above 3 copies. Initially they thought a multiplier of 3 would fit. But, given that 1.) Not all libraries use YBP and 2.) The nature of a shared print book and a shared ebook was fundamentally different and a shared ebook access a consortia with multiple users give you siginicantly more convenience and reduce in costs and 3.) they were purchasing in combination with DDA/STLS we proposed going to publishers with a multiplier of 5, which we thought would be reasonable for both Orbis and for publishers.Although print data is useful in some cases, as more and more libraries move toward e. publishers have asked for different data and we’ve developed different models for calculating a multiplier as needed.We discussed their needs in terms of workflow support and reporting up front and altered our platform to support their goals including real=time detailed reporting center at the consortia level and library level. We set up authentication so each institution could use their own authentication method and use single-sign un with university login if set up.At the same time we were altering the platform, we started publisher negotiations. As __ said, it is a long process. We didn’t have any back and forth, but stuck to what we felt was a good multiplier. A key point in the relationship with publishers working with Oribs is that we offer usage and expenditure data back to the publishers for this program as well as information about non consortial purchases of their books which in many cases grew, as individual libraries added their own ebook and DDA programs. We worked to identify target size for their initial pool of records. For individual libraries, we use averages to predict spend, which generally proves to be quite accurate. With orbis, we had no similar size institutions so we couldn’t use regular averages to predict spend and had to do some educated guessing when identifying size of the pool. The first year was a bit rough with many changes but by the second year we had a much smoother situation.
- On going supportWe have worked very closely with Orbis and OCLC to develop two separate workflows. An initial workflow included WCP and then a second utilized the OCLC Knowledge base. We also recommend adjustments to their profile as we watch expenditures over time. Often doing calculations to predict spend through the year and figure out if they need to raise or lower trigger.
- As I said before, Orbis cascade was really the jumping point for us in terms of consortia models. We now have 30 programs live in N. America across ebl and ebrary. Ebrarybegain with a model very similar to the orbis model as well – although we were not yet “partners.None of our 30 programs are alike and most are uniquely different. Our goal has been to work with each consortia to develop a model that fits them or alter an existing model to fit their needs.