LC Training for RDA:
Resource Description & Access
Module 5:
Relationships in RDA
-- in bibliographic records and
in authority records
Cooperative and Instructional Programs Division
Library of Congress
Sept. 2012
Adapted by the National Library of New Zealand, November 2012
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
This version of this material




Adapted from the original Library of
Congress training programme by the
National Library of New Zealand
Some slides have been edited in red
Other slides have been removed to fit
with the way training has been organised
by the National Library of New Zealand
Extra slides have been added with red
title boxes to distinguish them from the
LC originals.
Basics of relationships
1.
What are relationships?
Associations between entities
2. Why relationships?
To help users find what they want
4
What kinds of relationships?
1.
Primary relationships (section 5,
chapt. 17)
Relationships within a resource, such as
the work it represents
2.
Persons/families/corporate bodies
related to a resource (section 6,
chapts 18-22)
Authors, illustrators and other
contributors to content. Also
relationships at the manifestation and
item level, e.g donor, former owner, etc.
What kinds of relationships? (contd.)
3. Relationships between works,
expressions, manifestations & items
(section 8, chapts. 24-28) e.g.
Adaptations, translations, arrangements,
etc.
4. Relationships between persons,
families & corporate bodies (section
9, chapts. 29-32)
Authority relationships such as
pseudonyms or former and later names
Methods for recording
relationships
1. Identifiers (not yet)
2. Authorized access points, e.g.

110 2# $a Society of Linguists, $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
Digital fortress.
7
Core Relationships



RDA: Creator used to construct
authorized access point for the work
LC: Above plus first illustrator of
resources intended for children
NLNZ? Will follow the RDA and LC
core relationships – no further
policy on choice of relationships to
record yet.
NLNZ policy criteria?




User needs
Sustainable
Explainable (to other cataloguers)
Predictable (for other librarians &
users)
1. Primary Relationship or
Relationships between …
Primary Relationships
Section 5
Chapter 17
Relationships between a work and its
expressions, the expression and its
manifestations, etc.
Work
Expression
Manifestation
From NLA RDA Train the Trainer Course
Item
Primary relationships
Work
manifested
Larsson, Stieg,
1954-2004. Man
som hatar
kvinnor
Expression
manifested
Larsson, Stieg, 19542004. Man som hatar
kvinnor. English
From VUW MLIS paper INFO 546
11
2. 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, annotator, autographer,
etc. associated with items (ch. 22)
12
Creator relationships
Persons/families/bodies related to
works






author
compiler
filmmaker
interviewer
programmer
and others …
13
Creator relationships (con’t)
LCPS 19.2:


LC/RDA core relationship: Give first
creator with principal responsibility
LC: If multiple creators associated with the
work are present, apply cataloger
judgment (NLNZ: apply some criteria that
you can explain to other cataloguers) to
give more than the first
14
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 of 1XX and
7XX field
 Not a closed list
 Do not include $e in name authority
record
15
Example Creator work relationship
110 $a Society of Linguists, $e author.
710 $a Linguists International, $e author.
100 $a Glass, Philip, $e composer.
110 $a Virginia, $e enacting jurisdiction.
16
Example Others associated with
work
Others associated with works (19.3):
710 $a U.S. Geology Society, $e issuing body.
710 $a ABC Institute, $e sponsoring body.
17
Contributor relationships
Persons/families/bodies related to
expressions






Translators
Editors of compilations
Performers
Illustrators
Arrangers of music
Compilers
18
Contributor relationships (cont.)
LCPS 20.2:


LC core relationship: first illustrator of
resources intended for children
If multiple illustrators are present, apply
cataloger judgment (NLNZ: apply criteria
that you can explain to other cataloguers)
to give more than the first
19
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 of 7XX
field – only required for illustrator


Not a closed list
Do not include $e in name authority
record
20
Example 1: Contributor relationships
100 1# $a Wood, Audrey.
245 14 $a The napping house / $c Audrey Wood
; illustrated by Don Wood.
700 1# $a Wood, Don, $e illustrator.
Notes: 1) Relationship designator “author” could be given
for creator in 100 field.
2) 2nd statement of responsibility is not core; (but
NLNZ would record it following our policy) also,
it isn’t needed to justify the 700 field.
3) LC policy: give $e illustrator
21
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) Relationship designators “author” and “translator”
could be given -- cataloger judgment.(for LC)
2) 2nd statement of responsibility is not core; also,
it isn’t needed to justify the 700 field.
22
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.
23
Relationships to manifestations
Persons/families/bodies related to
manifestations (RDA 21.0, Appendix I.4)




Producers
Publishers (e.g., broadcasters)
Manufacturers (e.g., engravers, printers)
Distributors (e.g., film distributor)
These relationships are also recorded
as attributes of manifestations
24
Examples: Relationships to
manifestations
264 #1 $a Bethesda : $b NIH, $c 2008.
710 2# $a National Institutes of Health
(U.S.), $e broadcaster.
* “Publisher” isn’t used as an RDA relationship
designator because that relationship is an element.
25
Relationships to items
Persons/families/bodies related to items
(RDA 22.0, Appendix I.5)




Owners
Custodians
Curators
LC: cataloger judgment NLNZ: case-bycase as requested by curators
26
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.
27
Summary

