LC Training for RDA:
Resource Description & Access
Module 4:
Relationships in RDA
-- in bibliographic records and
in authority records
Cooperative and Instructional Programs Division
Library of Congress
September 2012
Revised by A. Schiff, July 2013
Acknowledgements


This course has been adapted from
training developed by Barbara Tillett and
Judith Kuhagen, Library of Congress
Policy and Standards Division, for several
training sessions.
COIN gratefully acknowledges their
permission to adapt the material for the
present purpose
2
Learning Objectives for Module 4 -Relationships in RDA



Understand the basics of
relationships in RDA
Determine the relationships that are
core to LC catalogers
Express relationships correctly in
bibliographic records
3
Outline for today
1.
2.
3.
4.
Introduction: Basics of
relationships in RDA
People and resources
Resources: works, expressions,
manifestations, items
People: persons, families and
corporate bodies
4
Basics of relationships
1. What are relationships?
2. Why relationships?
Expressing Relationships:
Helps users find what they want!
5
Basics of relationships
1. Entities being related?
2. Types of relationships
6
Entities being related
Relationships between:
1. Resources and associated persons,
families, and corporate bodies
2. Resources (works, expressions,
manifestations, items)
3. Persons, families, corporate bodies
7
Relationships in RDA

Chapters 18-22, Appendix I


Chapters 24-28, Appendix J


Resource and associated persons,
families, corporate bodies
Between resources (works, expressions,
manifestations, items)
Chapters 29-32, Appendix K

Between persons, families, corporate
bodies
8
Relationship designators

RDA appendices I, J, and K





Not CORE
Not closed lists
“If none of the terms listed in this
appendix is appropriate or sufficiently
specific, use another concise term to
indicate the nature of the relationship.”
LC policy: decisions in some LC-PCC
PS’s; otherwise, cataloger judgment
to use
PCC Guidelines
9
[Screen image from the RDA Toolkit (www.rdatoolkit.org) used by permission
of the Co-Publishers for RDA (American Library Association, Canadian Library
Association, and CILIP: Chartered Institute of Library and Information Professionals)]
10
Methods to express relationships
1. Identifier, e.g.
110 2# $0 (DLC)n 80119883 $e author.
 110 2# $0 (uri)http://id.loc.gov/authorities/
names/n80119883 $e author

2. Authorized access point, e.g.

110 2# $a Society of Actuaries, $e author.
3. Structured description, e.g.

776 08 $i Also issued as: $t Health statistics
4. Unstructured description, e.g.

500 ## $a Translation of the author’s novel
11
Digital fortress.
Designation of relationships in
MARC bibliographic records
$e of 100-110 and 700-710
 $j of 111 and 711
 $i of 700-730
 $i of 76X-78X linking entry fields
 MARC 21 coding (e.g., 780 00
“continues”; 785 00 “continued by”)
 PCC Guidelines - Guideline 14
 MARC 21 264 fields

12
Citing another resource:
authorized access points
In MARC 700-730 fields:


Give the form represented by NAR*
If there is no NAR, give the RDA form
* Exception: Do not use AACR2 NAR with “Polyglot” or more
than one language in subfield $l for multiple expressions.
13
Citing another resource:
linking entry fields
In MARC 760-787 fields:


Copy/paste what is in the existing
record for that resource and adjust
the subfield coding as appropriate
OCLC has “Insert from Cited
Record” feature to automatically fill
in field based on OCLC # of the
related record
14
Designation of relationships in
MARC authority records

In older authority records relationships
are shown in:


500 $w and 663
510, 511, and 530 $w
110 2# $a Society of Actuaries
510 2# $a Actuarial Society of America $w a
510 2# $a American Institute of Actuaries $w a

RDA relationships are now recorded in
5XX $i and $w r (more on this later)
15
Summary



You have been recording
relationships in AACR2
There are some new concepts about
relating entities in RDA
Relationships are recorded as
authorized access points, notes, and
linking fields
16
Persons/families/bodies and
resources




