PDA01 for PDA/DDA Plans
What is a PDA or DDA plan?
PDA stands for "Patron Driven Acquisitions," DDA stands for "Demand Driven Acquisitions." They're essentially the same, with the term used depending on the vendor. For convenience "PDA" will be used here to refer to both.
A PDA plan is a different purchasing model for libraries from the traditional one. It has similarities to an approval plan. With a PDA plan, a library often sets up a profile with the book vendor. What's different is nothing is purchased until someone takes action. The "action" is negotiated with the vendor; for e-books it's often how often someone clicks the link to go to the ebook. Three patrons using an ebook can trigger a purchase. One patron using an ebook once in a year probably won't trigger a purchase. It's a way for a library to target its purchases to actual user needs.
How does this work?
A book vendor such as Coutts or ebrary sends the library a file of bibliographic records for the set of titles from which purchases may be made. These records may be referred to as "discovery" records because they provide the means to find and access the title. The records are loaded into the discovery tool. Sometimes a publisher withdraws a title or all its titles from a vendor's PDA offerings. When that happens, the vendor sends the library information about the withdrawn titles so the library can delete the discovery record/s from the discovery tool. When a title is purchased, the discovery record is deleted and a permanent record is created, or the discovery record is turned into a permanent record. When the plan ends, the remaining discovery records for unpurchased titles are deleted.
For the FCS, the discovery records are piped directly into Primo. When a title is purchased, the discovery record is deleted from Primo and a permanent record is loaded into Aleph.
For the SUS, the discovery records have been loaded into Aleph (UXU01), then sent to Mango. When a title is purchased, the discovery record in UXU01 is turned into a permanent record.
PDA01 is a new Aleph bibliographic library for FCS and SUS discovery records. It meets several goals for the FLVC.
FCS: The initial Statewide Union Catalog does not include the FCS PDA discovery records. A mechanism was needed for getting those records into Union Mango and the local Mango views. Direct piping of records into Primo has worked well for the FCS. FLVC was interested in a similar mechanism for Mango that would support the special requirements for discovery record maintenance. PDA01 provides a place to maintain the records and pipe them into Mango without mixing them in with the regular Aleph bib library (FCC01).
SUS: Since migrating to a shared bibliographic library, SUS catalogers have struggled with issues surrounding discovery records for the PDA plans. It is not unusual for one library to purchase a title that another library has on a PDA plan. Problems ensued when the same record in UXU01 was used as a discovery record and as a record for a purchased title. The PDA Task Group of the Shared Bib Task Force recommended loading PDA records directly into Mango to resolve this problem. The Shared Bib Task Force presented this recommendation to the Members Council for Library Services (MCLS)in September 2013, and the MCLS approved it. PDA01 is a good solution for implementing the recommendation.
FLVC: FLVC strives to provide uniform services for both FCS and SUS. PDA01 provides such a service for discovery record management that can be managed via LAPS, a centralized processing service for both Colleges and Universities.
How does PDA01 work?
FLVC loads and maintains the records in this new bibliographic library. Each institution's records are kept separate (no sharing of records). If an institution has multiple PDA plans, the records from those plans are kept separate from one another as well. The discovery records are no longer loaded into UXU01 for the SUS, and existing discovery records are deleted from UXU01 after they are migrated to PDA01.
The bibs in PDA01 have no holdings, items or orders. Ownership of the record is indicated by an OWN field with the code for the institution, with some variation for shared plans.
The records are piped from PDA01 to Mango for display in the Statewide Union Catalog and the local catalogs. For the institutions that subscribe to EDS and Summon, the appropriate records are extracted from PDA01 and are shipped to the vendor along with the records from UXU01.
How do the records look in Mango?
The PDA01 records look pretty much like the other records in Mango and can be searched in exactly the same way. It should be transparent to your patrons that some ebook records are PDA records.
How do I identify whether a record I'm viewing is a PDA record?
- Go to the full view of the record.
- Select the MARC view at the top left.
- Look for the presence of an OWN field in the MARC record. PDA01 bib records are the only ones with an OWN.
- SUS libraries may also look for a STA field containing DISCOVERY RECORD.
How do I search Mango to find all the records in one of my PDA plans?
There is a field in the record that's used for data loading that can also be searched. It contains a specially constructed string that is 0 followed by seven letters followed by the ebook identifier. You can search the alpha string followed by a question mark to retrieve all records for a particular vendor and library.
Character 1 represents the type of plan
- 0 = electronic PDA/DDA
- 1 = print PDA/DDA (monographs)
- 2 = non-PDA electronic resources
- 3 = non-PDA print resources
- 4 = print PDA/DDA (scores)
Characters 2-4 represent the vendor
- ALX = Alexander Street Press
- AMV = Ambrose Video
- APP = American Psycho. Publishing
- CAM = Cambridge
- COU = Coutts
- CRC = CRC Press
- DOC = Docuseek
- EBC = Ebook Central
- EBL = EBL
- EBR = Ebrary
- EBS = EBSCO
- ELS = Elsevier
- ENG = ENGnetBASE (CRC Press)
- FOD = Films on Demand
- FPM = Film Platform
- GVL = Gale Virtual
- HAR = Harrasowitz
- JST = JSTOR
- KAN = Kanopy
- RIT = Rittenhouse
- SFR = Safari Books
- SPE = Springer Reference
- SPR = Springer
- TAF = Taylor and Francis
- WIL = Wiley
- YBP = Yankee Book Peddler
- (more will be added as plans are added to PDA01)
Character 5 represents FCS or SUS
- F = FCS
- S = SUS
Characters 6-8 represent the institution.
- FCS codes end in "C"
- SUS codes end in "U"
- Code for SUS-wide shared PDA is "SUS"
- Code for FSU-UF shared PDA is "FFS"
- 0EBSFBOC? retrieves EBSCOhost ePDA records for Broward College
- 0CAMSFFS? retrieves Cambridge ePDA records for the shared FSU-UF plan
- 0COUSSUS? retrieves Coutts ePDA records for the shared SUS plan
- 0COUSUFU? retrieves Coutts ePDA records for UF
- 1COUSUFU? retrieves Coutts print PDA records for UF
- 2EBRFBOC? retrieves Ebrary electronic discovery records (non-PDA) for Broward College
How do I view the records in the Aleph client?
For the SUS only, the clients are configured to offer PDA01 as a library you may search. Select the search base PDA01 to search all PDA records. Select PDA xx Cat (e.g. PDA UF CAT) to search only your library's PDA records.
The available indexes are listed in the dropdowns. Special ones for PDA01 include:
- 910 -- the alphanumeric number described above
- LCI -- the call number in the 050 field
- TKR -- load tickler; 3-letter institution code followed by PDA and the load date, e.g. SUSPDA20140326
- WOW -- OWN code