Works:



Expression:





First creator in 1XX, others in 7XX
$e is optional
First contributor in 7XX field
$e required for illustrator for resources
intended for children
Manifestations:
Items:
NLNZ policy for which relationships
to record is yet to be developed
28
3. 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)
29
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)
30
Related works: LC core
LCPS 25.1
LC core work relationships:
Whole-part relationships for
works in a compilation
 Sequential serial relationships

31
Whole-part relationships for
compilations



LC: 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: Give one MARC 7XX analytical authorized
access point; 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, etc. – LCPS 25.1
32
Example: Whole-part work
Authorized access points for the works:
100 1# $a Shakespeare, William,
1616.
245 10 $a Hamlet ; $b King Lear
William Shakespeare.
*700 12 $a Shakespeare, William,
1616. $t Hamlet.
*700 12 $a Shakespeare, William,
1616. $t King Lear.
$d 1564-
/ $c
$d 1564$d 1564-
* 2nd indicator in 700 indicates the relationship “Contains”
33
Example: Adaptation of work



130 0# $a Hobbit (Motion picture : 2012)
245 00 $a The Hobbit : an unexpected
journey / $c directed by Peter Jackson
*700 1 $i Motion picture adaptation of
(work)$a Tolkien, J. R. R.$q (John
Ronald Reuel),$d 1892-1973).$t Hobbit.
Related expressions


RDA 26.1
Common expression relationships:






Whole-part (e.g., translations in a
compilation)
Revisions
Editions
Translations
Language editions
Abridgements
35
Related expressions: LC core
LCPS 26.1

LC core expression relationships:


Whole-part relationships for
expressions in a compilation (same
policy as for works)
Sequential serial relationships
36
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 $a Petterson, Per, $d 1952- $t Ut og
stjæle hester. $l English.
700 12 $a Petterson, Per, $d 1952- $t Til
Sibir. $l English.
740 02 $a Out stealing horses.
740 02 $a To Siberia.
37
Example 2: 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.
38
Example 3: 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.
$a Translation of: Digital fortress /
Dan Brown. -- 1st ed. -- New York :
St. Martin’s Press, 1998. -- 371
pages ; 22 cm.
Example 4: Related expression translation
Structured description in 765 field:
100
240
245
*765
1#
10
10
0#
$a Brown, Dan, $d 1964$a Digital fortress. $l French
$a Forteresse digitale.
$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”
40
Example 5: Related expression translation
Unstructured description in 500 field:
100
240
245
500
1#
10
10
##
$a
$a
$a
$a
Brown, Dan, $d 1964Digital fortress. $l French
Forteresse digitale.
Translation of the author’s novel
Digital fortress.
41
Related manifestations

RDA 27.1

Common manifestation
relationships:




Reproductions
Different formats for same expression
(e.g., book vs. CD; book vs. PDF)
Special issues
LC core relationships: reproductions
42
Recording related manifestations

Structured or unstructured description:




Linking entry fields: 775 or 776
5XX
Not by an authorized access point
LC: cataloger judgment to use
relationship designators in RDA
appendix J.4 in subfield $i if MARC
content designation does not give
relationship
43
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.
44
Reproductions: LC core

LC: Generally, give information
about the original in a linking field
(i.e. a structured description):



MARC 775 field if same carrier
776 field if different carrier
Use information as is from the
record for the original

If detailed information is not available,
give a bibliographic history note in a
MARC 500 field (this is an unstructured
45
description)
Example: Reproduction
Structured description including an identifier:
100 1# $a Ringwalt, J. Luther $q (John Luther)
245 10 $a Anecdotes of General Ulysses S. Grant.
264 #1 $a Washington, D.C. : $b Library of
Congress Preservation Microfilming
Program, $c 1993.
300 ## $a 1 microfilm reel (118 pages) ; $c 35 mm
776 08 $i Reproduction of (manifestation): $a
Ringwalt, J. Luther (John Luther) $t
Anecdotes of General Ulysses S. Grant $d
Philadelphia : J.B. Lippincott Company,
1886 $h 118 p. ; 18 cm. $n Call number
of original: E672.R58 $w (DLC)
10032685
46
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
47
Recording Related items
RDA 28.1
Structured or unstructured description:
 Linking entry fields: 7XX
 5XX (NLNZ uses 5XX fields for these relationships
in the AACR2 environment)
 Not by an authorized access point

Cataloger judgment to use relationship
designators in RDA appendix J.5 in subfield $i if
MARC content designation does not give
relationship
48
Examples: Related items
501 $i Bound with: $a ___________. $5 DLC
775 $i Reprint of (item): $t Hiking in
Unicoi State Park $d Helen, GA : RST
Publishers, 1955 $h 22 p. : ill. ;
19 cm.
49
Summary
Related resources LC core:
 Works and Expressions:



Manifestations:


Whole part compilations
Serial sequential relationships
Reproductions
Items:


“Bound withs”
Reproductions
50
4. 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)
51
What’s really important




Identify relationships for the
resource you describe
Determine which ones are
important
Work out how to record those using
RDA instructions and MARC coding
Contribute your ideas for NLNZ
policy on criteria for relationships
Exercise


Complete the Module 5 exercise
Record relationships for the
resource(s) you have been
describing