SUS-wide DDA

From SharedBib

Jump to: navigation, search

Contents

Summary

A library contracts with vendors for the purchase of materials that may be selected one-by-one or selected en masse based on a profile that defines areas of interest, formats, language, and so on. The vendors provide various support services that include the provision of bibliographic records. The library loads the records into its library management system (LMS) to support internal accounting and collection management needs as provide information about what’s been ordered for patrons. Library patrons occasionally recommended titles for purchase, but this was not the main means of identifying what to buy.

A new type of puchase plan developed in recent years provides an alternate means to identify titles for purchase. Known variously as Patron Driven Acquisitions (PDA) or Demand Driven Acquisitions (DDA), this type of plan encourages greater participation by library patrons in purchasing materials for the library’s collection. Rather than providing records only for titles the library is purchasing, the vendor provides records for all titles the library considers appropriate to purchase (“discovery” records). There are usually some kind of criteria used to select these records, such as areas of interest, formats, language, etc. The library loads these records into the catalog or discovery tool for patrons to discover, right along with the materials the library already owns. The patron can then generate a purchase without further intervention of library staff. In the case of ebooks, the patron clicks the link to the ebook and accesses the title immediately. Depending on the library’s contract, one to maybe three accesses of the ebook triggers the automatic purchase of the title. Once a title is purchased, the vendor generally supplies a permanent bib record for loading into the LMS.

There are two parts to PDA/DDA data loads: loading the discovery records and loading the permanent records. The discovery records represent materials the library has not purchased yet; there is no particular need to load them into the LMS. The records for purchased titles need to be loaded into the LMS as a permanent part of the library’s collection.

Project Steps

  • In conjunction with the library, negotiate with the vendor on the delivery schedule for discovery records and permanent records.
  • Ideally, load discovery records directly into Mango, using specs for library-specific location display and URL. This requires the vendor to provide a full replacement file of discovery records on a weekly or monthly schedule.
    • Discovery records are causing problems in Aleph in terms of sharing.
  • Provide files of discovery records for loading into EDS or Summon as needed.
  • Load permanent records into Aleph.

Status

  • SUS-wide PDA project with Coutts (new)
    • Loaded test file into a test Mango
    • Requested full file for discovery records
    • Collections team discussing which vendor records to include
    • Waiting for content decisions to be finalized and a production file to be sent to FLVC
    • Will load into Mango within 2 weeks of receiving new file
    • Will send to Serials Solutions and EBSCO as appropriate
    • Waiting for Coutts/Ingram while discussions continue with publishers
  • FSU/UF PDA project (pre-existing)(discovery records loaded into Aleph)
    • Loaded in the Gainesville office before Shared Bib with manual process
    • July and August have been loaded in Production
    • September, October, November files will be loaded the beginning of December
    • Established a new process more in line with the SUL-wide process eventually
    • Created new Genload profiles
  • DDA legacy projects
    • Should review to see if new process (loading into Mango) would be more efficient
    • In the mean time should continue to load into Aleph
    • Use unique sublibrary/collection code to identify discovery versus purchased titles
  • New DDA projects
    • UWF Update: UWF has decided to not load discovery records into either Aleph or Mango. They will put in a Genload request for the purchased items only. This item is closed.

Proposed procedure for SUS-wide project

  • Load full file directly into Mango on a weekly basis
    • Add holdings and 856s with proxy string
    • No deduplication
  • Notification when item is bought
    • Load into Aleph with 11 holdings and separate 856 fields
  • Adapt Mango Union Catalog display
Personal tools