A Learning Curve: Lessons Learned Driving Along the PDA Path
•Télécharger en tant que PPTX, PDF•
1 j'aime•771 vues
COMO2013: PowerPoint presentation to accompany the video found here: https://valdosta.sharestream.net/ssdcms/i.do?u=ba21530b62dc4fc
Recommandé
Recommandé
Contenu connexe
Tendances
Similaire à A Learning Curve: Lessons Learned Driving Along the PDA Path
Similaire à A Learning Curve: Lessons Learned Driving Along the PDA Path (20)
Plus de GLA: Technical Services Interest Group (TSIG)
Plus de GLA: Technical Services Interest Group (TSIG) (20)
Dernier
Dernier (20)
A Learning Curve: Lessons Learned Driving Along the PDA Path
- 1. A Learning Curve: Lessons Learned Driving Along the PDA Path Panelists: Lynn Futch Guy Leach Chris Palazzolo Olga Russov Amy Bursi Sofia Slutskaya Ogeechee Technical College Georgia Tech Library & Information Center Emory University Kennesaw State University Georgia Perimeter College Georgia Perimeter College
- 2. What is PDA?
- 4. Do you have books that are never checked out? PDA helps with this problem. • Definition: Library user find and identify documents/books prior to the library’s purchase of them; the library pays only for what its patrons actually use. • E-books purchased by the patron at time of use • Immediate access to content • Books found through library catalog • Paid through an institutional account • User is not aware if the book is owned or not
- 5. Possible Approaches • Single preferred vendor/platform • Options: • • • • EBSCO EBRARY JSTOR Project Muse • Multiple platforms through YBP • E-books from multiple platforms are available with the ability to select a preferred platform • Duplicate checking is possible against e-book and print collection • Same acquisitions workflow as for print books
- 6. Vendor Selection Considerations • Vendors vary significantly in terms of use, content/titles inventory, format, etc. • Multiple vendors vs. single vendor
- 7. Vendor Selection (cont) • Vendor’s reputation and existing relationships with vendors • Terms of use/license agreement with publishers • Platform/interface/tools provided by vendors (how easy to select a book, program management, payments, vendor’s response and turnaround time)
- 8. Vendor Selection (cont) • Purchasing models and acquisition options (ownership vs. subscription, one time fee, annual access fee, annual subscription cost, purchase, STL, lease, SUPO vs. MUPO, threshold for triggering an acquisition) • Vendor’s response and turnaround time
- 9. Budget Considerations • Shrinking budgets • Increasing prices • Shifting from ―just-in-case‖ acquisitions model to ―just-in-time‖ • Control spending by limiting number of books offered for PDA
- 10. Working with various e-book platforms through YBP • eBrary • EBSCO • EBL
- 11. Emory: PDA/DDA Workflow/Process Issues • Are discovery records uploaded automatically? How often? How does notification of new loads work? • Any additional technical specifications added to records? • Are the records held in the catalog itself or are they piped into a discovery service, e.g., Primo or Summon? • Are liaisons able to choose records to add to DDA pool? • Changes to records once title is triggered for purchase? • Are records ever removed? How are they identified? • How is invoicing handled?
- 12. GA Tech: PDA/DDA Chose ebrary via YBP--Easy set up based on Slip Profile $25,000 Deposit account--$200 price cap for eBooks May 2010 Create YBP Slip Plan (move from Blackwell) Jan. 2012 Sent ISBNs to YBP & Create Retrospective (Not Used) April 2012 Received first Discovery Records August 2013 Manual DDA made available to Subject Librarians October 2013 Tiered DDA with ebrary, EBL and EBSCOhost
- 13. GA Tech: PDA/DDA Workflow • Collection Development reviews each weekly batch of titles • Compare against ebook subscriptions where the holdings are not in YBP • Identify standing orders, non-monographic series, publishers/imprints, etc. to remove from DDA • Collection Management adds and maintains catalog records • Add 970 field ―ebrary DDA - discovery - loaded 2012‖ (now 2013)--date added for easy retrieval, review and potential removal of records • Replace discovery records with purchased records—change 970 field to ―ebrary DDApurchased‖ • Communicate internally and with subject librarians when DDA titles are purchased via firm order • Collection Development monitors usage and maintains statistics • Review plan and make adjustments • Review coverage and usage by subject areas/fund codes for impact on future funding • Examine coverage and usage by Publishers to determine best source for acquisition
- 14. GA Tech: PDA/DDA Assessment Review and Analyze Loans & Purchases Review Titles Used and NOT Triggered for loan or purchase Review Turnaways (default is single user— upgrade if possible if usage is high) Review Usage of Books Purchased • 11,265 Discovery Titles--average of 662 Titles a month • 910 Total loans--$11,896.51 in loans, $13.07 average loan cost • 582=1 loan, 215=2 Loans, 113= 3 loans • Value of books loaned=$59,170.39 • 95 Title Purchased--$8,720.52 • 65 with Short Term Loan--$6,543.12 • 30 Purchased upon first use (no STL)--$2,177.40 • 859 Titles used but not triggered for loan or purchase • Total Spent $20,616.17 in a 17 month period
- 15. GPC PDA Workflow PDA/DDA consideration pool Discovery • Consideration pool created and activated in EBSCO Collection manager • Deposit account ($5000 increments) • MARC records for consideration pool titles are not added • Discovery through EDS Acquisitions • Weekly notifications of purchased titles from EBSCO • MARC records are added only for purchased titles Evaluation/ Assessment • Trigger report • Usage after purchase • Consideration pool evaluation
- 16. GPC Results 05/30/13 – 08/07/13 (10 week) 12/10/12 – 02/07/13 (9 weeks) Selected for consideration 4000 Selected for consideration 4000 Total spent: $4823.96 Total spent: $4925.69 Titles purchased Cost per title: 49 $100 Titles purchased Cost per title: 88 $56 Selections parameters: Selections parameters: • Unlimited simultaneous use • One user • Price per titles - $200 or below • Price per titles - $100 or below
- 17. Technical Colleges are using EBSCO’s PDA program
- 20. Assessment • Cost per title • ROI • Circulation statistics • Counter usage reports and turnaways • Fit • User behavior and satisfaction • Others?
- 21. GPC Assessment: Trigger Reasons Page Turns, 67.2% Time in Book, 14.6% Download, 11.7% Printing, 6.6% 1
- 22. GPC Assessment: Use after Purchase (Jan.– Jul. 2013) none 8.20% 1 time 20.40% 2 times 10.20% 3 - 4 times 20.40% 5 -9 times 22.40% 10 and more 0.00% 18.40% 5.00% 10.00% 15.00% 20.00% 25.00%
- 23. Questions? • Lynn Futch College) lfutch@ogeecheetech.edu (Ogeechee Technical • Guy Leach guy.leach@library.gatech.edu (Georgia Tech Library) • Chris Palazzolo Cpalazz@emory.edu (Emory University) • Olga Russov orussov@kennesaw.edu (Kennesaw State University) • Amy Bursi amy.bursi@gmail.com (Georgia Perimeter College) • Sofia Slutskaya sofia.slutskaya@gpc.edu (Georgia Perimeter College)
Notes de l'éditeur
- Lynn
- LynnIn the library world, PDA means Patron Driven Acquisition:In academic libraries, we’ve gotten very good at understanding our patrons’ needs in the aggregate: we know the curriculum and we know our faculties and their areas of research interest, and that knowledge has always guided our collecting strategies. This means, for example, that it’s possible for me to know that my faculty needs good books on high-energy physics. The problem is that it’s not possible to buy “books on high-energy physics.” It’s only possible to buy specific books on high-energy physics, which necessarily entails not buying other books on high-energy physics, and my ability to predict which exact books on high-energy physics my patrons will need and use is very limited. Remember that the purpose of the collection isn’t to be a great collection; it’s to connect patrons with exactly what they need
- LynnPDA is built on a deceptively simple premise: in a largely digital information environment, it’s increasingly possible to let library users find and identify desired documents prior to the library’s purchase of them, and for the library to pay only for what its patrons find and actually use. When a patron’s use of an ebook or journal article passes a certain agreed-upon threshold (a certain number of ebook pages read, for example, or the download of a complete article) the library is charged, the document acquired, and the patron never knows that the document was not part of the “collection” to begin with. Such an arrangement has the potential to be enormously liberating for library users, and to solve one of the library’s longstanding and fundamental problems: the fact that traditional “just-in-case” collections give patrons access to only a tiny (and inconsistently relevant) sliver of the population of documents that are actually available for use.But like all acquisition and access models, PDA is imperfect, its manifestations are numerous and to some degree chaotic, and its availability raises lots and lots of questions, many of which I find myself trying to answer during the Q&A segments at the ends of my presentations. Several questions arise repeatedly, which suggests to me that there’s broad interest in answers to them. Here are some of those questions, with my attempts at responses.
- Sonya
- Olga
- Olga
- Olga
- Olga
- Olga
- Chris
- Sonya
- Lynn
- Lynn
- Lynn
- Olga
- Total: 4910 and more 95-9 113-4 102 51 10None 4