Developing a Demand-Driven Acquisitions Plan: A Library-Vendor Collaboration

Developing a Demand-Driven Acquisitions Plan: A Library-

Vendor Collaboration

Michael Levine-Clark, University of [email protected]

Patricia Smith, Colorado State [email protected]

Kim Anderson, [email protected]

mailto:[email protected]








Why Demand-Driven Acquisition Makes Sense

University of Denver Data

• 1999-May 2008

– 208,248 titles (21,921 a year)

– 47.77% unused (99,480)

• FY 2008

– Approx $1 million spent on monographs

• 47.77% = $477,700

University of Denver Data (2)

• Books Published 2005-2009: 89,496 Titles

– 0 Circulations: 47,257 (52.80%)

– 1 Circulation: 21,810 (24.37%)

– 2 Circulations: 9,809 (10.96%)

– 3 Circulations: 4,816 (5.38%)

– 4 Circulations: 2,484 (2.78%)

– 5+ Circulations: 3,320 (3.71%)

The Universe of Titles

• 170,663 books published in the U.S. in 2008*• 53,869 books treated on approval by Blackwell in

FY 2008 (North America)• 23,097 forms generated in FY 2008

– 4,687 titles ordered from forms

*Library and Book Trade Almanac 2009, p. 506 (preliminary data).

Everything is Different

• Users expect everything instantly

• Born-digital books won’t go out of print

• We’re more accountable to our administrations

– Budget

– Shelf space

Developing a DDA Plan for DU

• Jan 2009: Begin conversations with Blackwell

• Spring 2009: Begin conversations with EBL

• Summer/fall 2009: EBL/Blackwell platform development

• Dec 2009: YBP/Blackwell announce merger

• Jan 2010: Begin conversations with YBP

• Spring 2010: Implement DDA with EBL

• Spring 2010: Plan DDA with YBP

How We’re Implementing Demand-Driven Acquisition

The University of Denver Plan

• Program will begin July 2010• Print and Electronic Books• YBP and EBL• Forms

– No fiction, reprints, or textbooks– Discovery through the catalog

• POD (eventually)

• Automatic approval books will continue to come automatically

The User Experience

• Discovery (catalog)

– Print and/or ebook(s)

• Request (catalog)

– Fast, seamless

• Ordering

– Baker & Taylor and Alternative Sources

– Rush (in some cases)

– Drop Ship (in some cases)

Demand Driven Acquisitions

Developing the profile for University of Denver’s Demand Driven

Acquisitions Program

Some Considerations for DDA

Mediated or non-mediatedMediated: patron requests go to acquisitions staff, who make

final decision on whether title gets ordered, fund availability, format in which title is ordered

Non-mediated: patron request is ordered immediately

Budget control – monitoring so funds are available for duration of program or fiscal year

Print books or eBooks, or both?

Some Considerations for DDA

How long will MARC records stay in OPAC? -How do we remove them?-Will selectors review before removal to order any that users

didn’t want?

Reports-Which users requested what (how much, and in what

subject areas)?

Mirror existing approval plan profile, or set up a separate profile?

What universe of titles shall we expose to patrons?

• Subject areas

• Publishers

• Non-Subject Parameters

• How far back shall we go

YBP Acquires Blackwell in December 2009

Different procedures, different technology partners, and new resources require rethinking the plan

YBP offers ‘Patron Choice’ Service for Print Material

‘Patron Choice’ is…

• Mediated or unmediated patron choice acquisitions

• For print and/or electronic books

• Full or brief catalog records available to import

• Titles (records) profiled using current or separate approval plan profile

– All subjects or some subjects

• Duplication control across other YBP accounts

• Separate subaccount(s) for patron-driven purchases

Four sites so far, each different…

• UCLA– Five plans that augment existing approval plans

• University of Vermont– Three publishers - Oxford University Press, Palgrave

Macmillan, and John Wiley

• University of Kansas– Separate profile for selected

subjects, Engineering, Education & Political Science

• CARLI-academic libraries in IL– Books published between November 1, 2008 and October

31, 2009 – Priced at $300 or less & currently in stock at YBP

What does ‘demand-driven’ mean? There are many possibilities

• YBP provides the titles & catalog records– Profiled each week from approval plan

– Loaded in a batch based on a title list

• Library loads records into catalog– Full (OCLC Plus service from YBP)

– Brief on-order records

• OPAC button for users to request the book be purchased– Log in required

– Options available to user (rush, normal, notify, don’t notify?)

• Acquisitions retrieve patron-choice requests daily & place orders– Mediated or un-mediated

UVM’s ‘Get This Book” Service

After finding a title, UVM users must log

in before they can submit a request

KU uses special location for Patron Choice titles

Full record in KU OPAC

Identifier in catalog

record so Patron

Choice records can

easily be removed

after 6 months

KU Workflow for Patron Choice

START : Slips are generated using the Patron Driven Profile and and loaded into the OPAC every week

