350 likes | 491 Views
RDA Implementation: What, Why, and How in One Hour Richard Guajardo & Stephanie Rodriguez University of Houston. University of Houston Libraries. RDA Conversion & Authorities Project. What – Bibliographic database Has not been output for a complete authority
E N D
RDA Implementation:What, Why, and How in One HourRichard Guajardo & Stephanie RodriguezUniversity of Houston
RDA Conversion & Authorities Project • What – Bibliographic database Has not been output for a complete authority control project since the mid 90’s • Why – A hybrid catalog This could prove difficult to manage and result in some confusion with inconsistent access points
RDA Conversion & Authorities Project • [ Who – Four libraries: UH, UHD, UHCL, UH LAW ] • How – Creating a new set of Material Type codes, outputing bibliographic records for print and media materials for RDA conversion & authority control, developing an in-house process for e-resource records
RDA Conversion Planning Revise Material Types Updated Catalog Search RDA Content, Media, & Carrier Types RDA Implementation Preparation RDA Conversion Conversion Timeline Post-RDA Conversion Practice
Material Type (BCode2) Revision • Why revise the Material Types? • The General Material Designation [GMD] in the title field is replaced in RDA with more specific CMC fields Content type Media typeCarrier type • We need to revise our material types to be more specific to match CMC fields • Ensure the insertion of appropriate CMC fields in the RDA records conversion process
B CODE1
RDA Implementation – Preparation • Database Clean Up - OCLC Number Match Project • Configure Load Tables for New RDA Bib. and Authority Fields • Install AACP for RDA Authority Headings Change • Launch BCODE2 (material type) Changes for RDA GMD Replacement
OCLC Number Match Project • PRODUCT SUMMARY ProductCode: TAP3989 135,674 ProductCode: CTR3750 127,286 • BIB PROCESSING Records processed: 135,673 Duplicates dropped: 1,251 Records rejected: 1 Unresolved records: 5,075 Records merged: 2,061
LOAD TABLES Request a Service Commitment (CSDIRECT) for an RDA load table update UH has 60 load tables for bibliographic and authority records (some not active) Revise the load tables as additional RDA updates are adopted Used daily for batch load work in acquisitions and cataloging functions (including reloading of records processed by Marcive for authority control and RDA conversion) Reloading of one time projects (OCLC reclamation project)
AACP for RDA Authority Headings Change • Automatically updates headings in a bibliographic record • Requires a 4XX reference in the authority record • Triggered by a change in the authority record • Heading in bib. record must match 4XX exactly
AACP Installation – Automated Authority Control Process Courtesy: csdirect.iii.com
Strategies for Review Files • Build lists from current BCODE2s Example: • Bcode 2 = j • Exclude BCODE3 = d • Break lists down by specific formats Example: • Identify marc characteristics • Rapid update
BCODE 2
NO [GMD] ICON
RDA Conversion • MARCIVE RDA Conversion Process: • Send files to MARCIVE • MARCIVE test RDA conversion – 1 week • MARCIVE send test file to us for approval • Final conversion (7-10 days) • Load converted record back to III • Internal Conversion Process: • Global RDA Update of E-books/E-journals
RDA Conversion Timeline 2013 • 04/01- 04/03 Update load table to accommodate new RDA fields • 04/15 - 04/19 Export Bib-records and send them to MARCIVE • Created 10 files of 50,000 records • 04/22 - 04/26 MARCIVE test conversion
RDA Conversion Timeline 2013 • 04/29 - 05/10 Approve test conversion and begin MARCIVE final conversion • 05/13 – 06/12 Load converted records back into III
Post-RDA Conversion Practice • Physical items • Continue accepting best available (RDA or AACR2) records from OCLC • Revised local OCLC constant data records to accommodate new material types • Weekly, pull together new bib. records for authority process and send to Marcive for RDA conversion • E-books/E-journals • Receive Serials Solution ebook and ejournal records bi-monthly • Configured load table to insert RDA fields to records • Decided to convert these in-house because of fluidity of records
Post-RDA Conversion Practice • Bringing in updated records from OCLC and other vendors
Post-RDA Conversion Practice Hybrid -> RDA
Thank You! Richard Guajardo & Stephanie RodriguezUniversity of Houston