Transcript RDA - New York University

Essentials of RDA :
Resource Description & Access
Presented for the NYLLTSR Roundtable at
Cahill, Gordon & Reindel LLP,
April 20, 2011
George A. Prager
Head of Cataloging, New York University Law School
[email protected]
1
Outline
•
•
•
•
•
•
•
•
1. Introduction
2. Organization of RDA
3. Basic principles
4. RDA Timeline
5. RDA and OCLC
Appendix I. Most important MARC 21 Changes
Appendix II. Selected RDA Resources
Appendix III. Exercises
2
1. Introduction*
• AACR2 dates from 1978; need for new
cataloging rules suitable for the digital age
• International Conference on the Principles and
Future Development of AACR, in Toronto, 1997
• New rules in development were first called
AACR3; name changed to RDA
• Based on FRBR and FRAD entity models, as
well as the Statement of International
Cataloguing Principles (ICP) (RDA 0.3-0.4)
*This introduction is based in part upon presentations by Alan Danskin, Robert L.
Maxwell, and Barbara Tillett (citations given in Appendix II).
**The Conference was held Oct. 23-25, 1997. Nine papers were presented and
discussed at the meeting. Versions of the papers posted prior to the Conference are
available online at: http://www.rda-jsc.org/intlconf1.html
3
1. Introduction
• Shares most general principles with ICP;
Highest principle: Convenience of the user
• Designed to be compatible with pre-existing
records in AACR2 and related standards
• RDA a content standard, NOT a display
standard; RDA records may use ISBD
punctuation, MARC 21, Dublin Core, or other
encoding scheme*
*Examples of possible displays of RDA records are given in RDA Appendices D & E.
4
1. Introduction
• AACR2 used mostly by libraries; RDA intended
to be used not only by libraries, but also by
museums, archives, publishers, book dealers,
educators, ILS vendors, etc.
• AACR2 Anglocentric; RDA designed to be more
international (RDA 0.11 options regarding:
language and script of description, numerals,
dates, and units of measurement)
• AACR2 Part I organized by class of materials;
(doesn’t work well for mixed resources such as
streaming videos, online maps, etc.)
5
1. Introduction
• RDA: Designed to cover all types of resources,
including present and future types of digital
resources
• RDA: Designed to support automated data
capture, such as digital data from publisher
• AACR2: (1.0D1): Three levels of description;
Most libraries in U.S. used Second level
6
1. Introduction
• RDA: “Core elements” = the minimum set of
elements necessary to support user tasks
• Some elements are core only in certain cases
(“Core if”)
• Less detailed than AACR2 2nd level in some
areas
An example of an element that is “core” in certain
cases only: Place of distribution, if the place of
publication is unknown
7
1. Introduction
RDA core (list at RDA 0.6) includes:
Title proper (245 $a), 1st statement of responsibility
(245 $c), serials numbering elements (362), first listed
place of publication (260 $a), first listed publisher
(260 $b), date of publication (260 $c), extent (300 $a;
only if resource is complete, and extent is known),
series statement (490; NOT 800-830 series added
entry), identifier for the manifestation (020, etc.), the
new content and carrier types (336, 338), and a few
other elements; list available at:
(www.loc.gov/catdir/cpso/RDAtest/coreelements.doc)
8
1. Introduction
• RDA core does not include:
• Other title information (245 $b), parallel title (245 $b),
additional statements of responsibility relating to the title
proper (245 $c) or edition (250 $b), extent of resource (if
incomplete, 300 $a), dimensions of resource (300 $c),
notes (5XX)
• Library of Congress (LC) core includes some elements
not in RDA core
(www.loc.gov/catdir/cpso/RDAtest/training2word9.doc; &
http://www.loc.gov/catdir/cpso/RDAtest/training2word7.doc)
•
*Selective list of LC core not in RDA Core: During the RDA test, LC core also
included parallel title proper, other title information, ISSNs of series and subseries,
frequency, and dimensions of resource (except for serials)
9
1. Introduction
• National libraries, networks, and cooperative
cataloging programs (such as the Program for
Cataloging, or PCC) may decide on common
policies on which core plus elements to include
• Each institution can decide on a local policy to
include any RDA elements it wants beyond RDA
core in its own OPAC
10
1. Introduction
Vocabulary: AACR2 vs. RDA:*
• AACR2 “Heading” -> RDA “Authorized access
point”
• AACR2 “Author, composer, etc.” ->“Creator”
• AACR2 “Main entry” -> “Preferred title +
authorized access point for creator if appropriate”
• AACR2 “Uniform title” -> 1. “Preferred title (and
other information to differentiate)” or 2.
“Collective uniform title”
*The information on RDA vocabulary on this slide and the next one is from Barbara Tillett’s
presentation, listed in Appendix II.
11
1. Introduction
• AACR2 “See reference” -> RDA “Variant access
point”
• AACR2 “Chief source” -> RDA “Preferred source”
Group 3 FRBR entities (Concept, object, event,
place), not covered in first release of RDA*
• RDA first published June 2010
• Some policy decisions about changes from
AACR2 will be made after the test period
*Place names as jurisdictions, but not as subjects of works, are partially covered in
Chapter 16
12
1.Introduction
• Testing and evaluation by U.S. national libraries
and test partners, Oct. 2010-March 2011
• Decision on implementation by 3 U.S. national
libraries will be announced in June 2011
• RDA Toolkit available for subscribers: Sept. 1,
2010- ; designed as an online tool (IP address
recognition and also password access)
http://www.rdatoolkit.org/
• Also available as a print (loose-leaf) subscription
13
2. Organization of RDA*
• RDA organized by FRBR and FRAD entities and
attributes (RDA 0.5)
• RDA has 10 sections
• First part: Records attributes for FRBR entities
• Second part: Records relationships between
FRBR entities
*This section is based in part on FAQ 4.1 on the JSC’s Website (http://www.rdajsc.org/rdafaq.html).
14
2. Organization of RDA
Recording attributes for FRBR entities:
• Section 1 - Recording attributes of manifestation
and item
• Section 2 - Recording attributes of work and
expression
• Section 3 - Recording attributes of person, family,
and corporate body
• Section 4 - Recording attributes of concept,
object, event, and place (most of this section
needs to be added in a future release of RDA)
15
2. Organization of RDA
Recording relationships:
• Section 5 - Recording primary relationships
• Section 6 - Recording relationships to persons,
families, and corporate bodies associated with a
resource
• Section 7 - Recording subject relationships (to
be added in a future release of RDA)
• Section 8 - Recording relationships between
works, expressions, manifestations and items
16
2. Organization of RDA
Recording relationships (continued):
• Section 9 - Recording relationships between
persons, families, and corporate bodies
• Section 10 - Recording relationships between
concepts, objects, events, and places (to be
added in a future release of RDA)
17
3. Basic Principles of RDA:
3.1. Take What You See
• AACR2 (1.1B1, etc.) has rules on changing
capitalization and punctuation appearing in
statements of responsibility, edition statements,
series statements, and some other areas
• AACR2 (1.1F7) also does not usually transcribe
certain words in statements of responsibility,
such as titles of persons (Dr., Reverend, etc.)
18
3.1. Take What You See
• RDA: Basic rule is: Take what you see
• Applies to all transcribed fields
– Sometimes options to omit certain
information*
• Follows the ICP principle of “Representation”**
• Facilitates automated data capture
*We will look at some examples later. In some RDA transcribed elements, there are
options to abbreviate or shorten the data in certain ways
**Representation: ICP 2.3: Descriptions and controlled forms of names should be based
on the way an entity describes itself
19
3.1 Take What You See
– Includes punctuation, abbreviations, spelled
out words, Roman numerals, inaccuracies
– Don’t abbreviate words that aren’t abbreviated
in the source
– Capitalization: Follow policy of cataloging
agency or just “take what you see”
20
3.1 Take What You See
• Transcribed fields in RDA: titles
– Title proper, parallel title proper, other title
information, statement of responsibility
relating to title proper (MARC 21 field 245 $a,
$b, and $c)
– Earlier title proper (MARC 247)
– Later title proper (MARC 246)
– Key title (MARC 222)
– Abbreviated title (MARC 210)
21
3.1 Take What You See
•
•
•
•
Other transcribed fields in RDA:
Edition statements (MARC 250)
Imprint statements (MARC 260)
Numeric, alphabetic, and chronological
designations (MARC 362)
• Series statements (MARC 490)
• Some transcribed fields: Take what you see, or
follow policy of cataloging agency, network, or
program
22
3.1 Take What You See:
3.1.1 Capitalization, etc.
• In source: THE STORY OF MY LIFE by the RECENTLY
retired George Prager, MA, MLS, Member of the
American Library Association // Fourth Edition
• AACR2: The story of my life / by George Prager. 4th ed.
• RDA (with ISBD punctuation): THE STORY OF MY LIFE
/ by the RECENTLY retired George Prager, MA, MLS,
Member of the American Library Association. -- Fourth
Edition.
• RDA options: omit extra words in statement of
responsibility & follow agency decisions with
capitalization
23
3.1.2 Take What You See:
Inaccuracies
• Transcribe errors found on the resource
• Optionally, make note and/or added entry with
corrected form if useful for users of catalog
• T.p. on resource: The hsitory of Casalini Libri
• AACR2: The hsitory [sic] of Casalini Libri (or:
The hsitory [i.e. history] of Casalini Libri)
• RDA: The hsitory of Casalini Libri.
• RDA exception for continuing resources*: Correct the
title and make a note/added entry on form in source
*The exception for continuing resources is to keep the RDA rules for serials in agreement
with the ISBD and the ISSN Network rules
24
3.2 Replacement of GMD (General
Material Designation)
• AACR2 allowed only 1 GMD for each
manifestation; sometimes 2 or more might apply
• GMD replaced by three new RDA elements:
• Content type (RDA Core; MARC 21 field 336)
– Applies to FRBR expression level
• Media type (Not RDA Core; MARC field 337)
– FRBR manifestation level; may be able to
automatically generate from content and carrier types
• Carrier type (RDA Core; MARC field 338)
– FRBR manifestation level
25
3.2 Replacement of GMD
MARC 21 specifics:
• RDA allows use of term (MARC $a) and/or code
(MARC $b)
• RDA includes lists of terms or codes; also allows
use of “other” or “unspecified”; lists also
available from:
http://www.loc.gov/standards/valuelist*
• Both subfields may be repeated if more than one
type is appropriate, and terms or codes are from
the same vocabulary
*Terms developed to be compatible with the ONIX standards for electronic
information interchange used by publishers
26
3.2 Replacement of GMD
• Source term is given in $2
• Materials specified may be given in $3
• Example: Printed Book
• 245 13 $a Lo strano natale di Mr. Scrooge : $b e
altre storie / $c Dino Buzzati.
• 300 ## $a 364 pages ; $c 23 cm.
• 336 ## $a text $b txt $2 rdacontent
• 337 ## $a unmediated $b n $2 rdamedia
• 338 ## $a volume $b nc $2 rdacarrier
27
3.2 Replacement of GMD
Example: Updating Web resource with text and
audio
245 04 $a The Oyez Project : $b U.S. Supreme
Court media.
300 ## $a 1 online resource.
336 ## $a text $b txt $a spoken word $b spw $2
rdacontent
337 ## $a computer $b c $2 rdamedia
338 ## $a online resource $b cr $2 rdacarrier
28
3.2 Replacement of GMD
• OPAC display: Library may prefer to generate
one or more icons from text or code in these
three RDA elements
• Fields could also be suppressed from public
display
• Information in these 3 RDA elements could be
used to limit searches
• Offers more flexibility and better for user than
GMDs
29
3.3 Fewer abbreviations in RDA
• RDA uses few abbreviations; avoids Latin
abbreviations (ICP principles: Convenience of
the user, and: Common usage)
– Statement of responsibility:
AACR2 (1.1F5) uses “… [et al.]” when
statement of responsibility in source contains
names of more than three persons or
corporate bodies performing the same
function
RDA (2.4.2) does not use abbreviations in
statement of responsibility unless in source 30
3.3 Fewer Abbreviations in RDA
– Edition statements:
AACR2 abbreviates; RDA does not use
abbreviations unless abbreviation appears in
source
– Imprint statements:
AACR2 (1.4C6, 1.4D6): [s.l.] or [s.n.] for
unknown place of publication or unknown
publisher
RDA (2.8): [Place of publication not identified]
and [publisher not identified]*
*See also section 3.7 for how to avoid using these phrases
31
3.3 Fewer abbreviations in RDA
– Physical description: AACR2 uses p., ca., i.e.,
v., ill., col., ports., cm., and other
abbreviations
– RDA does not abbreviate any of these terms;
– “cm” is not abbreviated, but usually ends in a
period if MARC 21 and ISBD punctuation are
used (i.e., at the end of a 300 field)
AACR2: 300 ## $a 25 p. : $b ill. (some col.) ; $c 28 cm.
RDA: 300 ## $a 25 pages : $b illustrations (some
colored) ; $c 28 cm.
32
3.3A Sources of Information (RDA 2.2)
• “Preferred sources of information” (RDA
2.2.2) replaces the AACR2 concept of chief
source of information
• Three categories for sources (simplified):
– a. Pages, leaves, sheets, or cards: use t.p. or t.p.
substitute (priority list)
– b. Moving images: use title frame; alternative to use
eye-readable label
– c. All other resources: use permanent label or
embedded metadata
33
3.3A Sources of Information (RDA 2.2)
Other sources of information (RDA 2.2.4):
• May take information from anywhere in
resource, or from outside the resource, for fields
listed in 2.2.4
• Information supplied from outside the resource:
indicate by a note field or some other method,
such as coded data, or brackets around the
supplied data
• LCPS 2.2.4: LC uses square brackets
34
3.4 “Rule of three” eliminated*
• AACR2 allowed transcription of up to only three
authors for work of shared responsibility (1.1F5)
• RDA: No “rule of three”; transcribe every name
in statement of responsibility (RDA 2.4.1.5)
• RDA option (2.4.1.4-2.4.1.5) to transcribe first
name and summarize others
*“The rule of three” was a principle of the international Paris Principles of 1961,
predecessor of the International Statement of Cataloguing Principles,
finalized in 2009
35
3.4 “Rule of three” eliminated
• AACR2: 245 00 $a Building your civil trial skills /
$c authors, Nelson T. Abbott … [et al.].
• RDA: 245 10 $a Building your civil trial skills / $c
authors, Nelson T. Abbott, Tim Dalton Dunn,
John A. Snow, Todd D. Weiler.
• RDA option: 245 10 $a Building your civil trial
skills / $c authors, Nelson T. Abbott [and three
others].
36
3.4 “Rule of three eliminated:
3.4.1.Unlimited name access points*
• AACR2 usually no more than 3 access points for
persons performing the same function
• RDA core requires access point for creator of
work
• RDA places no limits on number of additional
access points
*The Rule of three has often not been followed in AACR2 cataloging of moving images,
rare materials, and archival materials
37
3.4.1 Unlimited Name Access Points
RDA:
100 1# $a Abbott, Nelson T.
245 10 $a Building your civil trial skills / $c
authors, Nelson T. Abbott, Tim Dalton
Dunn, John A. Snow, Todd D. Weiler.
700 1# $a Dunn, Tim Dalton.*
700 1# $a Snow, John A., $d 1948- *
700 1# $a Weiler, Todd D.*
*Only the access point for the first named or primary creator is required
38
3.4.1 Unlimited Name Access Points
RDA core:
100 1# $a Abbott, Nelson T.
245 10 $a Building your civil trial skills / $c authors,
Nelson T. Abbott [and three others].
39
3.5 Main Entry
• AACR2: Works of shared responsibility, more than 3
authors: title main entry; added entry for first named
author
• RDA: Authorized access point (1XX) under the principal
or first-named creator (RDA core), if principal
responsibility is not indicated. Creator may be a person,
family, or corporate body
RDA 19.2: “If there is more than one creator responsible for
the work, only the creator having principal responsibility
named first in resources embodying the work or in
reference sources is required. If principal responsibility is
not indicated, only the first-named creator is required.”
40
3.5 Main Entry
AACR2:
245 00 $a All about Ohio / $c contributors, Susan
Doll … [et al.].
700 1# $a Doll, Susan, $d 1954RDA:
100 1# $a Doll, Susan, $d 1954245 10 $a All about Ohio / $c contributors, Susan
Doll [and fifteen others].
(may list 1 or any other number of the 16
contributors in the statement of responsibility) 41
3.5A Preferred Title for a Compilation
of Works (RDA 6.2.2.10)
• Significant changes from AACR2!
• RDA (17.4, 17.8/17.10): For all compilations by
one or more creators, it is a core requirement to
record the primary relationship between the
work/expression and the manifestation that
embodies it. This may be done as:
– a. an identifier (lccn, etc.) for the
work/expression manifested
– b. an authorized access point
– c. a composite description (a note such as:
Rev. ed. of: …)
42
3.5A Preferred Title for a Compilation
of Works (RDA 6.2.2.10)
• The LCPS for 17.8 and 17.10 calls for an authorized
access point for the predominant or first work/expression
in the compilation (i.e., an analytical added entry).
Additional authorized access points may be given for the
other works/expressions in the resource
• For compilations without a collective title, there is an
RDA alternative for the cataloger to devise a title proper,
instead of or in addition to identifying all of the
works/expressions in the compilation, but the primary
relationship must still be recorded
43
3.5A Preferred Title for a Compilation
of Works (RDA 6.2.2.10)
• AACR2 (21.7C): For a resource without a collective title
consisting of 2 or three works by 2 or 3 authors, enter
under the first author, and code the first work as the title
proper (245 $a). AACR2 has no option to devise a title
proper for compilations
• RDA alternative (6.2.2.10.3): For all compilations of two
or more works by the same creator, you may also give a
conventional collective title such as “Works. Selections”,
or “Plays. Selections”, instead of, or in addition to the
analytical added entries (or identifiers, or composite
descriptions). But you still must have the entry for the
first work/expression manifested. LCPS: LC follows this
alternative
44
3.5A Preferred Title for a Compilation
of Works (RDA 6.2.2.10)
(Made-up example):
100 1# $a Prager, George $q (George Allen), $d 1952240 10 $a Works. $k Selections.*
245 10 $a RDA in literature / $c by George Prager.
505 0# $a An ode to RDA -- RDA, the drama.
700 12 $a Prager, George $q (George Allen), $d 1952- $t
Ode to RDA.
700 12 $a Prager, George $q (George Allen), $d 1952- $t
RDA, the drama.**
*This collective title is optional in RDA
**This second analytical access point is optional in RDA
45
3.6 Relator Terms and Codes
• Relator terms: Optional use of RDA Appendix I
terms to express possible relationships between
a resource and persons, families, and corporate
bodies (FRBR Group 1 and Group 2 entities)
• Relator codes: Codes from MARC Code List for
Relators (http://www.loc.gov/marc/relators/)
may be used instead
• May repeat relator term or code if person or
corporate body performs multiple functions
46
3.6 Relator Terms and Codes
100 1# $a Abbott, Nelson T., $e author.
245 10 $a Building your civil trial skills / $c authors
Nelson T. Abbott, Tim Dalton Dunn, John A.
Snow, Todd D. Weiler.
700 1# $a Dunn, Tim Dalton, $e author.
700 1# $a Snow, John A., $d 1948- $e author.
700 1# $a Weiler, Todd D., $e author.
Relator codes can be used instead:
100 1# $a Abbott, Nelson T., $4 aut
47
3.7 Publication, Distribution, etc.
Statements (RDA 2.7-2.11)
• Date of production is a core element for
resources issued in an unpublished form
• First named place of publication, First named
publisher, and Date of publication are core
elements for published resources
• Errors in publication, distribution, statement:
– Transcribe as it appears; optionally, make a
note, if considered important
48
3.7 Publication, Distribution, etc.
Statements
• Place of publication unknown and unable to guess at a
probable place of publication, use:
[Place of publication not identified]
• Unknown place of publication: Place of distribution
becomes core
• Unknown place of distribution: Place of manufacture
becomes core
• Probable place of publication:
– Can avoid “[Place of publication not identified]” by
giving probable place or country of publication in
brackets: “[Italy?]”
49
3.7 Publication, Distribution, etc.
Statements
Adding name of larger place after known place of
publication:
AACR2 allows: “Cizur Menor [Navarra]” or “Cizur
Menor [Spain]” even if only “Cizur Menor”
appears in the source. RDA does not allow this.
Instead, you can add a note
50
3.7 Publication, Distribution, etc.
Statements
Library of Congress policy statements (LCPS) for
RDA 2.8.4.2: LC practice: “Supply a probable
place of publication if possible rather than give
‘[Place of publication not identified]’ and then
give place of distribution or of manufacture
• Publisher’s name unknown:
Use: [publisher not identified]
Distributor’s name becomes core
No distributer’s name: manufacturer’s name
becomes core
51
3.7 Publication, Distribution, etc.
Statements
• Use brackets if date is taken from outside resource
• No date of publication:
– For single-part monographs, use: [date of publication
not identified]*
– Distribution date becomes core
– No distribution date: Copyright date is core
– No copyright date: Date of manufacture is core
– Only copyright date:
260 ## $a New York : $b Scribner’s, $c [copyright
symbol]2003.
*But see next slide for ways of avoiding using this phrase!
52
3.7 Publication, Distribution, etc.
Statements
• Alternatives to using “[date of publication
not identified]”:
• May supply probable date or range of dates, or
known range of dates (RDA 1.9.2)
• Add question mark if date/s are probable date/s
• Some examples:
• [2011?], [2009 or 2010], [between 1800 and
1900?], [not after March 8, 2011], [not before
January 1, 2010], [between November 3, 2008
and January 4, 2011]
53
3.7 Publication, Distribution, etc.
Statements
• For resources other than single part
monographs: if no date from first and/or last
issue can be found, then supply an approximate
date or dates of publication. If no approximate
date or dates can be found, then leave the date
of publication blank (do not include “[date of
publication not identified]” (RDA 2.8.6.5 & LCPS
2.8.6.6)
54
3.8 Carrier Description
Extent of Resource (300 $a; RDA 3.4):
Core element only if resource is complete, or if total extent
is known
• 300 leaves
• 40 unnumbered pages
• 1 volume (unpaged) – resource is complete
• approximately 45 pages – RDA does not use “ca.”
• 2000 leaves in various pagings
• 1 volume (various pagings)
• volumes - for incomplete (textual) resource, or if the total
number of units issued is unknown (3.4.10)
55
3.8 Carrier Description
Extent of Resource (cont.):
• 1 online resource (68 pages)
• Terms in common usage are also allowed (RDA
3.4.1.5):1 USB flash drive
• Only a few abbreviations are allowed, such as
“ft.” for foot or feet, and “in.” for inch or inches,
when used for recording the storage space of
collections (RDA 3.4.1.11); abbreviations given
in RDA Appendix B.5.2.
• Metric symbols are used, but are not considered
56
abbreviations (m, cm, etc.)
3.8 Carrier Description
• Misleading numbering: Leave uncorrected
unless it creates a completely false impression:
309, that is, 409 pages
• Other physical details (300 $b):
– Few abbreviations allowed
– Some details are covered in Chapter 3 on
carriers, such as encoding formats (RDA
3.19)
57
3.8 Carrier Description
– Many other physical details are covered in RDA
Chapter 7 as attributes of expressions (7.15:
illustrations; 7.17: color; 7.18: sound, etc.)
• Dimensions: (300 $c; RDA 3.5):
• Not RDA Core
• Metric symbols are generally used
• LCPS has one exception from RDA 3.5.1.4.4: use
inches (abbreviated “in”) for discs, rather than
centimeters (cm)
58
3.9 Series Statements (RDA 2.12)
• Record the series statement as it appears on
the resource
• Series numbering (follows RDA 1.8.2): Record
numerals in the form preferred by the agency
creating the data, unless the substitution would
make the numbering less clear
Alternative 1: Record numbering in the form it
appears on the piece (LC follows this
alternative)
59
3.9 Series Statements
• Alternative 2: Also add the equivalent numerals in the
form preferred by the agency creating the data, and give
the source of the data in a note:
tomo II [2]
Note: Numbering within series on source of information
reads: tomo II
• Captions in series numbering are not usually
abbreviated in RDA, but there is an option to follow
agency’s guidelines in this regard (1.7)
Authorized access points for series: see RDA & LCPS
6.27.1; series numbering: RDA/LCPS 24.6 (refers again
back to 1.8.2)
60
4. RDA Timeline
• June-Sept. 2010: Training and practice for RDA
official test participants (26 U.S. libraries)
• Oct. 1-Dec. 31, 2010: Record creation
30 common resources (original & copy
cataloging)
25 extra set records (original or copy cataloging
titles)
All records collected by LC and made freely
available in late 2010
Online survey for common set records for all test
participants
61
4. RDA Timeline
• Jan.-Mar. 2011: Analysis of test results & preparation of
recommendations by U.S. RDA Test Coordinating
Committee
• Apr.-June 2011: Decision on implementation and a
public report; Report will be issued before ALA Annual
• Four possible decisions:
– Do not implement RDA
– Postpone implementation until certain changes are
made
– Implement RDA
– Implement RDA with specific recommended changes
or policy decisions for US libraries
62
4. RDA Timeline
• Widespread adoption of RDA in U.S. unlikely
until after the public report is released
• Earliest implementation: 3rd quarter 2011
(probably later)
• Many European countries adopting a “wait and
see” policy (waiting to see what LC decides)
(More information at
http://www.loc.gov/catdir/cpso/RDAtest/admindo
c9.doc)
63
5. RDA and OCLC
• OCLC policy statement on RDA Cataloging in
WorldCat for the U.S. testing period
• Sept. 2010- : Any OCLC member library may add an
original record in AACR2 or RDA to OCLC for any
resource that lacks a record in the same language of
cataloging. If a full level AACR2 or RDA record already
exists, a record in the other code should not be added to
Worldcat
• A WorldCat full-level master record should not be edited
to change it from one set of rules to another (see
exception on next slide for serials and integrating
resources)
64
5. RDA and OCLC
• AACR2 records for continuing resources may be
changed to RDA. Once changed to RDA, the
record should not be changed back to AACR2
• Less than full level monographic records may be
changed from AACR2 to RDA
• Copy cataloging: Catalogers may locally edit
records created under any rules to another set
of rules
• Full OCLC policy statement:
http://www.oclc.org/rda/policy.htm (last updated
June 15, 2010)
65
Appendix I. Most Important MARC 21
Changes: I.A. Bibliographic Records
• Leader 18 Descriptive cataloging form
• Most Anglo-American libraries will use: “i” (ISBD
punctuation included)
• 040 Cataloging source
Use $e rda (additional codes may apply)
English language RDA record created by New
York University Law School:
040 ## $a NNU-L $b eng $c NNU-L $e rda
66
Appendix I.A. Bibliographic Records
• 336-338 Content type, Media type, and
Carrier type (see Section 3.2)
• 502 Dissertation Note: New subfields for RDA
sub-elements ($a may still be used instead)
– Degree type, Name of the granting institution,
Year degree granted, etc.
• 518 & 033 Date/Time & Place of an Event
– New subfields added to both fields
– 518 may use new subfields or $a alone
67
Appendix I. Most Important MARC 21
Changes: I.B. Authority Records
• 008/10 Descriptive cataloging rules
– Use “z” other
• 040 $e Description conventions
– Use “rda”
68
Appendix I.B. Authority Records
New MARC 21 Authority Fields:
046 Special coded dates
336 Content type
370 Associated place
371 Address
372 Field of activity
373 Affiliation
374 Occupation
69
Appendix I.B. Authority Records
New MARC 21 Authority Fields (cont.)
375 Gender
376 Family information
377 Associated language
380 Form of work
381 Other distinguishing characteristic of
the work/ … of the expression
382 Medium of performance
383 Numeric designation of a musical work
70
384 Key
Appendix I.B. Authority Records
General overview of 046, 370-384 fields:
• RDA allows certain elements to be recorded
either as part of access point for the entity, as
separate identifying elements, or both
• New fields and subfields “contain additional
information about characteristics of heading
entities in fields 100-185”
• All of the fields are repeatable, except 384
• Source of information for 046, 370-377:
– Give in $v, $u, or in 670 field
71
Appendix II. Selected RDA Resources
• Coyle, Karen. RDA Vocabularies for a Twenty-First
Century Data Environment. Chicago, Ill. : American
Library Association, 2010 (Library technology reports ; v.
46, no. 2 Feb./Mar. 2010)
• Danskin, Alan. A Long and Winding Road: RDA from
Principles to Practice; http://www.rdajsc.org/docs/A_long_and_winding_road_format_150310.
pdf (last updated March 16, 2010)
• EURIG-JSC seminar on RDA: "RDA in Europe: making it
happen!" Aug. 8, 2010
http://www.slainte.org.uk/eurig/meetings.htm
• Hart, Amy. The RDA Primer: a Guide for the Occasional
Cataloger. Santa Barbara, Calif. : Linworth, 2010. ISBN:
9781586833480 (also available as an e-book)
72
Appendix II. Selected RDA Resources
• Joint Steering Committee for Development of
RDA http://www.rda-jsc.org/rda.html (list of links)
• Kuhagen, Judith A. RDA Essentials. Connecticut
Library Association. Nov. 4, 2010.
http://www.rdajsc.org/docs/ConnLA_Tech_6nov2010.ppt#413,
142,Inform your library’s users
• LC documentation for the RDA … test
http://www.loc.gov/catdir/cpso/RDAtest/rdatest.h
tml (list of links)
73
Appendix II. Selected RDA Resources
• Maxwell, Robert L. Introduction to RDA. Utah
Library Association, May 14, 2010;
http://www.rdajsc.org/docs/RDA_part_1_201005.pdf
• Maxwell, Robert L. RDA in Depth: Differences
Between RDA and AACR2. Utah Library
Association, May 14, 2010; http://www.rdajsc.org/docs/RDA_part_2_201005.pdf
• McCallum, Sally. RDA in MARC;
http://www.loc.gov/marc/RDAinMARC29.html
(last updated Jan. 5, 2011)
74
Appendix II. Selected RDA Resources
• Oliver, Chris. Introducing RDA: a Guide to the
Basics. Chicago : American Library Association,
2010. ISBN 9780838935941
• PoCo Discussion Paper on RDA Implementation
Alternatives (Apr. 5, 2011; rev. Apr. 15, 2011);
http://www.loc.gov/catdir/pcc/PoCo-RDADiscussion-Paper040511.pdf
• Prager, George. MARC 21 Changes for RDA.
Presented at the Program: MARC and RDA: an
Overview, July 12, 2010;
http://www.aallnet.org/sis/tssis/annualmeeting/20
10/handouts/g5-marcandrda-prager-handout.pdf
75
Appendix II. Selected RDA Resources
• Prager, George. RDA, MARC 21, and Access Points.
Casalini Libri, Mar. 22, 2011 (available upon request)
• RDA and OCLC http://www.oclc.org/rda/about.htm (list of
links)
• RDA and PCC http://www.loc.gov/catdir/pcc/RDAPCC.html (list of links)
• Schiff, Adam L. Changes from AACR2 to RDA: a
Comparison of Examples; http://www.rdajsc.org/docs/BCLAPresentationWithNotes.pdf (last
updated Apr. 22, 2010?)
• Tillett, Barbara B. RDA Changes from AACR2 for Texts;
http://www.rda-jsc.org/rdapresentations.html (last
updated Jan. 12, 2010?)
76
Appendix III. Exercises
Each exercise has an image of the title
page and blank workforms to give
selected AACR2 and RDA fields. RDA
answer sheets are at the end
77
Exercise 1. AACR2:
• 100 __ $a
• 245 __ $a
• 260 __ $a
• 300 __ $a
• 490 __ $a
• 700 __ $a
78
Exercise 1. RDA:
• 040 $e
• 100 __ $a
• 245 __ $a
• 260 __ $a
• 300 __ $a
• 336 __ $a $2
• 337 __ $a $2
• 338 __ $a $2
• 490 __ $a
• 700 __ $a
79
Exercise 2. AACR2:
• 100 __ $a
• 245 __ $a
• 250 __ $a
• 260 __ $a
• 300 __ $a
• 490 __ $a
• 700 __ $a
•
Exercise 2 has imprint statement on
t.p. verso: Tottel Publishing;
80
Maxwelton House, 41-43 Boltro Road,
Haywards Heath, West Sussex; c2007
Exercise 2. RDA:
•
•
•
•
•
•
•
•
•
•
040 __ $e
100 __ $a
245 __ $a
250 __ $a
260 __ $a
300 __ $a
336 __ $a
337 __ $a
338 __ $a
490 __ $a
$2
$2
$2
81
81
Appendix III. Exercises. III.1., The
Subject of Philosophy
•040 ## $e rda
•100 1# $a Lacoue-Labarthe, Philippe.
•245 14 $a The Subject of Philosophy /
$c Philippe Lacoue-Labarthe.
•260 ## $a Minneapolis : $b University
of Minnesota Press, $c [date of
publication not identified], [copyright
symbol]1993.
82
Appendix III. Exercises. III.1, The
Subject of Philosophy (cont.)
•300 ## $a xx, 202 pages ; $a 23 cm.
•336 ## $a text $b txt $2 rdacontent
•337 ## $a unmediated $b n $2
rdamedia
•338 ## $a volume $b nc $2 rdacarrier
•490 0# $a Theory and History of
Literature ; $v Volume 83
83
Appendix III. Exercises. III.1., The
Subject of Philosophy
• The above display is RDA core
• All MARC 21 RDA records should have: 040 $e rda
• Main entry (100): RDA core requires that an authorized
access point be made for the creator of a work or
expression. RDA core +: You can make any number of
additional access points for editor, translators,
consultants, etc.
• RDA core +: Relator term ($e) or code ($4) can be used
at the end of the 100 field, and any 700 fields
• Alternate display of title proper (245 $a): You can either
use the capitalization as found on the item, or capitalize
according to the policy of the cataloging agency (such as
following some other citation standard or style manual)
84
Appendix III. Exercises. III.1., The
Subject of Philosophy
• Statement of responsibility (245 $c): RDA core only
requires display of the first statement of responsibility.
RDA core +: May give one or all additional statements of
responsibility in source. May give each statement in full,
or summarize.
• Alternate display of imprint (260): In RDA core, you can
also use 260 $c [1993?] as probable publication date
and omit the copyright date: 260 ## $a Minneapolis : $b
University of Minnesota Press, $c [1993?]
• RDA core +: You can use probable publication date
followed by copyright date: [1993?], [copyright
symbol]1993.
85
Appendix III. Exercises. III.1., The
Subject of Philosophy
• It is only required to list the first place of
publication; If desired, other places of
publication may be listed as well: 260 ## $a
Minneapolis ; $a London. You are not allowed to
add [Minn.] or [Minnesota] after “Minneapolis”, if
it does not appear in the source. If the location of
the place given in the source is not well known,
you can add a note (500) giving more
information about the place of publication, such
as the name or names of larger jurisdictions
(county, state, country, etc.)
86
Appendix III. Exercises. III.1., The
Subject of Philosophy
• Physical description (300 field): Abbreviations for
“pages” is not used in RDA; “cm.” has a period in a
MARC 21/ ISBD display because it is at the end of a 300
field (it is not considered an abbreviation)
• Content type (MARC 336) and carrier type (338) are
required in RDA core; media type (338) is not. Terms or
codes can be used alone, or both can be used in
combination with each other
• Series statement (490): You can either accept
capitalization as found in chief source, or follow the
policy of the cataloging agency. “Volume” is not
abbreviated in the series numbering
87
Appendix III. Exercises. III.2., Local
Government Contracts …
•040 ## $e rda
•245 00 $a Local Government
Contracts and Procurement / $c
General Editor, Helen Randall, Partner,
Trowers & Hamlins; Chair, New Local
Government Network.
•250 ## $a Second edition.
•260 ## $a Haywards Heath, West
Sussex : $b Tottel Publishing, $c
[2007?]
88
Appendix III. Exercises. III.2., Local
Government Contracts … (cont.)
•300 ## $a xxxvi, 710 pages : $b
illustrations ; $c 26 cm.
•336 ## $a text $b txt $2 rdacontent
•337 ## $a unmediated $b n $2
rdamedia
•338 ## $a volume $b nc $2 rdacarrier
•700 1# $a Randall, Helen, $e editor.
89
Appendix III. Exercises. III.2., Local
Government Contracts … (cont.)
• Absence of 1XX field: Like AACR2, RDA does not use
the name of an editor as a main entry
• Statement of responsibility: You can transcribe what’s on
title page, or give simply “Helen Randall” in 245 $c
(following RDA omit to leave out titles and inessential
information given in statement of responsibility)
• Alternate display: 245 00 $a Local Government
Contracts and Procurement / $c General Editor, Helen
Randall ; $a Assistant to the Editor, Nicola Ihnatowicz ;
$a Contributors, Richie Alder [and 34 others]. If you
wish, you could list all the contributors in the 245 $c!
90
Appendix III. Exercises. III.2., Local
Government Contracts … (cont.)
• Imprint (260): Alternately, you could use:
Haywards Heath, West Sussex : $b Tottel
Publishing, $c [date of publication not
identified],[copyright symbol]2007. In RDA, you
would not use “West Sussex” instead of “W.
Sussex”, or to use “Tottel”, or “Tottel Pub.”,
instead of “Tottel Publishing”. For place of
publication, you could include all the information:
“Maxwelton House, 41-43 Boltro Road,
Haywards Heath, West Sussex” if you wish. You
are not allowed to add [England] to the 260 $a, if
it’s not in the source
91
Appendix III. Exercises. III.2., Local
Government Contracts … (cont.)
• Physical description (300): RDA uses “illustrations”
rather than “ill.”, and “pages” rather than “p.”
• Use of relator term in 700 field is optional. Also, a relator
code could be used instead
• Name access points (700): You can have added entries
for none or all of the people given in the chief source,
whether listed in the 245 $c or not. Most catalogers
would choose to have at least a 700 field for the general
editor, both in an AACR2 and in an RDA record. Use of
the relator term in 700 $e is optional
92
Questions?
Thank you very much!
93