510 likes | 735 Views
Discover Discovery. The Maryville University Flavor!. Presenters. Ying Lin Electronic Resources & Information Literacy Maryville University ylin@maryville.edu Mary Ann Mercante Assistant Dean/Head Tech Services Maryville University mmercante@maryville.edu.
E N D
Discover Discovery The Maryville University Flavor!
Presenters Ying Lin Electronic Resources & Information Literacy Maryville University ylin@maryville.edu Mary Ann Mercante Assistant Dean/Head Tech Services Maryville University mmercante@maryville.edu
Maryville University Background • 2,568 FTE • Undergrad and graduate programs –Liberal Arts, Business, Education, Health • On May 7, began two nationwide online graduate Nursing programs (MSN & DNP)
Maryville Library Background • 104 databases, 84,559 unique e-journal titles • Approx. 41,000 eBooks & 101,000 physical holdings • Beginning a small PDA project with EBSCO for Nursing titles (109 records) • 4 Full-Time librarians (1 Dean, 2 Ref, 1 Tech Services) • 4 Full-Time staff & 3 20hr staff
Why Use Discovery? • Goal: Simple, for students to use library more. • Problem: Students, especially first time users, do not know how. • Thinking: Learning vs. Convenience Content vs. Infrastructure • Proposal: Make the searching easier but maintain the quality of searches • Solution: a discovery like interface
Why EBSCO? • We are deeply invested in EBSCO • The familiar interface for our users
Discovery – from the reference librarian’s point of view • Much faster compared to Integrated Search • Cover images for books • Enriched results compare to Integrated search • Higher quality of article-level results • EBSCO eBooks full text searching and table of content display • Catalog Record Display • Very powerful for the “Right Users”, both easy and complicated Next
Discovery – from the system and tech service librarians’ points of view • Questionnaires • EBSCO Branding and Customization • EDS Content Questionnaire • Library Catalog & Discovery
The Library Catalog & Discovery • Preplanning & catalog cleanup (you should be so lucky!) • Providing information to EBSCO on your catalog • Setting up initial and ongoing record transfers from your catalog for inclusion in Discovery • Planning for ongoing maintenance issues
Library – MCO Relationship • Need to open Help Desk Ticket • Need to get quote for services and “approve” the quote • MCO’s assistance in preparation for a “discovery” service and subsequent initial and ongoing record file transfers to “discovery” vendor (or scriptwriting for you to do this) is a billable service
Preplanning & Cleanup • Are there records in your catalog you would not want found in Discovery? • Are there obsolete item location codes that still have item records carrying them? • Are your itypes and location codes “in synch”? • Are you consistent about coding for materials, especially eBooks, audio-books, full-text?
Library Catalog Info for Discovery • EBSCO Custom Catalog Database Questionnaire • Purpose is to tell EBSCO where to find info and what codes mean/how they should display • Some questions need MCO assistance • Good idea to send completed questionnaire to MCO for review prior to sending to EBSCO
Catalog Linking Info for Discovery “Please provide the URL syntax that can be used to link directly to records in your OPAC along with the field/subfield in your data files that corresponds to the various URL parameters.” Original response: http://bridges.mobius.umsystem.edu/record= ***Needed to update EBSCO at time of server migration to http://bridges.searchmobius.org/record=
Catalog Metadata Info for Discovery “Please list the language(s) of your raw MARC data (not Language of Item). “ MARC21
Catalog Metadata Info for Discovery • “What is the MARC field/subfield that represents a persistent, unique identifier for your records (i.e. 001, or 907 $a)? “ 907 $a (This is the bib record #) Note: this value will be used by EBSCO to generate accession numbers and persistent links for items in your catalog
Catalog Metadata Info for Discovery • Important: When vendor asks for information as to where information is stored in your records, they are asking where the information will reside in the exported record, not in the record as you see it within Millennium
Catalog Metadata Info for Discovery • Important for you to know that the exported records sent to EBSCO will be bib records with your item and/or checkin record information and other info, such as bib #, in 9xx fields on the bib record • Attached records (items, checkins, orders) are not exported as records themselves
Export Table • There are export tables that determine which fields are output in the exported records • MCO will work with you on the Export Table(s)
Catalog Information for Discovery “EBSCO supports eBook and Audiobook icons. In order to display the correct icon, please tell us how EBSCO can identify a record as either an Audiobook or eBook:”
Catalog Full Text Info for Discovery “If you would like any catalog records to return when limiting to Full Text please tell us how EBSCO can identify a record as Full Text (For example: eBook, Audiobook, e-resource, etc)” The following text in 856 $z Maryville: Click here to access this online book
Catalog Location Lookup Table “ In order to display item/copy location information in user friendly form, EBSCO can expand coded location values in the holdings section of your MARC data via a lookup table.”
Catalog Location Lookup Table • This location lookup table (an Excel spreadhseet) needs to include four columns: • Location_Code, • Copy_Display, • Facet_Display, • Limiter_Display
Catalog Real Time Availability Info for Discovery “EBSCO can connect to your z39.50 service to retrieve and display Real-Time Availability for items in your catalog. If you have holdings information (status, location, call number, etc.) available within your z39.50 service, please include authentication information below.”
Record Loads • Test sample for the vendor • Initial load of whole catalog • Gap load • Ongoing – these are our choices: • Daily adds • Weekly cancels
Records Not Sent to Discovery • We’ve told MCO not to pull bib records where the bib suppress code (Bcode3) is n or s • These suppress codes suppress in both the Union catalog and locally • These keep ILL items and non-collection items (supplies, travel, etc.) from going into Discovery
MCO Pulls Records Based on Bib Codes • For daily adds file: • Looks for bib records with a Maryville active bib code and with a bib update date since the last pull • For weekly cancels file: • Looks for bib records where the only Maryville bib code is mzb (we defined this as our withdrawal bib code)
Maryville Active Bib Codes • Active bib codes: • mu1 generated by item codes mumcb, mumcm, mumco, mumtm • mu2 generated by item codes mumra, mumri, mumro, mumrs • Etc.
Maryville Cancels Bib Code • mzb – generated by item codes mzdii, mziii, mzwii
Always Remember!!!! • There is another copy of your database at your Discovery vendor • Changes must be made in both places • You can’t just delete bib records anymore • Any new bib location codes, itypes, URL changes, etc. must be thought of in terms of “does this affect Discovery”
You Can’t Just Delete Bibs Anymore!! • If you delete the item record for one copy or volume of a multi set, you still have a bib with holdings for the “real time” connection to find • If you delete a bib record for any reason, EBSCO must also delete it; otherwise if a patron finds it in Discovery and follows the catalog link, there’s no longer a match in your catalog
To Delete a Bib at Maryville • Code all items for mzdii (or delete all but one which is coded for mzdii) • Move any attached orders off the bib • These two steps cause the bib location code to convert to mzb only • MCO pulls mzb-only bibs in the weekly cancels • After MCO pulls, we can then go back and delete the bibs
Issues? eBooks and duplicate records