Developing a Patron-Driven Acquisition Service at the University of Denver


Published on

ALCTS Acquisitions Managers and Vendors Interest Group. ALA Annual Conference, July 12, 2009.

Published in: Education, Business
1 Like
  • Be the first to comment

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

No notes for slide

Developing a Patron-Driven Acquisition Service at the University of Denver

  1. 1. ALCTS Acquisitions Managers and Vendors Interest GroupJuly 12, 2009<br />Michael Levine-Clark<br />Collections Librarian, University of Denver<br />Kim Anderson<br />Chief Bibliographer, Blackwell<br />
  2. 2. Developing a Patron-Driven Acquisition Service at The University of Denver<br />
  3. 3. Why Patron Driven?<br />No dead ends for patrons seeking information<br />Adds a just-in-time element to Collection Development<br />Reduces item cost per use<br />Integrates print and digital Collection Development<br />
  4. 4. Consortial Non-Use (1999-May 2008)<br />39.14% out of 278,650 titles<br />39.46% out of 129,914 titles<br />47.77% out of 208,248 titles<br />49.41% out of 348,181 titles<br />50.89% out of 67,250 titles <br />51.57% out of 116,799 titles<br />52.41% out of 55,848 titles<br />59.62% out of 133,645 titles<br /><ul><li> 34.52% unused
  5. 5. 2.44 copies per title</li></li></ul><li>University of Denver Data<br />1999-May 2008<br />208,248 titles (21,921 a year)<br />47.77% unused (99,480)<br />FY 2008<br />Approx $1 million spent on monographs<br />47.77% = $477,700<br />23,097 forms generated in FY 2008<br />4,687 titles ordered from forms<br />
  6. 6. The Universe of Titles<br />170,663 books published in the U.S. in 2008*<br />53,869 books treated on approval by Blackwell in FY 2008 (North America)<br />*Library and Book Trade Almanac 2009, p. 506 (preliminary data).<br />
  7. 7. Demand-Driven Purchase<br />E-Books<br />Humanities forms<br />No fiction, reprints, or textbooks<br />Discovery through the catalog<br />Dollar limits by patron type<br />POD<br />
  8. 8. The User Experience<br />Discovery (OPAC)<br />Print and/or ebook(s)<br />Request (OPAC)<br />Fast, seamless<br />Ordering<br />Alternative Sources<br />Rush (or not?)<br />
  9. 9. Questions<br />What is “just in time?”<br />How can we make print books and e-books work together?<br />How do we measure success?<br />
  10. 10. Profile Creation<br />Develop a separate profile area for Patron- Driven activity<br />Incorporate all existing forms subprofiles<br />Block fiction, textbooks, reprints, sets<br />Librarian selectors continue to receive their existing electronic forms notifications<br />Approval book profile remains in place and active<br />
  11. 11.
  12. 12.
  13. 13. Record Workflow<br />Patron Driven profile generates title matches<br />Blackwell creates a weekly file for FTP<br />DU loads the MaRC tagged records with profiling metadata to their OPAC<br />Patron can discover titles ‘available to order’ and create a request for print or ebook<br />
  14. 14. Order Workflow<br />Patron identifies the title and creates a request for e-book or print book by clicking a ‘buy’ button<br />Acquisitions reviews requests and sources the order with e-book vendor, Blackwell, or another print supplier<br />Patron is notified of title availability<br />
  15. 15. A New Approach to Pricing<br />Annual subscription fee for record creation<br />Small transaction fee for each title ordered <br />
  16. 16. Measuring Success with Patrons<br />Did the patron find titles to request?<br />What was the ratio of requests to title records loaded in the OPAC?<br />Did the patron find the request function understandable and easy to use?<br />Was the title provided when the patron needed it – What is “just in time?”<br />
  17. 17. Measuring Success in the Library<br />Did patrons create requests?<br />How did circulation of patron-requested titles compare to other titles added in the same time period?<br />How do patron-selected titles compare to librarian-selected titles?<br />What was the impact on acquisitions workflow?<br />Is this workflow scalable?<br />