Difference between revisions of "RDA 2.0"

Revision as of 09:21, 2 August 2012

RDA PROCESSING OVERVIEW

MARS 2.0 RDA processing makes changes in over 100 different MARC fields within your bibliographic record. Our RDA service updates many elements in MARC bibliographic records to conform with current RDA and MARC 21 standards, providing increased consistency within your bibliographic files.The level of MARC update is entirely configurable by you and your staff. The update process is tailored to your expectations of what you’d like to see happen within your bibliographic records.

standard marc21 validation

As soon as we receive your files, they are prepared for processing. MARS 2.0 checks all files of MARC records submitted to ensure they conform to the basic structural requirements of the MARC 21 communications format. Our validation programs ensure that all records meet the following criteria:

• Leader is present and correctly structured
• Directory is present and correctly structured
• No record exceeds 99,999 characters. Including bib records larger than 99,999 byte maximum size prevents successful processing of the input files. Records cannot be segmented (broken apart into multiple physical records) to reach the maximum size limit. These records will be output as potentially corrupt for the library to review
• No field exceeds 9,999 characters (MARC 21 directory limitation)
• If a record exceeds the character or field size it is not processed. If there is a large number of rejected records our programmers will contact the library project manager to determine a course of action
• All records contain the following standard MARC delimiters:
  • Record terminators (ASCII 1D16)
  • Field terminators (ASCII 1E16)
  • Subfield delimiters (ASCII 1F16)
• All records contain valid characters (either in MARC8 or UTF-8)
• Any null characters (hex 00) are changed to spaces when records are loaded
• MARS 2.0 will also delete empty fields or subfields as records are loaded

Note: MARS 2.0 can process MARC 21 records that lack 001, 008 or other fields.

rda authority control

In November 2010, Backstage created several authority control options for processing RDA bibliographic records (040 $e). Since that time we have refined these options with help from our clients. Currently we have 5 separate options to choose from:

• 1 - AACR2 & RDA against AACR2 only
• 2 - AACR2 against AACR2; ignore RDA
• 3 - AACR2 against AACR2; RDA against RDA
• 4 - AACR2 & RDA against AACR2 (1st), RDA (2nd)
• 5 - AACR2 against AACR2 (1st), RDA (2nd); RDA against RDA (1st), AACR2 (2nd)

Option 1 is our current default, which requires no action on the part of our clients. However, if a client is interested in RDA authorities, our recommendation would be Option 5, which represents the current LC/PCC standard.

Regardless of which authority control option is chosen, there are several of our bibliographic validation rules that are not run on RDA bib records. This includes:

• Subfield Updates and Deletes (namely any rules that remove relator terms)
• Field Conversions and Additions
• GMD Standardization

TOPICS

• Step 2.1 - Bibliographic Validation
• Step 2.2 - Leader Update
• Step 2.3 - Cataloging Source Description Convention
• Step 2.4 - RDA Authority Control Options

LINKS