using YBP/OCLC Cataloging Plus

In the OPAC the Patron Driven records are

identifiable by containing a ‘Request’ button

Patrons choose when they need the title (one of the four

delivery methods)

Acquisitions goes in and searches selections at a

scheduled time each afternoon

Acquisitions either orders it via

RUSH, regular delivery, or an eBook

based on criteria KU has established

Acquisitions receives the title, processes it

(if needed) and notifies the patron of

its arrival FINISH : Records will be deleted from the OPAC once they’ve

been in there 6 months – selectors will review

at this point

‘Yesterday, Today was Tomorrow.’- Billy Joe Shaver

Implications

Assessment

• Feedback Form (p)

– At Request

– At Delivery

• Slip “Ordering” (p)

• Use Data (p and e)

Impact on Researchers

• Can they

– Browse the collection?

– Get books as needed?

– Get older books?

Impact on Libraries

• What about ILL?

– Blur between ILL/Acquisitions

– eBook Rental Replaces ILL?

• What about Collections of Record?

Implications for Scholarly Publishing

• Less predictable

– Reduced frontlist sales?

– Increased backlist sales?

– Fewer copies sold per title?

– Higher cost per title?

– Fewer titles published?

• Better ebook sales?

Implications for Authors

• Harder to publish a book?

– Implications for tenure/promotion

– Alternate forms of publication?

Implementing Shibboleth for Patron-Driven E Books

A Collaboration by Colorado State University and EBL (Ebook Library)

CALC Summit “Collaborate Like You Mean It” May 20, 2010, Denver

5/20/2010 35CALC Shib Presentation

CSU’s Experience– Collaboration During the Water Disaster of 1997

• Innovative Interfaces—gave us new fields

• YBP—oversaw subcontractors

• Absolute Journal Backorder--led to new services, e.g. valued collections for insurance


Current Crisis

• Budget recessions

• Space problems

• Low use of print monographs


New Directions/Goals for Collections:

• Electronic books

– Space savings

– Convenient access for users

– Publishing model for future

• Patron-driven models

– Lower expenditures

– Increase in use


EBL Patron-Driven Model—Advantages for CSU

• Academic publishers

• One free preview

• Short-term loans at % of price

• Automatic purchase option based on use

• Customizable options for loan periods, downloading, staff intervention, etc.


EBL Pricing Models for Purchases

• “Non-Linear” lending/ purchase 325 annual uses at list price—simultaneous use permitted

• Unlimited Multiple Concurrent Uses (Reference) typically at 1.5 list price, also prefer for e reserve

• Limited, Multiple Concurrent Uses for course textbooks, typically priced higher by publisher


User Access to EBL

• Provides MARC record for each title in library online catalog

• Must authenticate to see content


Authentication Issues

• CSU doesn’t want to require users to set up and remember multiple logons and passwords

• CSU wants to offer security and privacy for passwords


Shibboleth

• Open source software for federated identity-based authentication

• Allows single sign-on using institutional credentials

– Institutional netid for sign-on

• Eliminates need for content provider (EBL) to maintain user name and passwords


The Story of Shibboleth

• Judges: 12:1-15

• Shibboleth versus Sibboleth


Implementing Shibboleth

• New collaboration was born with mutual benefits!

– EBL had not implemented in U.S.

– CSU had not implemented for other products


Requirements

• Informed staff: CSU and EBL

• Trusted Foundation: InCommon Federation Allows service provider (EBL) and identity provider (CSU) to manage secure access to EBL’s protected resources using Shibboleth


5/20/2010 CALC Shib Presentation 47

CSU Directory

Shib Transactions

CSU ShibService User

Shib Service

Provider

Shib Identity Provider

CSU Shib

1. Request service

7. Return credentials

3. Pull-down menu, select CSU

4. For CSU, request identity/role

2. Where Are You From?

5. Log in

Synch

8. Grant access

6. Identity/role

InCommon

EBL

A

B

CD

E

Example of User Logon and EBL Screens

User Logon EBL Screen


Limitations of Shibboleth

• Restricts community/walk-in users

– Unless shib ‘orphans’ accommodated

• Doesn’t allow reports by specific user type or identity from EBL

• Protects privacy of CSU users so need local development to get reports by type of user


Lessons Learned --Thanks to insights from Robin

Chambieux, EBL, and Glenn Jaeger, Absolute)

• Outline project goals and priority clearly

• Assign responsibility to oversee project at both ends

• Set timelines for various steps

• Communicate/update regularly

• When testing begins, respond immediately--no breaks in sequencing


And Think Innovatively!

• There’s a way to do it better, find it! Thomas

Edison


Collaboration Leads to Mutual Benefits

• The Library got a simpler way to authenticate e-books

• The University got to test a new application and is working on other applications

• EBL can offer a new service to customers

• Other libraries benefit—other libraries installed Shibboleth within “hours”


Documents

Developing a Demand-Driven Acquisitions Plan: A Library-Vendor Collaboration