Creators and others associated with
works (ch. 19)
Contributors associated with
expressions (ch. 20)
Manufacturers, publishers,
distributors associated with
manifestations (ch. 21)
Owners, annotators, autographers,
etc. associated with items (ch. 22)
17
Creator relationships
Persons/families/bodies related to
works






author
compiler
filmmaker
interviewer
programmer
and others … (RDA Appendix I)
18
Creator relationships (con’t)
LC-PCC PS 19.2 Creator


CORE element. If more than one
creator, only first creator with
principal responsibility is required. If
principal responsibility not indicated,
only first-named creator is required.
Other creator relationships are
optional in RDA
19
Creator relationships in
bibliographic records


Give as authorized access point in MARC
1XX field (and 7XX field if more than one
creator or if “other” associated with work)
in bibliographic record
Relationship designators from RDA
appendix I.2 in subfield $e/$j of 1XX and
7XX field



Not a closed list
Do not include $e in name authority record
PCC Guidelines: include RD for all creators,
whether coded 1XX or 7XX
20
Example Creator work relationship
110 2_ $a Society of Actuaries, $e author.
710 2_ $a American Academy of Actuaries,
$e author.
100 1_ $a Fleischer, Tsippi, $e composer.
110 1_ $a Israel, $e enacting jurisdiction.
21
Example Others associated with
work
Others associated with works (19.3):
710 2_ $a Geological Survey (U.S.), $e issuing
body.
710 2_ $a Irgun ha-gananim be-Yiśraʼel, $e
sponsoring body.
700 1_ $a Fox, Eytan, $d 1964- $e film director.
700 1_ $a Chazan, Robert, $e honouree.
22
Creator and other relationships
in authority records


Give as authorized access point in MARC 5XX
field
Relationship designators from RDA appendix
I.2 in subfield $i of 5XX


Not a closed list
Consider proposing new terms to JSC
130 _0 Yosi ṿe-G'ager
500 1_ $i Film director: $a Fox, Eytan, $d 1964- $w r
500 1_ $i Screenwriter: $a Bernheimer, Avner, $d
1968- $w r
23
Contributor relationships
Persons/families/bodies related to
expressions






Translators
Editors of compilations
Performers
Illustrators
Arrangers of music
Compilers
24
Contributor relationships (cont.)

Not core in RDA

LC-PCC PS 20.2



CORE for LC: first illustrator of
resources intended for children
If multiple illustrators are present,
apply cataloger judgment to give more
than the first
PCC practice: record contributors if
considered important for identification
25
Contributor relationships (cont.)


Give as authorized access point in
MARC 7XX fields in bibliographic
record
Relationship designators from RDA
appendix I.3 in subfield $e/$j of 7XX
field


Not a closed list
Do not include $e in name authority
record
26
Example 1: Contributor relationships
100 1# $a Wood, Audrey, $e author.
245 14 $a The napping house / $c Audrey Wood
; illustrated by Don Wood.
700 1# $a Wood, Don, $e illustrator.
Notes: 1) 2nd statement of responsibility is not core; also,
it isn’t needed to justify the 700 field.
2) LC policy: give $e illustrator
3) PCC policy: give any contributors considered
important for identification
27
Example 2: Contributor relationships
100 1# $a Lindgren, Astrid, $d 1907-2002,
$e author.
240 10 $a Pippi Långstrump. $l English
245 10 $a Pippi Longstocking / $c Astrid
Lindgren ; translated by Tiina Nunnally.
700 1# $a Nunnally, Tiina, $d 1952- $e
translator.
Notes: 1) PCC: relationship designator for creators required
2) PCC: relationship designators for others highly
encouraged
3) 2nd statement of responsibility is not core; also,
it isn’t needed to justify the 700 field.
28
Example 3: Contributor relationships
245 $a Favorite American music / $c performed
by the Baltimore Symphony Orchestra with
Marin Alsop conducting.
505 $a ...
710 $a Baltimore Symphony Orchestra, $e
performer.
700 $a Alsop, Marin, $e conductor.*
* Could have used the more general “$e performer” for Alsop.
29
Contributor relationships in
authority records


