rda and editing bibliographic records
DESCRIPTION
This is a short (1.5 hour) presentation for support staff about RDA and the do's and don'ts of editing bibliographic records in MARC format. Covers background material on RDA, identifying RDA records vs AACR2 records, changes to records and cataloging practices due to RDA (fields, vocabularies, terms, etc.), hybrid AACR2/RDA records, and the basic rules of editing (both general and for specific fields).TRANSCRIPT
RDA and Editing Bib Records
Shana L. McDanold
Head, Metadata Services
2
Cataloging brief history Early cataloging codes
No “one” set for US libraries 1940s: ALA cataloging rules
1961 IFLA’s Paris Principles Cutter’s Rules for a Printed Dictionary Catalog
1967: Anglo-American Cataloging Rules (AACR) 2 versions!: North American text and a British text
1969: ISBDs (consolidated in 2007) 1978: Anglo-American Cataloging Rules Revised (AACR2)
Revisions: 1988, 1998, 2002
1960s: MARC developed (Henriette Avram) Work completed 1969 US standard by 1971; international standard 1973 Several “flavors” of MARC
3
RDA – the birth story
2005: Final update of AACR2 2002 ed.
1997: International Conference on the Principles & Future Development of AACR
2002: AACR3 development begins 2003-2007: meetings of the International Cataloguing Principles
(ICP) 2005: AACR3 renamed RDA: Resource Description and Access 2006, 2007: drafts of RDA chapters and appendices 2008: first full draft of RDA 2009: delivered to the publishers 2010: first published in the RDA Toolkit 2010/2011: testing, testing 2012: re-writing by an editor, other tasks designated by U.S. Test
Coordinating Committee March 31, 2013: RDA implementation!
4
So why RDA? AACR2 is based on a card environment
Rules/Structure limited by that 3x5 inch boundary
RDA is designed for the web and online communication, making use of how intertwined the web is to share information
From RDA 0.0 Purpose and Scope: “RDA provides a set of guidelines and instructions
on formulating data to support resource discovery.” “RDA provides a comprehensive set of guidelines
and instructions covering all types of content and media.”
5
Bibliographic records
RDA is fundamentally different in its approach to describing materials/resources/things Focus on content *first* and carrier/format second
RDA cultivates relationships
“Guidelines and instructions” rather than rules Cataloger’s judgment
6
Bib records – vocabulary changesAACR2 RDA
Heading Authorized access point
Author, composer, artist, etc.
Creator
Main entry Preferred title, and, if appropriate, authorized access point for the creator
Uniform title Two RDA counterparts:1. Preferred title + differentiating
information2. Conventional collective title like
“works”
Physical description Carrier description
General material designator (GMD)
Three elements:1. Content type2. Media type3. Carrier type
Chief source Preferred source(s)
7
Bib records – new MARC fields 336 – content type 337 – media type 338 – carrier type 344 – sound characteristics 345 – projection characteristics of moving image 346 – video characteristics 347 – digital file characteristics 264 – production, publication, distribution,
manufacture, and copyright notice New subfields for relationships (mostly $e) New subfields to parse 502 Dissertation
information
8
Bib records – controlled vocabularies Fields using controlled vocabularies:
336, 337, 338 [RDA] Relationship subfield (|e) [RDA] 6xx [LCSH]
MUST use a term from the lists in those fields Terms are registered on the web
9
Bib records – key changes Transcription – record what’s there! Source(s) Relationships for authorized access points
*Required* for the creator Rule of three – gone! Be liberal in recording alternate titles Related works are no longer in a general note
field, but rather traced so they can be linked GMD replaced by 336 (content type), 337
(media type), 338 (carrier type)
10
Bib records – key changes Spelling out of abbreviations
p. pages ill. illustrations cm is not an abbreviation, it is a symbol, like ©
Latin terms no longer used [S.l. : s.n.] [Place of publication not identified] :
[publisher not identified] [et al.] [and # others] [sic] 245 has title as appears on piece; 246
contains corrected form of title Adjacent bracketed elements are bracketed
separately
11
Bib records – identification/examples Identification of an RDA record:
040 |e rda LDR/18 (Desc) = i (ISBD), c (ISBD not included),
blank (non-ISBD)
Identification of an AACR2 record: 040 has NO |e LDR/18 (Desc) = a (AACR2)
12
RDA or AACR2? Maybe both! Hybrid records
A record that contains elements from more than one content standard Such as an AACR2 record with 33x fields or |e relationship
terms can safely add as many elements as you desire that
don’t impact the transcription based descriptive fields – those form the “bibliographic integrity” of the record Add notes, correct authorized access points, add authorized
access points, but don’t edit the publisher or title information If more edits are needed, give the record and resource to a
cataloger
Why? goal is to support access – add things that will enhance
and contribute to the user finding what they need
13
Bib records – basic rules of editing The goal of editing a bibliographic record
should be focused on enhancing the record to improve user access to the resource by contributing to the user tasks: find, identify, select, and obtain
If it's not wrong, leave it alone If it’s wrong, correct it; only delete when you can’t
fix it Don’t edit just for style/phrase/etc.
Accept capitalization and abbreviations! Ask first if you are not sure Do NOT use abbreviations
Unless present on the piece in hand
14
Bib records – what can I or can’t I edit?Field Delete
?Add? Edit? (change
or correct data)
050/090 (LC call number) YES YES YES
0xx (codes/numbers) YES YES YES
1xx (creator or preferred title)
NO NO YES
240 (preferred title) NO NO YES
245 |a |n |p |b (title) NO NO CORRECT ERRORS ONLY
GMD (245 |h) NO NO NO
245 |c (author) NO YES YES
246 3_ (alternate title) NO YES YES
15
Bib records – what can I or can’t I edit?Field Delete
?Add? Edit? (change
or correct data)
300 NO YES (if not present)
YES
336/337/338 NO YES* YES*
5xx fields (notes) NO YES YES
6xx fields (subjects) NO YES* YES*
700/710 (additional names)
NO YES YES
1xx/7xx |e (relationship term)
NO YES* YES*
856 41 (URLs) YES YES YES
*MUST use controlled vocabulary terms for these fields/subfields
16
Bib records – what can I or can’t I edit? 260 field versus 264 field
260: Imprint still valid if present, but not preferred, do not use
264: Production, Publication, Distribution, Manufacture, and Copyright Notice Repeatable Second indicator has meaning!
0 - Production 1 - Publication 2 - Distribution 3 - Manufacture 4 - Copyright notice date – can ONLY have a |c (date)!
Can I edit the 264? CORRECT ERRORS ONLY.
17
Authority records ALL authority records MUST be RDA compliant
as of March 31, 2013
Identification: 040 |e rda 008/10 (Rules) = z (other)
Records with a 667 note that says “DO NOT USE” Give the record to a cataloger
18
RDA Toolkit Tabs
RDA – text of RDA Tools
RDA element set RDA mappings (MARC-RDA; MODS-RDA) RDA record examples Workflows – can be global (public) or local Maps – Metadata Application Profiles Entity Relationship Diagrams (FRBR, FRAD, etc.) Schemas – element sets
Resources AACR2 LC-PCC PS (policy statements) Other (various links)
19
RDA Toolkit Updates
“When there is a new release for RDA Toolkit, it is made on the second Tuesday of the month. Releases typically contain updates to content and metadata, enhancements to RDA Toolkit functionality, and fixes to existing bugs.” (RDA Toolkit blog)
May 14, 2013 Next: July 9, 2013
Training RDA Toolkit Essentials - FREE
20
So what’s next? BIBFRAME Linked Data and the Semantic Web Tools
Bibframe.org RIMMF – RDA in Many Metadata Formats VTLS Sandbox (subscription) – “FRBRize” records Linkeddata.org
21
Wrap-up
??
22
Image created by: Jennifer Young
Northwestern University
23
Acknowledgments
Slide content credits: Library of Congress
Barbara Tillett, Judy Kuhagen, the staff of the Cataloging & Acquisitions Cooperative and Instructional Programs Division
Jacquie Samples (Duke U.) Joint Steering Committee for the Development of
RDA And many more who have contributed bits and
pieces