10 likes | 106 Views
The Good, The Bad and The Unread: DDA Un-Chosen Record Withdrawal Lauren DeVoe Acquisitions Coordinator Howard Tilton Memorial Library Tulane University ldevoe@tulane.edu 504-862-8583. Workflow: 1 .Adhere to all Policy Decisions
E N D
The Good, The Bad and The Unread: DDA Un-Chosen Record Withdrawal Lauren DeVoe Acquisitions Coordinator Howard Tilton Memorial Library Tulane University ldevoe@tulane.edu 504-862-8583 Workflow: 1.Adhere to all Policy Decisions 2.Query TULANET VOYAGER, for 9xx field with DDA information and dates. Retrieve all matching records. Also note: a. The platform the book is hosted on b. The date it was received c. The unique holdings location. 3.Select all records that you want to remove and create a list 4.Delete bib records and holdings with a bulk delete program, such as Gary Strawn’s. a. All records will be removed from the catalog 5. OCLC holdings deletion a. Delete our holdings from the OCLC record 6.Keep statistics a. Send lists of withdrawn titles to appropriate bibliographers Introduction: Demand driven acquisitions seems to be quickly gaining an important role in the library’s acquisition’s process. In the excitement over patron driven acquisitions, libraries have been looking at issues such as selection, access, price and how to implement a workflow for purchasing titles. But what happens when a title is not selected? How do libraries handle a build-up of these titles that are never touched? Do we leave them indefinitely? Do we put a time limit on how long a record stays without use and then withdrawal it? And if we do withdrawal a title, how can technical services set up a workflow that efficiently handles the withdrawals of these records? Policy: Policy is the most important aspect of the workflow. Bibliographers must decide how DDA records will be chosen. (Selected by vendor, or chosen specifically by bibliographer?) And then what is their criteria for withdrawing them. At Tulane, it will be the amount of time the record has stayed un-chosen. Each DDA record will be coded with a 9xx field to note that the record is DDA and the date it was received. If an item is purchased, that field will be overlaid with the purchasing info, so that there is no question about whether or not it has been purchased. Policy Decision Challenges of DDA: Is DDA there to help you build the collection, or simply supplement the collection? Curation of collection over time. How do these multiple records change the overall look of the collection? In an atmosphere of ambivalence towards eBooks, how does leaving DDA records help or hinder the user’s response to the collection? The assumption that your patrons know how to build a better collection that you do. How does DDA fit into long term collection plans and policies? Long term build up of DDA records. Efficiency of cutting titles from unchosen DDA. Long term licensing and platform issues Budget focus Generate a list of bib and holdings information for DDA coded records selected for withdrawal Resources Can Be Found: Run bib/hldg. Info through Bib-Delete program to Remove from OPAC