Give as authorized access point in MARC 5XX
field
Relationship designators from RDA appendix I.3
in subfield $i of 5XX


Not a closed list
Consider proposing new terms to JSC
100 0_ $a Plato. $t Amatores. $l Greek $s (Souilhé)
500 1_ $i Editor: $a Souilhé, Joseph, $d 1885-1941 $w r
100 1_ $a Pushkin, Aleksandr Sergeevich, $d 1799-1837.
$t Evgeniĭ Onegin. $l English $s (Kayden)
500 1_ $i Translator: $a Kayden, Eugene M. $q (Eugene
30
Mark), $d 1886-1977 ǂw r
Relationships to manifestations
Persons/families/bodies related to
manifestations (RDA 21.0, Appendix I.4)





Producers (of unpublished resources)
Publishers (e.g., broadcasters)
Manufacturers (e.g., engravers, printers)
Distributors (e.g., film distributor)
Other persons, families, or corporate
bodies associated with a manifestation
(e.g., book designers, platemakers, etc.)
Cataloger judgment whether to record in 7XX
31
Relationships designators for
persons/families/bodies associated with
manifestations



Relatively few terms are listed in
Appendix I.4
The terms “producer,” “publisher,”
“manufacturer,” “distributor” are
separate elements -- not found in
Appendix I.4
PCC Guidelines: Guideline 4
32
Examples: Relationships to
manifestations
264 #1 $a Bethesda : $b NIH, $c 2008.
710 2# $a National Institutes of Health
(U.S.), $e broadcaster.
264 #1 $a St. Paul : $b West Publishing
Company, $c 2011710 2# $a West Publishing Company, $e
publisher.
PCC Guidelines: “Assign an RDA element name as a
relationship designator, e.g., "creator" (19.2) or "publisher"
(21.3) if it will most appropriately express the relationship.”
33
Relationships to items
Persons/families/bodies related to
items (RDA 22.0, Appendix I.5)






Owners
Custodians
Curators
Binders
Inscribers
Cataloger judgment
34
Examples: Relationships to items
500 $a University Library's copy has
ms. notes by author on endpapers.
$5 IaH
700 $a Smiley, Jane, $e annotator.
541 $c Gift; $a John Jefferson; $d 2011.
$5 DLC
700 $a Jefferson, John, $e donor.
35
Summary
Works:




Expression:





First creator in 1XX, others in 7XX
$e/$j is optional in RDA
$i of 5XX in authorities
First contributor in 7XX field
$e required by LC for illustrator for
resources intended for children
$i in 5XX in authorities
Manifestations: Cataloger judgment
36
Items: Cataloger judgment
Relationships between resources
Related works, expressions,
manifestations, and items

Relationships in bibliographic and/or
authority records:




Related
Related
Related
Related
works (ch. 25)
expressions (ch. 26)
manifestations (ch. 27)
items (ch. 28)
37
Related works


RDA 25.1
Common work relationships:

Whole-part, e.g.,
Works in a compilation
 Chapters in a book




Adaptations
Supplements
Sequential relationships (e.g., earlier
and later serials)
38
Related works

Not core in RDA

LC-PCC PS 25.1
LC core related work relationships:


Whole-part relationships for works
in a compilation
Sequential serial relationships
39
Whole-part relationships for
compilations



