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

2 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

3 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

Outline for today 1. Introduction: Basics of relationships in RDA 2. People and resources 3. Resources: works, expressions, manifestations, items 4. People: persons, families and corporate bodies 4

5 Basics of relationships 1. What are relationships? 2. Why relationships? Expressing Relationships: Helps users find what they want!

6 Basics of relationships 1. Entities being related? 2. Types of relationships

7 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

8 Relationships in RDA  Chapters 18-22, Appendix I Resource and associated persons, families, corporate bodies  Chapters 24-28, Appendix J Between resources (works, expressions, manifestations, items)  Chapters 29-32, Appendix K Between persons, families, corporate bodies

9 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 PCC Guidelines

10 [Screen image from the RDA Toolkit ( ) used by permission of the Co-Publishers for RDA (American Library Association, Canadian LibraryAssociation, and CILIP: Chartered Institute of Library and Information Professionals)]

11 Methods to express relationships 1. Identifier, e.g # $0 (DLC)n $e author # $0 (uri) names/n $e author 2. Authorized access point, e.g # $a Society of Actuaries, $e author. 3. Structured description, e.g $i Also issued as: $t Health statistics 4. Unstructured description, e.g. 500 ## $a Translation of the author’s novel Digital fortress.

12 Designation of relationships in MARC bibliographic records $e of and $j of 111 and 711 $i of $i of 76X-78X linking entry fields MARC 21 coding (e.g., “continues”; “continued by”) PCC Guidelines - Guideline 14 MARC fields

13 Citing another resource: authorized access points In MARC 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.

14 Citing another resource: linking entry fields In MARC 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

15 Designation of relationships in MARC authority records  In older authority records relationships are shown in: 500 $w and , 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)

16 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

17 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)

18 Creator relationships Persons/families/bodies related to works author compiler filmmaker interviewer programmer and others … (RDA Appendix I)

19 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

20 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

21 Example Creator work relationship 110 2_ $a Society of Actuaries, $e author _ $a American Academy of Actuaries, $e author _ $a Fleischer, Tsippi, $e composer _ $a Israel, $e enacting jurisdiction.

22 Example Others associated with work Others associated with works (19.3): 710 2_ $a Geological Survey (U.S.), $e issuing body _ $a Irgun ha-gananim be-Yiśra ʼ el, $e sponsoring body _ $a Fox, Eytan, $d $e film director _ $a Chazan, Robert, $e honouree.

23 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 $w r 500 1_ $i Screenwriter: $a Bernheimer, Avner, $d $w r

24 Contributor relationships Persons/families/bodies related to expressions Translators Editors of compilations Performers Illustrators Arrangers of music Compilers

25 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

26 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

27 Example 1: Contributor relationships 100 1# $a Wood, Audrey, $e author $a The napping house / $c Audrey Wood ; illustrated by Don Wood # $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

28 Example 2: Contributor relationships 100 1# $a Lindgren, Astrid, $d , $e author $a Pippi Långstrump. $l English $a Pippi Longstocking / $c Astrid Lindgren ; translated by Tiina Nunnally # $a Nunnally, Tiina, $d $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.

29 Example 3: Contributor relationships 245 $a Favorite American music / $c performed by the Baltimore Symphony Orchestra with Marin Alsop conducting. 505 $a $a Baltimore Symphony Orchestra, $e performer. 700 $a Alsop, Marin, $e conductor.* * Could have used the more general “$e performer” for Alsop.

30 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 $w r 100 1_ $a Pushkin, Aleksandr Sergeevich, $d $t Evgenii ̆ Onegin. $l English $s (Kayden) 500 1_ $i Translator: $a Kayden, Eugene M. $q (Eugene Mark), $d ǂ w r

31 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

32 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 PCC Guidelines

33 Examples: Relationships to manifestations 264 #1 $a Bethesda : $b NIH, $c # $a National Institutes of Health (U.S.), $e broadcaster. 264 #1 $a St. Paul : $b West Publishing Company, $c # $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.”

34 Relationships to items Persons/families/bodies related to items (RDA 22.0, Appendix I.5) Owners Custodians Curators Binders Inscribers  Cataloger judgment

35 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 $5 DLC 700 $a Jefferson, John, $e donor.

36 Summary Works: First creator in 1XX, others in 7XX $e/$j is optional in RDA $i of 5XX in authorities  Expression: First contributor in 7XX field $e required by LC for illustrator for resources intended for children $i in 5XX in authorities  Manifestations: Cataloger judgment  Items: Cataloger judgment

37 Relationships between resources Related works, expressions, manifestations, and items  Relationships in bibliographic and/or authority records: Related works (ch. 25) Related expressions (ch. 26) Related manifestations (ch. 27) Related items (ch. 28)

38 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)

39 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

40 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

41 Example: Whole-part work Authorized access points for the works: 100 1# $a Shakespeare, William, $d $a Plays. $k Selections $a Hamlet ; $b King Lear / $c William Shakespeare. * $i Contains (work): $a Shakespeare, William, $d $t Hamlet. * $i Contains (work): $a Shakespeare, William, $d $t King Lear. * Even though 2nd indicator in 700 indicates the relationship “Contains”, PCC practice is to also include the designator.

