Reconciling Ebook Packages at NCSU Libraries Eric Hanson, Electronic Resources Librarian Christee Pascale, Associate Head Xiaoyan Song, Electronic Resources Librarian Acquisitions & Discovery at NCSU Libraries
The eBook Reconciliation Project ●e-Resource Hub o Wiki-based HTML text files o Captures administrative data about our ebook packages ●eBook Reconciliation Database o Microsoft Access database o Title list data o ILS MARC record data
eBook Reconciliation Database Goals ●Access verification ●Title list certification ●Package and provider look-up
Access Verification Title reconciliation process: 1.Load publisher ebook package title lists 2.Load ILS ebook MARC record data 3.Compare publisher title list data with ILS ebook MARC record data Title reconciliation results: 1.Every title included in an ebook package title list correctly activated in Serials Solutions knowledgebase 2.MARC record for each title is present in our ILS & Endeca 3.We have access to ebook titles on publisher/vendor platform
When perpetual access isn’t forever... ●Title list certification o Title list of record o Proof of purchase
Package and Provider Look-Up ●Troubleshooting access issues ●Look up an ebook title to find: o Package(s) association o Provider/vendor association
Ebook Package Data Chain Publisher Knowledge Base (Serials Solutions) ILS (Sirsi) Discovery (Endeca)
Project Pilot ●Goal: o Build up the reconciliation database o Create documentation o Establish workflows o Set up staffing model ●Elsevier ebook packages
Workflow Collecting Publisher Title ListObtaining Title List from Sirsi Reconciling the Two Title Lists to Locate Mismatched Titles Take Corresponding Actions for the Mismatches Identify Ebook Packages Requiring Reconciliation
The Reconciliation Database
Example: DUP Ebook Reconciliation
Our Approach Publisher list Publisher title lists vary Different approaches required for various publishers based on the data provided
Our Approach Publisher list Simplifying vendor lists to the essential data elements and standardizing column names so queries can be reused o Title o URL o ISBN o Collection/Series
Our Approach ILS list Used a custom bibliographic report in our Sirsi ILS to extract records from specific providers Report based on the provider name used by Serial Solutions in the 856 subfield z which we had requested as part of our MARC record service
Our Approach Comparing the lists The URL or a portion of the URL was used as the identifier for matching titles on both lists o Publisher: o ILS: ISBNs did not prove to be useful because they are complicated to extract from Sirsi and multiple ISBNs are often stored in MARC records and publisher lists
Our Approach Comparing the lists OpenRefine Jython script used to find the ending location of redirecting URLs, such as some DOIs o Publisher: o ILS: import httplib conn = httplib.HTTPConnection("dx.doi.org") doi = "/"+value conn.request("HEAD", doi) res = conn.getresponse() return res.getheader('location')
Our Approach Comparing the lists Created a Status field for categorizing discrepancies between the two lists Stored separately from the provider list, so it will not be lost if the provider list needs to be refreshed
Most commonly seen issues & solutions Not Tracked in SerSol Tracked in SerSol but not in Sirsi Not in SerSol Access Issue Activate them in SerSol Request SerSol to add Marc records Request to add to SerSol Correct URL error in SerSol Request access from provider
Data for Common Issues
Issues for Individual Provider
Next Steps ●Phase 2: o Access verification comparing ILS data to publisher title lists ●Phase 3: o Title list certification ●Other enhancements: o Reporting functionality o Look-up functionality