LC/PCC: Give MARC 505 contents note unless
contents indicated in another part of the
description (e.g., in MARC 245 $a because no
collective title present) or unless burdensome
LC/PCC: Give one MARC 7XX analytical
authorized access point for the predominant
or first work if it is substantial; cataloger
judgment if additional 7XX fields for other
works
Don’t give analytical authorized access points
for some works: anthologies of poetry,
conference proceedings, hymnals, journals,
interviews or letters, etc. – LC-PCC PS 25.1 40
Example: Whole-part work
Authorized access points for the works:
100 1# $a Shakespeare, William, $d 15641616.
240 10 $a Plays. $k Selections
245 10 $a Hamlet ; $b King Lear / $c
William Shakespeare.
*700 12 $i Contains (work): $a Shakespeare,
William, $d 1564-1616. $t Hamlet.
*700 12 $i Contains (work): $a Shakespeare,
William, $d 1564-1616. $t King Lear.
* Even though 2nd indicator in 700 indicates the relationship
“Contains”, PCC practice is to also include the designator.41
Example: serial related works
Structured descriptions and three identifiers each:
245 00 $a TCA journal.
785 00 $i Continues (work): $t Journal of
professional counseling, practice,
theory, & research $x 1556-6382 $w (DLC)
2005205756 $w (OCoLC)55891574
245 00 $a Journal of professional counseling,
practice, theory, & research.
780 00 $i Continues (work): $t TCA journal $x
1556-4223 $w (DLC) 93645762 $w (OCoLC)
26906768
785 indicators 00 = relationship “Continued by”
780 indicators 00 = relationship “Continues”
42
Authority record, work relationship
046 ## $k 1944
100 1# $a Chase, Mary, $d 1907-1981. $t
Harvey
380 ## $a Play
530 #0 $i Adapted as a motion picture
(work): $a Harvey (Motion picture)
$w r
670 ## $a Harvey, 1950.
670 ## $a Wikipedia, January 6, 2011 $b
(Harvey; Pulitzer Prize-winning
play by Mary Chase; premiered in
1944; adapted for film by Chase,
Oscar Brodney, and Myles Connolly
in 1950)
43
Related expressions


RDA 26.1
Common expression relationships:






Whole-part (e.g., translations in a
compilation)
Revisions
Editions
Translations
Language editions
Abridgements
44
Related expressions: LC core
LC-PCC PS 26.1

LC/PCC core expression relationships:


Whole-part relationships for expressions
in a compilation (same policy as for
works)
Sequential serial relationships
45
Example 1: Whole-part expression
Authorized access points for the expressions:
100 1# $a Petterson, Per, $d 1952245 10 $a Two Norwegian novels / $c Per
Petterson.
505 0# $a Out stealing horses -- To Siberia.
700 12 $i Contains (expression): $a
Petterson, Per, $d 1952- $t Ut og
stjæle hester. $l English.
700 12 $i Contains (expression): $a
Petterson, Per, $d 1952- $t Til
Sibir. $l English.
740 02 $a Out stealing horses.
46
740 02 $a To Siberia.
Example 2: serial related
expression
Structured description for other language edition:
130 0# $a Revista de política y derecho
ambientales en América Latina y el
Caribe. $l English.
245 10 $a Journal of environmental policy
and law in Latin America and the
Caribbean.
775 08 $i Issued also in Spanish under
title: $t Revista de política y
derecho ambientales en América
Latina y el Caribe.
47
Example 3: Related expression translation
Authorized access point:
100
240
245
700
1# $a Brown, Dan, $d 196410 $a Digital fortress. $l French
10 $a Forteresse digitale.
1# $i Translation of: $a Brown, Dan,
$d 1964- $t Digital fortress.
48
Example 4: Related expression translation
Structured description in 500 field:
100
240
245
500
1#
10
10
##
$a Brown, Dan, $d 1964$a Digital fortress. $l French
$a Forteresse digitale / $c Dan Brown.
$a Translation of: Digital fortress /
Dan Brown. -- 1st ed. -- New York :
St. Martin’s Press, 1998. -- 371
pages ; 22 cm.
Example 5: Related expression translation
Structured description in 765 field:
100 1# $a Brown, Dan, $d 1964240 10 $a Digital fortress. $l French
245 10 $a Forteresse digitale / $c Dan
Brown.
*765 08 $i Translation of: $a Brown, Dan,
1964- $t Digital fortress $b 1st
ed. $d New York : St. Martin’s
Press, 1998 $h 371 pages ; 22 cm
$w (DLC) 9703318
* 2nd indicator “blank” = “Translation of”
2nd indicator “8” = No display constant generated
50
Example 6: Related expression translation
Unstructured description in 500 field:
100 1# $a Brown, Dan, $d 1964240 10 $a Digital fortress. $l French
245 10 $a Forteresse digitale / $c Dan
Brown.
500 ## $a Translation of the author’s novel
Digital fortress.
51
Related manifestations