42 Example: serial related works Structured descriptions and three identifiers each: $a TCA journal $i Continues (work): $t Journal of professional counseling, practice, theory, & research $x $w (DLC) $w (OCoLC) $a Journal of professional counseling, practice, theory, & research $i Continues (work): $t TCA journal $x $w (DLC) $w (OCoLC) indicators 00 = relationship “Continued by” 780 indicators 00 = relationship “Continues”

43 Authority record, work relationship 046 ## $k # $a Chase, Mary, $d $t Harvey 380 ## $a Play 530 #0 $i Adapted as a motion picture (work): $a Harvey (Motion picture) $w r 670 ## $a Harvey, ## $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)

44 Related expressions  RDA 26.1  Common expression relationships: Whole-part (e.g., translations in a compilation) Revisions Editions Translations Language editions Abridgements

45 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

46 Example 1: Whole-part expression Authorized access points for the expressions: 100 1# $a Petterson, Per, $d $a Two Norwegian novels / $c Per Petterson # $a Out stealing horses -- To Siberia $i Contains (expression): $a Petterson, Per, $d $t Ut og stjæle hester. $l English $i Contains (expression): $a Petterson, Per, $d $t Til Sibir. $l English $a Out stealing horses $a To Siberia.

47 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 $a Journal of environmental policy and law in Latin America and the Caribbean $i Issued also in Spanish under title: $t Revista de política y derecho ambientales en América Latina y el Caribe.

48 Example 3: Related expression - translation Authorized access point: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale # $i Translation of: $a Brown, Dan, $d $t Digital fortress.

Example 4: Related expression - translation Structured description in 500 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale / $c Dan Brown. 500 ## $a Translation of: Digital fortress / Dan Brown. -- 1st ed. -- New York : St. Martin’s Press, pages ; 22 cm.

50 Example 5: Related expression - translation Structured description in 765 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale / $c Dan Brown. * $i Translation of: $a Brown, Dan, $t Digital fortress $b 1st ed. $d New York : St. Martin’s Press, 1998 $h 371 pages ; 22 cm $w (DLC) * 2nd indicator “blank” = “Translation of” 2nd indicator “8” = No display constant generated

51 Example 6: Related expression - translation Unstructured description in 500 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale / $c Dan Brown. 500 ## $a Translation of the author’s novel Digital fortress.

52 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.

53 Recording related manifestations  Structured or unstructured description: Linking entry fields: 775 or 776 5XX note Not by an authorized access point  LC-PCC PS : 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 the original (no need to upgrade)

54

55 Recording related manifestations  LC-PCC PS : 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

56

57

58 Example: Related manifestations $a Health statistics for elementary -school children. 264 #1 $a Baltimore : $b Johns Hopkins University, $c ## $a volumes ; $c 27 cm $i Also issued as: $t Health statistics for elementary-school children $d Baltimore : Johns Hopkins University, $h CD-ROMs ; 4 3/4 in.

59 Reproductions - LC-PCC PS  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

60 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

61 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”

62 Recording Related items RDA 28.1/LC-PCC PS 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

63 Examples: Related items 501 $i Bound with: $a ___________. $5 DLC 775 $i Reproduction of (item): $t Hiking in Unicoi State Park $d Helen, GA : RST Publishers, 1955 $h 22 p. : ill. ; 19 cm. 501 $i Filmed with: $a Liṭerarishe monaṭsshrifṭen. [Vilna : O. fg.], Yidishe folks-lider / Emil Sekulets. Bukaresht : Muzik-Farlag fun dem Kompozitorn-Farband fun der R.F.R., Ṿos geṿen : eṭyudn un zikhroynes̀ / A. Liṭṿaḳ. [Ṿilne] : Ṿilner farlag fun B. Ḳletsḳin, $5 WaU

64  Entities in relationships: Group 2  Relationships in authority records: Related persons (ch. 30) Related families (ch. 31) Related corporate bodies (ch. 32) Relationships between persons, families, and corporate bodies

65  LC/PCC core relationships: Different identities for persons (LC- PCC PS 30.1) Immediately preceding/succeeding corporate bodies (LC-PCC PS 32.1) Relationships between persons, families, and corporate bodies

66 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

67 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

68 Example: 2 identities 100 1# $a King, Stephen, $d # $a Bachman, Richard 100 1# $a Bachman, Richard 500 1# $a King, Stephen, $d RDA would allow coding as: 100 1# $a King, Stephen, $d # $i Alternate identity: $a Bachman, Richard $w r 100 1# $a Bachman, Richard 500 1# $i Real identity: $a King, Stephen, $d $w r

69 Examples: 3+ different identities 100 1# $a Twain, Mark, $d # $w nnnc $a Clemens, Samuel, $d # $w nnnc $a Snodgrass, Quintus Curtius, $d ## $a For works of this author written under other names, search also under $b Clemens, Samuel Langhorne, , $b Snodgrass, Quintus Curtius, # $a Clemens, Samuel, $d # $w nnnc $a Twain, Mark, $d ## $a For a listing of the names used by this author, search also under: $b Twain, Mark, Authorized access point in authority records:

70 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

71 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

72 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

73 Examples: person related to corporate body or family 100 1# $a Garr, Arnold K # $i Employer: $a Brigham Young University $w r 100 1# $a Carroll, Charles N. $q (Charles Nagus), $d # $i Descendants: $a Carroll (Family : $g Carroll, Charles N. (Charles Negus), ) $w r

74 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

75 Module 4: Relationships in RDA Questions?