“RDA Essentials”
Judith A. Kuhagen
Policy and Standards Division, Library of Congress
Connecticut Library Association, Technical Services Section
Farmington, CT -- November 4, 2010
Four topics today
1. US RDA Test
2. Critical differences between AACR2 and RDA
3. Changes to MARC 21
4. How to prepare:
– Yourself
– Your colleagues
– Your library
Conn. LA - Kuhagen - Nov. 4, 2010
2
US RDA Test
• Three national libraries
• 23 other libraries, etc., as formal Test
participants
• 12 informal participants
Conn. LA - Kuhagen - Nov. 4, 2010
3
Test participants
• Test partners represent all types and sizes of
libraries (national, government, academic,
public, school, special); archives; museums;
book vendors; systems developers; library
schools; and consortia and funnels
• List of formal Test participants available at:
http://www.loc.gov/bibliographicfuture/rda/test-partners.html
Conn. LA - Kuhagen - Nov. 4, 2010
4
Formal participants: differences
•
•
•
•
Current descriptive standards
Current encoding schema
Current cataloging systems/OPACs
Types of resources cataloged
• Specifics in Excel document on public site for
the Test:
http://www.loc.gov/bibliographic-future/rda/
Conn. LA - Kuhagen - Nov. 4, 2010
5
Goal of the US RDA Test
• “... to assure the operational, technical,
and economic feasibility of RDA”
• In response to concerns expressed by
the Library of Congress Working
Group on the Future of Bibliographic
Control (a non-LC group appointed to
advise LC)
Conn. LA - Kuhagen - Nov. 4, 2010
6
3 phases of the Test
• Through Sept. 30, 2010: training and
creation of practice records
• Oct. 1-Dec. 31, 2010: creation of Test
records
• Jan. 1-Mar. 31, 2011: evaluation and
analysis by the coordinating committee
• Then: decision by national libraries on
implementation
Conn. LA - Kuhagen - Nov. 4, 2010
7
Test records: 3 categories
• Common Original Set - 25 resources **
• Common Copy Set - 5 records **
• Extra Set - a library’s usual cataloging output
(at least 25 bibliographic records from each
Test partner with authority work if done)
** PDFs, etc., and instructions available as
administrative document #6 at:
http://www.loc.gov/catdir/cpso/RDAtest/rdatest
.html
Conn. LA - Kuhagen - Nov. 4, 2010
8
Surveys as part of Test
• Cataloging experience of record creator
• Ease of understanding RDA and use of the
Toolkit: positive and negative
• Levels of documentation and training
• Time to create bibliographic and authority
records
• Reactions by others in participants’ libraries,
etc., to their RDA records
Conn. LA - Kuhagen - Nov. 4, 2010
9
Comments from non-participants
• May send opinions and suggestions about
RDA, the RDA Toolkit, RDA records, etc., to
the coordinating committee via a survey
• Online questionnaire available at URL
http://www.surveymonkey.com/s/Q5968DB
Conn. LA - Kuhagen - Nov. 4, 2010
10
Test records
• OCLC Participants
– Common sets: institution records for master
records in WorldCat
– Extra set: as usual in WorldCat
• Other participants -- directly to LC
• NACO authority records
• Records from all participants on LC web
site for anyone to view/use [URL to be
announced mid-November on Autocat, etc.]
Conn. LA - Kuhagen - Nov. 4, 2010
11
Identifying RDA MARC records
• Bibliographic records:
– Leader/18: value “i” (ISBD)
– 040 $a ___ $c ___ $e rda
• Authority records:
– 008/10: value “z” (Other)
– 040 $a ___ $b eng $c ___ $e rda
Conn. LA - Kuhagen - Nov. 4, 2010
12
OCLC policies on RDA in
WorldCat
• General policy statement at:
http://www.oclc.org/us/en/rda/policy.htm
• “Adding RDA elements/fields to existing
OCLC non-RDA records” - administrative
document #7 at:
http://www.loc.gov/catdir/cpso/RDAtest/rda
test.html
Conn. LA - Kuhagen - Nov. 4, 2010
13
NACO policies during the Test
• No duplicate RDA authority records
• Not changing 1XX in AACR2 authority
records to RDA form
• No modification of headings in non-RDA
bibliographic records until there is a
decision on implementation of RDA
• Policies/procedures in administrative
document #1 at:
http://www.loc.gov/catdir/cpso/RDAtest/rdat
est.html
Conn. LA - Kuhagen - Nov. 4, 2010
14
Adding RDA to AACR2
authority records
• Giving RDA form (same or different) in
7XX field with second indicator of “4”
130 #0 $a Bible. $p O.T. $p Genesis
730 04 $a Bible. $p Genesis
• Specific elements may be included in
new fields (e.g., 046, 370)
Conn. LA - Kuhagen - Nov. 4, 2010
15
Questions about
the US RDA Test?
Conn. LA - Kuhagen - Nov. 4, 2010
16
Critical differences between
AACR2 and RDA
Conn. LA - Kuhagen - Nov. 4, 2010
17
Differences from AACR2
• General
– In perspective and foundation
– In structure
– In terminology
• Specific changes in instructions
Conn. LA - Kuhagen - Nov. 4, 2010
18
RDA based on IFLA’s international
models and principles
• Functional Requirements for
Bibliographic Records (FRBR; 1998)
• Functional Requirements for Authority
Data (FRAD; 2009)
• Statement of International Cataloguing
Principles (ICP; 2009)
Conn. LA - Kuhagen - Nov. 4, 2010
19
Addresses user tasks
FRBR:
• Find
• Identify
• Select
• Obtain
FRAD:
• Find
• Identify
• Contextualize
• Justify
• ICP’s highest principle = “convenience of
the user”
Conn. LA - Kuhagen - Nov. 4, 2010
20
Is a content standard
• Not a display standard (as is AACR2)
– Does have appendix D for ISBD and appendix
E for AACR2 style for access points
• Not an encoding standard
– Use whatever schema you prefer (MARC 21,
Dublin Core, etc.)
Conn. LA - Kuhagen - Nov. 4, 2010
21
Mappings, etc., for transition
• RDA Appendix D mappings:
– ISBD to RDA
– MARC 21 bibliographic format to RDA
• RDA Appendix E:
– Presentation and punctuation of access points
– MARC 21 authority format mapping to RDA
• Other mappings in the RDA Toolkit
Conn. LA - Kuhagen - Nov. 4, 2010
22
More international
• Focus on local user needs
• Choice of agency preparing the
description:
– Language of additions to access points
– Language of supplied data
– Script and transliteration
– Calendar
– Numeric system
Conn. LA - Kuhagen - Nov. 4, 2010
23
For wider scope
of resources
• Response to what’s being acquired in libraries
– More elements for non-printed text resources
– More elements for non-text resources
– More elements for unpublished resources
• Compatible with specialist manuals (DACS,
CCO, DCRM(B) etc.)
Conn. LA - Kuhagen - Nov. 4, 2010
24
Includes authority data
instructions
• Based on attributes and relationships in
FRAD
• Authorized/variant access points and
elements will for now continue to be
documented in authority records
Conn. LA - Kuhagen - Nov. 4, 2010
25
Has controlled vocabularies
• Only a few closed: content, media, and
carrier types; mode of issuance; etc.
• Most are open: cataloger can supply term
if needed term not in list
• Vocabularies being registered on the Web
(http://metadataregistry.org/rdabrowse.htm)
-- goal of multiple languages and/or scripts
Conn. LA - Kuhagen - Nov. 4, 2010
26
Importance of relationships
• Categories:
– Persons/families/corporate bodies to
resources
– Resources to other resources
– Person/families/corporate bodies to other
persons/families/corporate bodies
• Relationship designators in appendices
I, J, and K (not core elements in RDA)
Conn. LA - Kuhagen - Nov. 4, 2010
27
RDA: responding to changes
• Changes in technology
– Impact on descriptive/access data
•
•
•
•
book catalogs
card catalogs
OPACs
next generation
• Move from classes of materials to elements
and values (more controlled vocabularies)
• Move from individual library to international
audience
Conn. LA - Kuhagen - Nov. 4, 2010
28
Internet
• Catalogs are no longer in isolation
– Global access to data
• Virtual International Authority File
(www.viaf.org)
• Integrate bibliographic data with wider
Internet environment
– Share data beyond institutions
Conn. LA - Kuhagen - Nov. 4, 2010
29
RDA Structure
• General introduction
• Identifying elements (entities and their
attributes)
– Ch. 1-7: work, expression, manifestation, item
– Ch. 8-16: person, family, corporate body, place
• Relationships: ch. 17-22, 24-32
• Appendices
• Glossary
Conn. LA - Kuhagen - Nov. 4, 2010
30
RDA structure
• Not by class of materials: no separate
chapters for books, printed music, etc.
– Overarching principles applicable to all
• Basic goals: identify and relate (from
FRBR/FRAD user tasks and ICP)
• Chapters: separate elements for goals
– Assemble those elements when need
authorized access points (instructions at end
of chapters 6, 9-11)
Conn. LA - Kuhagen - Nov. 4, 2010
31
Toolkit not to be read linearly
• Using the online RDA Toolkit:
– “Jumping in” via keyword searches
– Going directly to elements from Table of
Contents (ToC) pane
– Following links
– Seeing some duplication of content (needed for
context)
• ALA will publish a printed text version of
RDA and the RDA element set
Conn. LA - Kuhagen - Nov. 4, 2010
32
Terminology
• FRBR and FRAD “attributes” are
“elements” in RDA
• FRBR and FRAD Group 1 entities:
– Work
– Expression
– Manifestation
– Item
Conn. LA - Kuhagen - Nov. 4, 2010
33
AACR2 to RDA vocabulary
• heading
• author, composer,
etc.
• main entry
• uniform title
Conn. LA - Kuhagen - Nov. 4, 2010
authorized access point
creator
preferred title + authorized
access point for creator if
appropriate
(1) preferred title (+ other
information to differentiate);
(2) conventional collective
title
34
AACR2 to RDA vocabulary
• see reference
variant access point
• see also reference
authorized access point
for related entity
• physical description
carrier description
Conn. LA - Kuhagen - Nov. 4, 2010
35
AACR2 to RDA vocabulary
• GMD
media type +
carrier type +
content type
• chief source
preferred sources
Conn. LA - Kuhagen - Nov. 4, 2010
36
Core elements
• Based on attributes mandatory for a national
level record in FRBR and FRAD
• Core elements (RDA 0.6):
– Agency can add others
• LC’s core elements for the US RDA Test -see document at
http://www.loc.gov/catdir/cpso/RDAtest/rdatr
aining2.html
Conn. LA - Kuhagen - Nov. 4, 2010
37
“Core-ness” identified at element
level in RDA
• If always a core element (if applicable
and available), label “CORE ELEMENT”
appears below element name
• If use as a core element depends upon
the situation, the label “CORE ELEMENT”
is followed by an explanation of the
situation
Conn. LA - Kuhagen - Nov. 4, 2010
38
Other choices in RDA
• Alternatives and options
• “or” instructions
• “agency preparing …” instructions
• LC’s decisions in Library of Congress
Policy Statements (LCPSs) available in the
RDA Toolkit and as pdfs at
http://www.loc.gov/catdir/cpso/RDAtest/rda
_lcps.html
Conn. LA - Kuhagen - Nov. 4, 2010
39
Areas of specific changes
in RDA
1. Description
2. Identifying the work/expression
3. Identifying a person, family, corporate
body
Conn. LA - Kuhagen - Nov. 4, 2010
40
Sources of information
• Preferred source (not “chief source”)
• Fewer categories for sources (RDA 2.2):
#1: Pages, leaves, etc., or images of
pages …
#2: Moving images
#3: All other resources
• Able to take many elements from anywhere
in the resource and from any other source
Conn. LA - Kuhagen - Nov. 4, 2010
41
Examples: expanded sources
• Parallel title
– AACR2: same source as title proper
– RDA: no restriction on location
• Statement of responsibility
– AACR2: restricted number of sources in the
resource
– RDA: no restriction on location
Conn. LA - Kuhagen - Nov. 4, 2010
42
ICP representation principle
• Transcribed information = “Take what you see”
and “accept what you get”
• General guideline at RDA 1.7.1 addresses
transcription of what is on the resource:
– Capitalization: follow appendix A or accept found
form
– Punctuation, abbreviations, inaccuracies, symbols,
initials, numbering: generally follow what is on
source
Conn. LA - Kuhagen - Nov. 4, 2010
43
Capitalization choices
Accepting found capitalization:
245 10 $a Cairo : $b THE CITY VICTORIOUS /
$c Max Rodenbeck.
250 ## $a FIRST VINTAGE DEPARTURES EDITION.
Changing found capitalization:
245 10 $a Cairo : $b the city victorious /
$c Max Rodenbeck.
250 ## $a First Vintage Departures edition.
Conn. LA - Kuhagen - Nov. 4, 2010
44
Correcting found errors?
• Principle of representation (RDA 2.3.1.4):
– Don’t correct errors in titles proper of
monographs = no more “[sic]” or “[i.e., ___ ]” –
give note (246 field in MARC) to explain
– Do correct errors in titles proper of serials and
integrating resources to have a stable title
– Don’t correct errors in other transcribed
elements; give note if considered important
Conn. LA - Kuhagen - Nov. 4, 2010
45
Errors on resource
Monograph:
245 $a Teusday’s tasks
246 $i Corrected title: $a Tuesday’s tasks
Serial:
245 $a Zoology studies
246 $i Misspelled title on number 1:
$a Zooology studies
260 $a Boston : $b RH Pulblishers
Conn. LA - Kuhagen - Nov. 4, 2010
46
Statement of responsibility …
title proper
• Single statement naming more than one
person, family, or corporate body
– Transcribe as found (no longer the AACR2
“rule of 3”)
– Option: transcribe first name and give
bracketed summary about information not
transcribed – cataloger’s judgment
• Don’t need to transcribe to justify additional
access points and vice versa
Conn. LA - Kuhagen - Nov. 4, 2010
47
Statement of responsibility
example
245 $a … / $c by J. Douglas, A. Dean, C.
Terry, M. Paul, L. Michaels, M. Lawrence,
and J. James.
Or, if option applied:
245
$a … / $c by J. Douglas [and six others]
(no longer “[et al.]”)
Conn. LA - Kuhagen - Nov. 4, 2010
48
Numbering of serials
• General guidelines (RDA 2.6.1):
– Transcribe terms and months as on the resource
– Can adjust form of numerals or record as on the
resource
• Substitute numerals for numbers expressed as
words (RDA 1.8.3)
362 0# $a Volume X, number 1362 0# $a January 2010Conn. LA - Kuhagen - Nov. 4, 2010
49
Place of publication (RDA 2.8.2)
• If more than one, only the first recorded is
required – no “home country” provision
• LC recommendation: Supply a probable place
whenever possible for benefit of users and
catalogers
• If no probable place, give “[Place of
publication not identified]” – not “[S.l.]”
Conn. LA - Kuhagen - Nov. 4, 2010
50
Place of publication: “do not ...”
• Do not supply higher jurisdiction for found
local place
• Do not correct fictitious or incorrect
information; make a note to explain
Conn. LA - Kuhagen - Nov. 4, 2010
51
Examples: place of publication
260 $a London
On resource: London -- New York -- Boston
260
260
$a Red Oak [Iowa]
$a [Place of publication not identified]
260
500
$a Minneapolis
$a Actually published in St. Paul
Conn. LA - Kuhagen - Nov. 4, 2010
52
Publisher’s name (RDA 2.8.4)
• If more than one, only the first recorded is
required
• Do not shorten the form of name but can
omit corporate hierarchy
• If no publisher identified, give “[publisher
not identified]” – not “[s.n.]”
Conn. LA - Kuhagen - Nov. 4, 2010
53
Examples: publisher’s name
260 $b J.J. Wilson Publishing Company
not: 260 $b Wilson Pub. Co.
260
$a Toronto : $b Pilkington Pub. Co.
on source: Toronto -- Pilkington Pub. Co.
Houston -- Davidson Publishers
260 $b Humanities Association, Renaissance
Literature Section
on source: Humanities Association, Literature Division,
Renaissance Literature Section
260
$b [publisher not identified]
Conn. LA - Kuhagen - Nov. 4, 2010
54
Date of publication
• If no publication date on resource, supply
a probable date whenever possible for
benefit of users and catalogers
• If no probable date (very rare) for singlepart monographs, give “[date of
publication not identified]”
Conn. LA - Kuhagen - Nov. 4, 2010
55
Date of publication
• For other resources, If the first and/or
last issue, part, or iteration is not
available:
– Supply an approximate date or dates of
publication
– If date or dates cannot be approximated,
don’t record date(s) of publication – omit the
element; do not give “[date of publication
not identified]”
Conn. LA - Kuhagen - Nov. 4, 2010
56
Copyright date (RDA 2.11)
• Separate element from date of publication
– Core element if no date of publication or of
distribution
• Precede by copyright symbol (©) or
phonogram symbol ()
• In MARC 260 $c preceded by publication
date and comma
Conn. LA - Kuhagen - Nov. 4, 2010
57
Examples: copyright date
260
$a Chicago : $b ELC Publishers, $c
[date of publication not identified],
2010.
On disc label: ELC Publishers, Chicago, 2010
260
$a [Denver?] : $b Colorado Department of
Education, $c 2009, ©2009.
On source: Published 2009 by Colorado
Department of Education, Copyright 2009
Conn. LA - Kuhagen - Nov. 4, 2010
58
Replacement for GMD
• Developed with ONIX publishing community:
– Content type -- RDA 6.9 -- MARC 336 field
– Media type -- RDA 3.2 -- MARC 337 field
– Carrier type -- RDA 3.3 -- MARC 338 field
• Libraries may use as search limits, display
as icons, etc., rather than as terms in fields
Conn. LA - Kuhagen - Nov. 4, 2010
59
Controlled vocabularies for
content, media, carrier types
• Closed lists in RDA 6.9.1.3, 3.2.1.3, 3.3.1.3
• If more than one term appropriate, two choices:
– Give all: repeat subfield $a or repeat field
– Pick term representing the predominant or most
substantial content, media, carrier
• If no term appropriate, give “other”
Conn. LA - Kuhagen - Nov. 4, 2010
60
MARC for content, media, carrier
• In each field (336-338):
– $a: term
– $b: code [give $a and/or $b]
– $2: “rdacontent” or “rdamedia” or “rdacarrier”
as appropriate
– $3: materials specified - give if appropriate
Conn. LA - Kuhagen - Nov. 4, 2010
61
Content type (RDA 6.9)
• Scope = “fundamental form of
communication in which the content is
expressed and the human sense through
which it is intended to be perceived”
– “cartographic image,” “performed music,” “still
image,” “text,” etc.
• For images, also whether in two or three
dimensions and presence or absence of
movement (e.g., “two-dimensional moving
image”)
Conn. LA - Kuhagen - Nov. 4, 2010
62
Media type (RDA 3.2)
• Scope = “a categorization reflecting the
general type of intermediation device
required to view, play, run, etc., the
content of a resource”
– “audio,” “projected,” “microform,” “video,” etc.
• Broad categories; specific types in
Carrier type (RDA 3.3)
Conn. LA - Kuhagen - Nov. 4, 2010
63
Carrier type (RDA 3.3)
• Scope = “a categorization reflecting the
format of the storage medium and housing
of a carrier in combination with the type of
intermediation device required to view, play,
run, etc., the content of a resource”
– “audio disc,” “computer disc,” “microfiche,”
“slide,” “volume,” etc.
• Don’t confuse with term used in Extent
(MARC 300 $a): some terms in common
Conn. LA - Kuhagen - Nov. 4, 2010
64
One 336-338 example for now
Book:
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
[Other examples after slides on Extent]
Conn. LA - Kuhagen - Nov. 4, 2010
65
Some changes in recording
extent
• No abbreviations for terms (e.g., “pages,”
“volumes”)
• Changes in vocabulary from AACR2, e.g.:
– “close score” and “miniature score” not in RDA;
use “condensed score” and “study score”
– “computer disc” for both “computer disk” and
“computer optical disc”
– “sheet,” not “broadside”
Conn. LA - Kuhagen - Nov. 4, 2010
66
MARC 300 $a, 336-338
Book:
300
336
337
338
$a
$a
$a
$a
Music CD:
300
336
337
338
123 pages, 28 unnumbered pages
text $2 rdacontent
unmediated $2 rdamedia
volume $2 rdacarrier
$a
$a
$a
$a
1 audio disc
{or: 1 CD}
performed music $2 rdacontent
audio $2 rdamedia
audio disc $2 rdacarrier
Conn. LA - Kuhagen - Nov. 4, 2010
67
MARC 300 $a, 336-338
Score:
300
336
337
338
$a
$a
$a
$a
1 vocal score (xii, 300 pages)
notated music $2 rdacontent
unmediated $2 rdamedia
volume $2 rdacarrier
Map:
300
336
337
338
$a
$a
$a
$a
1 map
cartographic image $2 rdacontent
unmediated $2 rdamedia
sheet $2 rdacarrier
Conn. LA - Kuhagen - Nov. 4, 2010
68
MARC 300 $a, 336-338
DVD:
300 $a 1 DVD
{or: 1 video disc}
336 $a two-dimensional moving image $2
rdacontent
337 $a video $2 rdamedia
338 $a video disc $2 rdacarrier
Online PDF:
300 $a
336 $a
337 $a
338 $a
1 online resource (39 pages)
text $2 rdacontent
computer $2 rdamedia
online resource $2 rdacarrier
Conn. LA - Kuhagen - Nov. 4, 2010
69
MARC 300 $a, 336-338
Website (with maps, text, and photographs):
300 $a 1 online resource
336 $a text $2 rdacontent
336 $a cartographic image $2 rdacontent
336 $a still image $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier
Or repeat subfield $a in 336 field:
336 $a text $a cartographic image
$a still image $2 rdacontent
Conn. LA - Kuhagen - Nov. 4, 2010
70
MARC 300 $a, 336-338
Book with accompanying CD of lecture
300 $a 244 pages ... + $e 1 CD
336 $3 book $a text $2 rdacontent
336 $3 CD $a spoken word $2 rdacontent
337 $3 book $a unmediated $2 rdamedia
337 $3 CD $a audio $2 rdamedia
338 $3 book $a volume $2 rdacarrier
338 $3 CD $ audio disc $2 rdacarrier
Can also give note or can repeat 300 field
300 $a 244 pages ...
300 $a 1 CD ...
Conn. LA - Kuhagen - Nov. 4, 2010
71
No abbreviations in 300 $b
• Most elements in this MARC subfield are
attributes of the expression (RDA chapter 7):
–
–
–
–
–
–
–
illustrations
portraits
photographs
sound
silent
color
black and white
Conn. LA - Kuhagen - Nov. 4, 2010
72
Questions on
changes in description?
Conn. LA - Kuhagen - Nov. 4, 2010
73
Identifying works and expressions
• Also called “naming the work” and “naming the
expression”
• Same as AACR2 “main entry” if the
manifestation contains that work/expression:
Bibl. records:
 100/110/111 + 240
 100/110/111 + 245
 130
 245
Conn. LA - Kuhagen - Nov. 4, 2010
Auth. records:
 100/110/111 $a $t
 100/110/111 $a $t
 130
 130
74
Determining preferred title
• Form to be used when determining the
authorized access point
• Based on title proper of first manifestation
received
• If later manifestations have different forms,
determine the most common form of the
preferred title
Conn. LA - Kuhagen - Nov. 4, 2010
75
Simultaneous publication:
different titles in same language
• Choose the preferred title based on
title of the resource first received (not
the resource published in the home
country)
U.K. volume received first: Walking in Britain
U.S. volume received later: Day walks in Britain
Preferred title = Walking in Britain
Conn. LA - Kuhagen - Nov. 4, 2010
76
Simultaneous publication:
different titles/languages
• No longer a priority order of languages
– use title in resource first received
Serial published simultaneously in German and
English versions
German-language version received first
English-language version received later
Preferred title = title from German-language version
Conn. LA - Kuhagen - Nov. 4, 2010
77
Preferred titles: parts of the
Bible (RDA 6.23.2.9)
• Refer to the Old and New Testaments by
their spelled-out forms (not “O.T.” and
“N.T.”)
• Omit the name of the testament in the
preferred title for individual books or
groups of books
Conn. LA - Kuhagen - Nov. 4, 2010
78
Bible examples
130 $a Bible. $p New Testament
not 130 $a Bible. $p N.T.
130 $a Bible. $p Genesis
not 130 $a Bible. $p O.T. $p Genesis
130 $a Bible. $p Gospels
not 130 $a Bible. $p N.T. $p Gospels
Conn. LA - Kuhagen - Nov. 4, 2010
79
Responsible entity related to
work?
• RDA 0.6.3 and RDA 6.27.1: when creating
the authorized access point for the work,
precede the preferred title for the work,
if appropriate,
by the authorized access point
representing the person, family, or
corporate body responsible for the work
Conn. LA - Kuhagen - Nov. 4, 2010
80
Creator (RDA 19.2)
• Creator = “person, family, or corporate body
responsible for the creation of a work”
• If more than one, only the creator having
principal responsibility named first in resource
is required
• If more than one and principal responsibility
not indicated, only the first-named creator is
required
Conn. LA - Kuhagen - Nov. 4, 2010
81
Example: creators with
principal responsibility
100
245
*700
*700
*700
$a Sweet, Martha.
$a … / $c by Martha Sweet and Linda
Bruce with contributions by Gus
Peterson and Marilee James.
$a Bruce, Linda.
$a Peterson, Gus.
$a James, Marilee.
* number of access points for other creators:
cataloger judgment
Conn. LA - Kuhagen - Nov. 4, 2010
82
Example: creators with no
principal responsibility indicated
100
245
*700
*700
*700
*700
$a Brown, Susan.
$a … / $c by Susan Brown, Melanie
Carlson, Stephen Lindell, Kevin Ott,
and Janet Wilson.
$a Carlson, Melanie.
$a Lindell, Stephen.
$a Ott, Kevin.
$a Wilson, Janet.
* number of access points for other creators:
cataloger judgment
Conn. LA - Kuhagen - Nov. 4, 2010
83
Compilation of works
• RDA: do not name the compilation by the first
work in the compilation as AACR2 does in
some situations, because doing so
misidentifies the compilation (work of works)
• Can give authorized access points for each
work/expression
• If no collective title, alternative to devise a title
proper (cataloger’s judgment)
Conn. LA - Kuhagen - Nov. 4, 2010
84
Preferred title for compilations of
one creator (RDA 6.2.2.10)
• Categories:
– Complete works = use “Works”
– Complete works in a single form = use term
chosen by cataloger
– Other compilations of two or more works in
same form or different forms = give preferred
title for each work
– Not “Selections” by itself (change from AACR2)
Conn. LA - Kuhagen - Nov. 4, 2010
85
Alternative: Other compilations
• Instead of or in addition to giving the
preferred title for each work, use a
conventional collective title, e.g.,:
– Works. Selections
– Posters. Selections
– Orchestra music. Selections
• For music conventional collective titles, see
RDA 6.14.2.8; for law, see RDA 6.19.2.5
Conn. LA - Kuhagen - Nov. 4, 2010
86
Compilation of two works by
same creator
AACR2:
100
240
245
505
1#
10
10
0#
$a Miller, Arthur, $d 1915-2005
$a Archbishop’s ceiling
$a Two plays / $c Arthur Miller.
$a The Archbishop’s ceiling -- The
American clock.
700 12 $a Miller, Arthur, $d 1915-2005.
$t American clock.
Conn. LA - Kuhagen - Nov. 4, 2010
87
Compilation: two works, same
creator
RDA with alternative for conventional collective title:
100
240
245
505
1#
10
10
0#
$a Miller, Arthur, $d 1915-2005
$a Plays. $k Selections
$a Two plays / $c Arthur Miller.
$a The Archbishop’s ceiling -- The
American clock.
700 12 $a Miller, Arthur, $d 1915-2005.
$t Archbishop’s ceiling.
*700 12 $a Miller, Arthur, $d 1915-2005.
$t American clock.
* This access point is not a core requirement if
a 240 field is in the record.
Conn. LA - Kuhagen - Nov. 4, 2010
88
Work/expression manifested
(RDA 17.8; RDA 17.10)
• In MARC context, if cataloging a single work or
expression, the element is same as naming
the work or expression (AACR2 “main entry”)
• If a compilation, core requirement to give
predominant or first-named work/expression:
– As identifier, authorized access point, or composite
description (RDA 17.4.2)
– LC policy for the US RDA Test modifies the core
requirement for some types of compilations
Conn. LA - Kuhagen - Nov. 4, 2010
89
Compilation of works by
different creators
AACR2:
100 1# $a Polk, Sharon.
240 10 $a Community band concerts
245 10 $a Community band concerts / $c Sharon
Polk. Fall harvest festivals / Terri
Swanson.
700 12 $a Swanson, Terri. $t Fall harvest
festivals.
Conn. LA - Kuhagen - Nov. 4, 2010
90
Compilation of works by
different creators
RDA without alternative for devised title:
245 00 $a Community band concerts / $c Sharon
Polk. Fall harvest festivals / Terri
Swanson.
700 12 $a Polk, Sharon. $t Community band
concerts.
*700 12 $a Swanson, Terri. $t Fall harvest
festivals.
* This access point is not a core requirement.
Conn. LA - Kuhagen - Nov. 4, 2010
91
Compilation: different
expressions of the same work
AACR2: original + Spanish translation in same resource:
041 1# $a eng $a spa $h eng
100 1# $a Macken, JoAnn Early, $d 1953240 10 $a Mail carrier. $l Spanish &
English
245 10 $a Mail carrier = $b El cartero /
$c JoAnn Early Macken.
246 31 $a Cartero
546 ## $a English and Spanish.
Conn. LA - Kuhagen - Nov. 4, 2010
92
Compilation: different
expressions of the same work
RDA:
041 1# $a eng $a spa $h eng
100 1# $a Macken, JoAnn Early, $d 1953245 10 $a Mail carrier = $b El cartero /
$c JoAnn Early Macken.
246 31 $a Cartero
546 ## $a English and Spanish.
700 12 $a Macken, JoAnn Early, $d 1953$t Mail carrier. $l English.
*700 12 $a Macken, JoAnn Early, $d 1953$t Mail carrier. $l Spanish.
* This access point is not a core requirement.
Conn. LA - Kuhagen - Nov. 4, 2010
93
Other changes about creator
• Treaties: generally first signatory, not first in
English alphabetic order
• Librettos: no longer considered to be
musical works named by composer + title
• Performer: can be creator if performance
involved substantial creative responsibility
for creating a new work
Conn. LA - Kuhagen - Nov. 4, 2010
94
Questions on
changes in identifying the
work or expression?
Conn. LA - Kuhagen - Nov. 4, 2010
95
Name of person, family, or
corporate body
• Preferred name: form to be used when
creating the authorized access point
• Variant name(s): form to be used when
creating variant access point(s) (not
core in RDA)
Conn. LA - Kuhagen - Nov. 4, 2010
96
Identifying a person
• Definition (RDA 8.1.2) = “An individual or an
identity established by an individual (either alone
or in collaboration with one or more other
individuals)”
• RDA 9.0: Includes fictitious entities (change from
AACR2)
– Miss Piggy, Snoopy, etc. now in scope if presented as
having responsibility in some way for a work,
expression, manifestation, or item -- not just as subjects
Conn. LA - Kuhagen - Nov. 4, 2010
97
LCPS for RDA 9.0 scope
• LCPS expands scope also to real nonhuman entities having roles as creators
or contributors
• Not changing LCSH during the Test:
– Create NAR for person & notify LC
– List of subject headings for possible deletion
if LC implements RDA
Conn. LA - Kuhagen - Nov. 4, 2010
98
Examples of expanded scope
in RDA and in LCPS
100 0# $a
245 10 $a
by
700 1# $a
Miss Piggy.
Miss Piggy’s guide to life / $c
Miss Piggy as told to Henry Beard.
Beard, Henry.
100 0# $a Lassie.
245 1# $a Stories of Hollywood / $c told
by Lassie.
Conn. LA - Kuhagen - Nov. 4, 2010
99
Preferred name (RDA 9.2.2)
• Choose the form most commonly known
• Variant spellings: choose the form found on
the first resource received (RDA 9.2.2.5.4)
• If individual has more than one identity, a
preferred name for each identity (RDA 9.2.2.8)
– No time period restrictions -- change from
AACR2
Conn. LA - Kuhagen - Nov. 4, 2010
100
Surnames: words, etc.,
indicating relationships
• Include words, etc., (e.g., Jr., Sr., IV) in
preferred name – not just to break
conflict
100
670
$a Rogers, Roy, $c Jr., $d 1946$a Growing up with Roy and Dale, 1986:
$b t.p.(Roy Rogers, Jr.) p. 16 (born
1946)
Conn. LA - Kuhagen - Nov. 4, 2010
101
Date associated with the person
• Three dates:
– Date of birth (RDA 9.3.2) – LC: if available
– Date of death (RDA 9.3.3) – LC: if available
– Period of activity of the person – LC: if needed
to differentiate and dates of birth/death not
known
• no restrictions on time period (RDA 9.3.4) -- change
from AACR2
Conn. LA - Kuhagen - Nov. 4, 2010
102
Changes: dates for persons
• Abbreviations “cent.,” “ca.,” “b.,” “d.,” and
“fl.” not in appendix B:
– “cent.” becomes “century”
– “approximately” replaces “ca.”
– “b.” and “d.” dates -- LC : use hyphens
instead of spelling out the abbreviations
– “fl.” -- LC: use “active”
Conn. LA - Kuhagen - Nov. 4, 2010
103
Fuller form of name (RDA 9.5)
• Scope:
– Full form of a part of a name represented only
by an initial or abbreviation in the form chosen
as the preferred name, or
– A part of the name not included in the form
chosen as the preferred name (change from
AACR2)
Conn. LA - Kuhagen - Nov. 4, 2010
104
Examples: fuller form of name
100 1# $a Smith, Nancy E. $q (Nancy Elizabeth)
100 1# $a Williams, John $q (John Dudley)
100 1# $a King, $c Mrs. $q (Annie Liddon)
Conn. LA - Kuhagen - Nov. 4, 2010
105
Terms of address not as
additions
• But may be needed as part of the preferred
name:
– When the name consists only of the surname
(RDA 9.2.2.9.3: Seuss, Dr.)
– For a married person identified only by a
partner’s name and a term of address (RDA
9.2.2.9.4: Davis, Maxwell, Mrs.)
– If part of a phrase consisting of a forename(s)
preceded by a term of address (RDA 9.2.2.23:
Sam, Cousin)
Conn. LA - Kuhagen - Nov. 4, 2010
106
Other additions not allowed
• Some AACR2 additions to access points for
persons not allowed:
– not titles of position or office
– not initials of academic degrees
– not initials denoting membership in an
organization
• Can include this identifying information in
MARC 670 field in authority record
Conn. LA - Kuhagen - Nov. 4, 2010
107
Questions on
identifying a person?
Conn. LA - Kuhagen - Nov. 4, 2010
108
Identifying a family (ch. 10)
• Definition (RDA 8.1.2) = “two or more
persons related by birth, marriage,
adoption, civil union, or similar legal status,
or who otherwise present themselves as a
family”
• Families not in AACR2
Conn. LA - Kuhagen - Nov. 4, 2010
109
Scope of “family”
• Now considered creators, contributors, etc.
– Important for archives, museums, and special
collections -- may supplement RDA with
specialist manuals (e.g., Describing archives :
a content standard (DACS))
– Also possible for general library materials:
genealogy newsletters, family reunion
publications, etc.
Conn. LA - Kuhagen - Nov. 4, 2010
110
NARs vs. subject headings
• Ch. 10 applies to distinctive family entities
• Continue the current subject cataloging
policy for general family groupings (one
spelling with others as variants)
• Separate authority records will exist in the
LC/NACO Authority File and LCSH
Conn. LA - Kuhagen - Nov. 4, 2010
111
Family elements other than
preferred name
•
•
•
•
•
•
•
Type of family *
Date associated with the family *
Place associated with the family *
Prominent member of the family *
Hereditary title
Family history
* = in access points
Identifier
Conn. LA - Kuhagen - Nov. 4, 2010
112
Examples for family
100 3# $a Pahlavi (Dynasty : $d 1925-1979)
100 3# $a Nayak (Dynasty : $d 1529–1739
: $c Madurai, India)
100 3# $a Medici (Royal house : $g
Medici, Lorenzo de’, 1449-1492)
Conn. LA - Kuhagen - Nov. 4, 2010
113
Questions on
identifying a family?
Conn. LA - Kuhagen - Nov. 4, 2010
114
Identifying a corporate body
• Definition (RDA 8.1.2) = “an organization
or group of persons and/or organizations
that is identified by a particular name and
that acts, or may act, as a unit”
• Includes ad hoc events (such as athletic
contests, exhibitions, expeditions, fairs,
and festivals) and vessels (e.g., ships and
spacecraft)
Conn. LA - Kuhagen - Nov. 4, 2010
115
Preferred name for the corporate
body (RDA 11.2.2)
• Choose the form most commonly known
• Variant spellings: choose the form found in
the first resource received (RDA 11.2.2.5.1)
– LC will keep its policy to change to the later
spelling in cases of orthographic reform
• Not abbreviating “Department” (should not
have abbreviated in AACR2 headings)
Conn. LA - Kuhagen - Nov. 4, 2010
116
Number or year in preferred name of
a conference, etc. (RDA 11.2.2.11)
• A merged instruction for preferred name -changes from AACR2:
– Retain frequency in the name of a conference,
congress, or meeting
– Omit year of convocation from the name of an
exhibition, fair, or festival
• Include year as addition in authorized access
point if resource not cataloged as a serial
Conn. LA - Kuhagen - Nov. 4, 2010
117
Location of conference, etc.
(RDA 11.3.2)
• In form as authorized access point (ch. 16)
• No “rule of three” when sessions held in three
or more locations (separated by semicolons
in access point -- RDA appendix E.2.2.4)
• If conference held online, location is “Online”
Conn. LA - Kuhagen - Nov. 4, 2010
118
Assemble elements: access
points
• 9.19: persons
• 10.10: families
• 11.13: corporate bodies
• See RDA appendix E for punctuation, etc.
(AACR2 style carried forward) (also LCPS 1.7)
• Cataloger’s judgment to give elements in
separate MARC fields when available
Conn. LA - Kuhagen - Nov. 4, 2010
119
Questions on
changes in identifying a
corporate body?
======
Questions on changes
from AACR2 to RDA?
Conn. LA - Kuhagen - Nov. 4, 2010
120
Changes in MARC 21
• Can encode RDA content in any schema
but many libraries will be using MARC 21
when testing or first implementing RDA
• RDA/MARC Working Group made
proposals for changes to MARC 21
Conn. LA - Kuhagen - Nov. 4, 2010
121
Current NACO authority record
practice now in RDA
• Status of identification (RDA 8.10)
– MARC 008/33
• Undifferentiated name indicator (RDA 8.11)
– MARC 008/32
• Source consulted (RDA 8.12)
– MARC 670
• Cataloger’s note (RDA 8.13)
– MARC 667
Conn. LA - Kuhagen - Nov. 4, 2010
122
New fields in authority format
• Separate fields for many of the elements
• RDA allows the “coreness” of some
elements to be satisfied by including it in
the authorized access point – NACO policy
for the Test
• Cataloger’s judgment to give element also
in its own MARC field in authority record
Conn. LA - Kuhagen - Nov. 4, 2010
123
New fields in authority format
for works and expressions
•
•
•
•
•
•
•
046:
370:
380:
381:
382:
383:
384:
Special coded dates
Associated place
Form of work
Other distinguishing characteristic
Medium of performance
Numeric designation of musical work
Key
Conn. LA - Kuhagen - Nov. 4, 2010
124
New fields in authority form
at for persons
•
•
•
•
•
•
•
•
046:
370:
371:
372:
373:
374:
375:
377:
Special coded dates
Associated place
Address
Field of activity
Affiliation
Occupation
Gender
Associated language
Conn. LA - Kuhagen - Nov. 4, 2010
125
New fields in authority format
for families
• 046: Special coded dates
• 370: Associated place
• 376: Family information
Conn. LA - Kuhagen - Nov. 4, 2010
126
New fields in authority format
for corporate bodies
•
•
•
•
046:
370:
371:
377:
Special coded dates
Associated place
Address
Associated language
Conn. LA - Kuhagen - Nov. 4, 2010
127
MARC 670 field ?
• If separate MARC field for an RDA element
and cataloger is adding that separate field,
cataloger’s judgment applies:
– in separate field, give source in subfield $v or
subfield $u if subfield present in separate field,
or
– give source and information in a 670 field
Conn. LA - Kuhagen - Nov. 4, 2010
128
New fields in bibliographic
format
•
•
•
•
•
033: Time, place, and date of event
336: Content type
337: Media type
338: Carrier type
380-384: [elements for Works/expressions]
• Some new values in 007 and 008
Conn. LA - Kuhagen - Nov. 4, 2010
129
Problems in encoding RDA
content in MARC
• Some elements lack separate fields (e.g.,
Language of expression in authority format)
• Too many RDA elements in same subfield, e.g.,
– 100 $c: Title of person, Other designation, Field of
activity, Profession
– 260 $a: Place of production, Place of publication,
Place of distribution
– 300 $b: Illustrative content, Color content, Layout,
Polarity, Sound content, Base material (and more)
Conn. LA - Kuhagen - Nov. 4, 2010
130
More information on new fields in
the MARC 21 authority format
• MARC 21 encoding document for LC’s practice
for the RDA Test
http://www.loc.gov/catdir/cpso/RDAtest/rdatraining2.
html
• Examples folder for authority records
http://www.loc.gov/catdir/cpso/RDAtest/rdaexamples
.html
• LC Network Development and MARC Standards
Office site:
http://www.loc.gov/marc/authority/ecadhome.html
Conn. LA - Kuhagen - Nov. 4, 2010
131
Questions on
changes in MARC 21?
Conn. LA - Kuhagen - Nov. 4, 2010
132
How to prepare yourself
1. Become familiar with FRBR and FRAD:
entities, terminology, user tasks
2. Review available training materials and
documentation
3. Explore RDA Toolkit if have access; if not,
review last full draft (caveat: some aspects
changed):
http://www.rdatoolkit.org/constituencyreview
Conn. LA - Kuhagen - Nov. 4, 2010
133
How to prepare yourself
4. View webcasts/webinars and attend briefings,
workshops, etc.
5. Read books and articles about RDA
6. Talk with cataloging colleagues in your and
other libraries
Conn. LA - Kuhagen - Nov. 4, 2010
134
How to prepare yourself
8. Take or audit a cataloging course
9. Create RDA practice records
10. Create more RDA practice records
Conn. LA - Kuhagen - Nov. 4, 2010
135
How to prepare your
colleagues
• Staff in all parts of your library
• Tell them what you’ve learned about
FRBR, FRAD, RDA, MARC
– In appropriate levels of detail
– Telling someone else ensures you really do
understand
Conn. LA - Kuhagen - Nov. 4, 2010
136
Prepare your library: If
implementing RDA
• Make policy decisions with colleagues
from various areas:
– Elements beyond RDA core elements you will
include in own records and accept in copy
records (consult with vendor and consortium
as needed)
– Decisions on options and alternatives or
always cataloger judgment
– Changes in existing records (e.g., form of
access points, GMD vs. 336-338 fields)
Conn. LA - Kuhagen - Nov. 4, 2010
137
Prepare your library: If not
implementing RDA
• Make policy decisions with colleagues
from various areas:
– Add RDA records from others to your
catalog for resources in your collection?
– If add RDA records, accept with no
changes? If make some changes, what
changes?
Conn. LA - Kuhagen - Nov. 4, 2010
138
Library system impact if RDA
records in your catalog
• Talk with IT staff and/or vendor to ensure
MARC 21 RDA changes implemented
(have been issued as regular MARC
updates)
• Make decisions on display and indexing
of new fields in your OPAC
Conn. LA - Kuhagen - Nov. 4, 2010
139
Training and implementation
• If implementing RDA:
– Develop training materials
– Give demonstrations of the RDA Toolkit
– Review mappings
– Create templates, macros, workflows
– Practice, practice, practice !!!
– Discuss practice/real records
– Foster cataloger judgment (includes
“stamping out tweaking” of others’ records)
Conn. LA - Kuhagen - Nov. 4, 2010
140
Training and implementation
• If not implementing RDA:
– Explain changes from AACR2 so staff can
understand records in Worldcat, etc. (and
especially if RDA records added to your
catalog)
– Explain changes in MARC 21 formats
Conn. LA - Kuhagen - Nov. 4, 2010
141
Inform your library’s users
• Explain changes in display and indexing
• If policy is not to change authorized
access points to same form in all records,
give guidance where forms are different
Conn. LA - Kuhagen - Nov. 4, 2010
142
Down the road ...
• Stay informed/investigate:
– Controlled vocabularies on the Web
– Linked data
– Encoding schema successor to MARC 21
• Talk with colleagues in other information
communities (e.g., archives, museums)
• Exciting challenges and opportunities!
Conn. LA - Kuhagen - Nov. 4, 2010
143
Questions now on
today’s topics?
======
Questions later on any aspect of
RDA: LChelp4rda@loc.gov
======
Questions on today’s presentation:
jkuh@loc.gov
Conn. LA - Kuhagen - Nov. 4, 2010
144