RDA 27.1

Common manifestation
relationships:




Reproductions
Different formats for same expression
(e.g., book vs. CD; book vs. PDF)
Special issues
Related manifestation is a core
element for LC and PCC for
reproductions.
52
Recording related manifestations

Structured or unstructured description:




Linking entry fields: 775 or 776
5XX note
Not by an authorized access point
LC-PCC PS 27.1.1.3: use structured
description




775 if carrier of reproduction is same as
original
776 if carrier not same as original
Use “Reproduction of (manifestation)”
unless a particular PCC program
recommends otherwise
Use information as is from the record for
53
the original (no need to upgrade)
54
Recording related manifestations

LC-PCC PS 27.1.1.3: use structured
description


For serials, give reciprocal relationship
on the record for the original. Use
“Reproduced as” unless a particular PCC
program recommends otherwise
Generally do not give reciprocal
relationship on originals for monographs
and integrating resources
55
56
57
Example: Related manifestations
245 00 $a Health statistics for elementary
-school children.
264 #1 $a Baltimore : $b Johns Hopkins
University, $c 2009300 ## $a volumes ; $c 27 cm
776 08 $i Also issued as: $t Health statistics
for elementary-school children $d
Baltimore : Johns Hopkins University,
2009- $h CD-ROMs ; 4 3/4 in.
58
Reproductions - LC-PCC PS
27.1.1.3


If the manifestation is a compilation
containing reproductions of works not
published earlier as a compilation,
give a bibliographic history note,
rather than MARC 775/776 linking
fields, about the individual works if
you think that information would be
helpful
If reproduction is facsimile of a
manuscript and attributes for use in
775/776 are not readily available,
give bibliographic history note instead
59
Related items


RDA 28.1
Common item relationships




Reproduction of a specific copy
“Bound with”
Item added to copy of manifestation in
a special collection
Relationships that apply only to a
single copy of the manifestation -so, usually local information
60
Related item: LC core

LC-PCC PS 28.1

CORE for LC for:



Reproductions when important to
specify the item that was reproduced
Special relationships for rare materials
if warranted
“Bound withs”
61
Recording Related items
RDA 28.1/LC-PCC PS 28.1.1.3
Structured or unstructured description:
 Linking entry fields: 7XX
 5XX
 Not by an authorized access point


Use relationship designators in RDA
appendix J.5 in $i of 7XX linking fields
For reproductions, use 775 if carrier of
reproduction is same as original; 776 if
carrier of reproduction different from
original
62
Examples: Related items
501 $i Bound with: $a ___________. $5 DLC
501 $i Filmed with: $a Liṭerarishe
monaṭsshrifṭen. [Vilna : O. fg.], 1908 -Yidishe folks-lider / Emil Sekulets.
Bukaresht : Muzik-Farlag fun dem
Kompozitorn-Farband fun der R.F.R., 1959
-- Ṿos geṿen : eṭyudn un zikhroynes̀/ A.
Liṭṿaḳ. [Ṿilne] : Ṿilner farlag fun B.
Ḳletsḳin, 1925. $5 WaU
775 $i Reproduction of (item): $t Hiking in
Unicoi State Park $d Helen, GA : RST
Publishers, 1955 $h 22 p. : ill. ;
63
19 cm.
Relationships between persons,
families, and corporate bodies


