2. Agenda
• RDA Basics
• RDA Updates Since Implementation
• Real World RDA
• RDA Copy Cataloging Exercise
• Toolkit Problem Solving
• Lunch
• Record Creation
• Changes for the Future
6. Rule of Three is Gone
Source: by Susan Brown, Melanie Carlson, Stephen
Lindell, Kevin Ott, and Janet Wilson.
AACR2:
by Susan Brown … [et al.].
RDA:
by Susan Brown, Melanie Carlson, Stephen Lindell,
Kevin Ott, and Janet Wilson.
RDA allows:
by Susan Brown [and four others].
7. Latin Terms are Gone
AACR2:
[S.l. : s.n.], 2008.
RDA:
[Place of publication not identified] : [Publisher
not identified], 2008.
8. GMD is Gone
GMD (General Material Designation) = bracketed
information in the title that conveys the type of
material
[electronic resource]
[sound recording]
[videorecording]
9. GMD is replaced by:
–Content type (text, performed music, spoken
word, etc.)
–Media type (audio, microform, video, etc.)
–Carrier type (audio disc, online resource,
videodisc, etc)
Terminology comes from lists in the RDA
guidelines.
20. Process for updating RDA
• constituency proposals for changes in intent of
existing instructions and addition of new
instructions
• a “fast track” process for correction of
typographical errors, addition or removal of
examples, addition of terms to vocabularies,
addition of references, clarification in
wording, etc.
http://www.rda-jsc.org/rdaupdating.html
21. Updates since March 2013
• http://www.loc.gov/aba/rda/pdf/summary_rd
a_changes_2013.pdf
• http://www.loc.gov/aba/rda/pdf/summary_rd
a_changes_2014.pdf
22. Summary of Updates
• New instructions for sources of information
for online resources
• Added wording about braille to font size
• Additions to glossary
• Additions to Appendix I - relationship
designators
• Clarification of inclusion of core vs. non-core
elements
23. Real World RDA
Photo credit: https://www.flickr.com/photos/mniemand/3254191378/
25. OCLC Policy - Hybrid Records
When editing and replacing master records in WorldCat, catalogers
may choose to add some RDA elements to existing non-RDA records
without re-cataloging the entire record according to RDA. Candidates
for such editing include, but are not limited to:
• Adding relator terms to access points
• Spelling out non-transcribed abbreviations
• Adding complete statements of responsibility in 245 (in place of "[et
al.]")
• Adding 336/337/338 fields
When adding or editing one or more such elements in the master
record without re-cataloging the record to RDA, do not code the
record as RDA. OCLC will generally adhere to the PCC Guidelines on
Hybrid Bibliographic Records and expects member libraries editing
existing records to add selected RDA elements to follow these
guidelines.
33. How to Identify an RDA Record
• 040 $e = rda
• Descriptive cataloging form = i
34. Data Elements to Check
• Title and statement of responsibility - MARC
field 245
• Edition statement - MARC field 250
• Publication information - MARC field 264
• Physical Description - MARC field 300
• Content, media & carrier types - MARC fields
336, 337 & 338
35. Title and statement of responsibility -
MARC field 245
Ensure that RDA instructions have been followed:
• Delete “[sic]” or “[i.e., ___].”
• Remove $h if present.
• Ensure the presence of the first statement of
responsibility.
• In an existing statement of responsibility, replace
a supplied “[et al.]” with a full transcription of the
statement as on the source, or record “[and ___
others]”
36. Edition statement - MARC field 250
Ensure that the edition statement has been
recorded exactly as it appears on the resource:
• Expand unauthorized abbreviations to the full
form
• Record numerals as found on the resource
37. Publication information - MARC field
264
• Ensure that the field is tagged as a 264 field
and use the appropriate 2nd indicator value
based on the content of the field.
• Remember that there is no ‘home country’
requirement for either place or publisher
• Ensure that the data has been transcribed
according to RDA instructions
38. Place of publication - 264 $a
• Ensure that the first place of the first publisher
is transcribed as found in the resource.
• Include both the local place name and the
larger jurisdiction, if present on the source
• Replace “[S.l.]” with a supplied place
(preferable) or “[Place of publication not
identified]”.
39. Publisher - 264 $b
• Ensure that the first publisher is transcribed as
found in the resource
• Expand abbreviations as applicable, and add
missing words in the name of the publisher.
• Add levels of hierarchy that have been
omitted from the imported record
40. Date of publication - 264 $c
• Ensure that the date is transcribed as found on
the resource
• Ensure that the date of publication is given even
if it is a supplied date (e.g., it is often possible to
supply a publication date, inferred from a
copyright date)
• You may, additionally -- but are not required to --
record a copyright date in a separate 264 field,
with a second indicator of “4”; if recorded, this
field contains only $c and the must be used.
42. Content, media & carrier types - MARC
fields 336, 337 & 338
• Ensure that $a contains the appropriate term
from RDA for the resource in hand
43. Access Points to Check
• Creator - MARC field 1XX
• Other creators, contributors & other entities -
MARC field 7XX
44. Creator - MARC field 1XX
• Ensure that the principal or first-named
creator has been recorded in the 1XX field, for
a work by a single creator or by a group of
collaborators.
• Note, especially, situations with more than 3
entities in a single statement of responsibility,
which would have been ‘title main entry’
according to AACR2; remove a 7XX incorrectly
provided for the first creator in such cases.
45. Other creators, contributors & other
entities - MARC field 7XX
• To the extent possible, accept the
complement of 7XX fields in the imported
record.
• Remember that the concept of “justification”
is not present in RDA; an access point may be
provided for an entity that is not recorded
elsewhere in a descriptive element.
46. Copy Cataloging Using RDA training
materials from Library of Congress
http://www.loc.gov/catworkshop/RDA%20training%20materials/
50. Exercise
Scenario: Two resources by the same author.
One uses accent marks in the name, one does
not. There is no AAP in the authority file.
How should you record the name (i.e., with or
without diacritic marks) in the 100 field?
51. Exercise
Scenario: Title page has Second edition; Spine
has 2nd edition; CIP has 2nd ed.
What is the Preferred Source for Transcribing
the Edition Statement?
52. Exercise
Scenario: You have a book with pages numbered
1-23, 1-200, and A1-A34. Find the information
about irregular paging in the RDA Toolkit.
What does the RDA guideline say? Is there an
associated LC PCC PS?
53. Exercise
Scenario: You are cataloging a book that is a
compilation of 3 novellas (all by the same
author), and you need to know how to record
the title.
What does the RDA guideline say? Is there an
associated LC PCC PS?
54. RDA Record Creation
Photo credit: https://www.flickr.com/photos/montagecomms/2692226959/
63. Elements vs. Areas of Description
• AACR2 - Publication area:
260 _ _ $a Chicago : $b American Library
Association, $c c2005.
• RDA - Publication elements
– Place of publication: Chicago
– Publisher: American Library Association
– Copyright date: 2005
– Publication date: [2005]
65. Bibliographic
Record
Records can be exchanged,
but there is no way to
exchange the individual
pieces of information
within a record.
Bibliographic
Record
Bibliographic
Record
66. When RDA (and a method of encoding
that recognizes its elements) is used, a
bibliographic record is made up of many
pieces of data.
Person
Is author of
Title
Bibliographic Record
And the
relationships
between
these pieces
of data are
defined.
67. Person
Is author of
Title
Bibliographic Record
The
boundaries
of the
record can
be
dissolved…
68. Person
Is author of
Title
Bibliographic Record
…and the
data can
interact
with other
information
on the
Web…
69. Person
Is author of
Title
Bibliographic Record
…and make
use of other
data on the
web.
70.
71. What is an RDA Record?
http://www.slideshare.net/GordonDunsire/what-rda-
record?
73. “The Bibliographic Framework Initiative (BIBFRAME) is an
undertaking by the Library of Congress and the
community to better accommodate future needs of the
library community. A major focus of the initiative will be
to determine a transition path for the MARC 21 exchange
format to more Web based, Linked Data standards.
Zepheira and The Library of Congress are working
together to develop a Linked Data model, vocabulary and
enabling tools / services for supporting this Initiative.”
- http://bibframe.org
74. “The Bibliographic Framework Initiative (BIBFRAME) is an
undertaking by the Library of Congress and the
community to better accommodate future needs of the
library community. A major focus of the initiative will be
to determine a transition path for the MARC 21 exchange
format to more Web based, Linked Data standards.
Zepheira and The Library of Congress are working
together to develop a Linked Data model, vocabulary and
enabling tools / services for supporting this Initiative.”
- http://bibframe.org
92. “RDA is an important source of elements in the
vocabulary for BIBFRAME, even though it
generally aims to be independent of any
particular set of cataloging rules.”
http://www.loc.gov/bibframe/faqs/
94. Chicken or Egg?
Photo Credit: http://www.flickr.com/photos/24098698@N05/5556334141
“The change in rules
for metadata creation,
represented by RDA,
will also help library
metadata to be more
useful, though
perhaps to a lesser
extent than
BIBFRAME.”
Jason W. Dean
http://www.inthelibrarywiththeleadpipe.org/2013/charl
es-a-cutter-and-edward-tufte-coming-to-a-library-near-you-
via-bibframe/