Entities in relationships: Group 2
Relationships in authority records:



Related persons (ch. 30)
Related families (ch. 31)
Related corporate bodies (ch. 32)
64
Relationships between persons,
families, and corporate bodies

LC/PCC core relationships:


Different identities for persons (LCPCC PS 30.1)
Immediately preceding/succeeding
corporate bodies (LC-PCC PS 32.1)
65
Recording relationships between
persons/families/corporate bodies



Relationship recorded in authority
record in 5XX field
Use Appendix K relationship
designators in $i of 5XX
LC/PCC policy: Some relationships
indicated by values in subfield $w
rather than designators in subfield $i:

Different identities for persons
66
LC policy for different identities


2 identities = un-coded 500 fields in
each NAR
3 or more identities: DCM Z1 yellow
page for the 663 field gives
information about use of the 663 field
with $w nnnc in 500 fields
67
Example: 2 identities
100 1# $a King, Stephen, $d 1947500 1# $a Bachman, Richard
100 1# $a Bachman, Richard
500 1# $a King, Stephen, $d 1947-
RDA would allow coding as:
100 1# $a King, Stephen, $d 1947500 1# $i Alternate identity: $a Bachman,
Richard $w r
100 1# $a Bachman, Richard
500 1# $i Real identity: $a King, Stephen, $d
1947- $w r
68
Examples: 3+ different identities
Authorized access point in authority records:
100 1# $a Twain, Mark, $d 1835-1910
500 1# $w nnnc $a Clemens, Samuel, $d 1835-1910
500 1# $w nnnc $a Snodgrass, Quintus Curtius, $d
1835-1910
663 ## $a For works of this author written under
other names, search also under $b Clemens,
Samuel Langhorne, 1835-1910, $b Snodgrass,
Quintus Curtius, 1835-1910
100 1# $a Clemens, Samuel, $d 1835-1910
500 1# $w nnnc $a Twain, Mark, $d 1835-1910
663 ## $a For a listing of the names used by this
author, search also under: $b Twain, Mark,
1835-1910
69
Example: related corporate bodies
Previous AACR2 and early RDA practice
110 2# $a Library of Congress. $b Policy and
Standards Division
510 2# $w a $a Library of Congress. $b
Cataloging Policy and Support Office
110 2# $a Library of Congress. $b Cataloging
Policy and Support Office
510 2# $w b $a Library of Congress. $b
Policy and Standards Division
70
Example: related corporate bodies
Current RDA practice
110 2# $a Library of Congress. $b Policy and
Standards Division
510 2# $i Predecessor: $a Library of
Congress. $b Cataloging Policy and
Support Office $w r
110 2# $a Library of Congress. $b Cataloging
Policy and Support Office
510 2# $i Successor: $a Library of Congress.
$b Policy and Standards Division $w r
71
Other relationships

LC/PCC: if giving other
relationships in name authority
records:


Cataloger judgment to give
relationship designator from RDA
appendix K in subfield $i to identify
specific relationship
Need value “r” in subfield $w if using
subfield $i
72
Examples: person related to
corporate body or family
100 1# $a Garr, Arnold K.
510 2# $i Employer: $a Brigham Young
University $w r
100 1# $a Carroll, Charles N. $q (Charles
Nagus), $d 1817-1902
500 3# $i Descendants: $a Carroll
(Family : $g Carroll, Charles N.
(Charles Negus), 1817-1902) $w r
73
Summary
Module 4: Relationships
“Relate”: 2nd main goal of RDA (1st = identify)
 Relationships within and between FRBR Group 1
(work, expression, manifestation, item) and
Group 2 (person, family, corporate body) entities
 Relationship designators in appendices I, J, K
 LC and PCC core relationships
74
Module 4:
Relationships in RDA
Questions?
75