LC Training for RDA: Resource Description & Access Module 4: Relationships in RDA -- in bibliographic records and in authority records This is an overview of how relationships are handled in RDA. For complete information you’ll want to consult the chapters we point out in the toolkit and the Links to LC-PCC PS where LC core requirements and information about coding practices are given. Detailed information on LC core elements and coding are given in Documents R-1 pages 8-9, R-5. Module 2, Appendix 1 which you received contains information about relationships. There are specialized modules dealing specifically with relationships available here: RDA Refresher Training at LC: Special Topics http://www.loc.gov/aba/rda/Refresher_training_dec_2011.html Topics: Compilations [PPT, 1.85 MB]  RDA Elements in NARs [PPT, 2.5 MB]  Relationship Designators in RDA NARs [PPT, 999 KB]  Revised editions [PPT, 507 KB]  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 Barbara Tillett and Judy Kuhagen and other descriptive specialists in PSD created FRBR, RDA presentations, documentation, and training materials for the test as well as updated them for the refresher training after the test. They continue to provide expertise, guidance, and training to RDA catalogers here and outside of LC so we always want to acknowledge their great contribution to get us ready for RDA. We took a real general approach when we adapt the original module created by Judy knowing that specific situations should be covered in specialized courses. The original relationship module that we adapted from is available on LC’s RDA website, listed under training http://www.loc.gov/aba/rda/

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 Introduction: Basics of relationships in RDA People and resources Resources: works, expressions, manifestations, items People: persons, families and corporate bodies The module is broken into four parts: General basics of recording relationships in MARC 21, structure of RDA for relationship instructions, some other tools you can use

Basics of relationships 1. What are relationships? 2. Why relationships? Expressing Relationships: Helps users find what they want! The two basic goals in the structure of RDA are to identify and relate (from the FRBR/FRAD user tasks and the Statement of International Cataloguing Principles). Goal one to identify attributes or characteristics of works, expressions, manifestations, items, persons, corporate bodies, and families was discussed in modules 1 and 2. This module provides an overview of the other goal: relating entities. WHAT: The entities that we identify in our cataloging, the people, corporate bodies, and resources are associated with one another, these are relationships. We are familiar with the fact that authors have a relationship to the literary works they have written, composers have a relationship to the musical works they create, that we express relationships with linking fields when a serial changes its title, or when we want to link print and online manifestations. Not unfamiliar to us but relationships play a much more prominent role in the structure of RDA. WHY: Relationships are an important part of RDA. Expressing relationships in bibliographic and authority records helps users find what they want and tell users about other available resources. We show users the pathways to related materials. We need to reflect important relationships in our catalogs and resource discovery systems.

Basics of relationships 1. Entities being related? 2. Types of relationships Relationships consist of two parts: There are the entities being related – and what do we mean by entities? These are FRBR entities – the work, expression, manifestation, item (Group 1) and persons, corporate bodies, and families (Group 2), that you learned about in previous modules. Entities can be identified by their authorized access point (what we used to call a heading) or an identifier, such as an ISSN or an ISBN or URI (universal resource identifier) or a description (note). The other part of a relationship is stating the type of relationship, and we do this with a relationship designator. For example, a term that says what the relationship is, or what role a person, corporate body, or family plays with respect to a particular work or expression or manifestation or item.

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 This unit is a general introduction to FRBR relationships in RDA and how they are expressed in the catalog records you create. We will discuss three sets of relationships: Relationships between: FRBR Group 2 entities and Group 1 entities, that is Persons, Families, and Corporate Bodies: how these entities relate to a resource (Works, Expressions, Manifestations, Items). Relationships between entities in Group 1: Works, Expressions, Manifestations, Items: how these entities relate to each other And relationships between Group 2 entities: Persons, Families, and Corporate Bodies: how these entities relate to each other

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 We learned in the Toolkit module that RDA instructions are divided into two main groups: those about identifying entities and those about making relationships. And there are appendices for abbreviation and capitalization, for mapping to ISBD and MARC, as well as appendices for relationship designators. We will cover the chapters about making relationships and appendices for relationship designators today. Here are the chapters about making relationships corresponding to the three sets of relationships we will focus on in this module. Note: Chapter 23 General guidelines on recording the subject of a work has not been written yet. Relationship designators are terms used to describe relationships among resources, persons, families, and corporate bodies. The terms describe relationships between entities represented by authorized access points, descriptions, and/or identifiers. These terms are variously used as part of authorized access points or are reflected in MARC 21 coding. Appendix I: Relationship designators between Group 1 and Group 2 entities: Relationships Between A Resource And Persons, Families, And Corporate Bodies Associated With The Resource. For example the designator “author” expresses the relationship between the creator of a primarily textual work and the work itself. Note: used primariliy in bibliographic records, but may also be used in authority records. Appendix J: Relationship Designators: Relationships Between Works, Expressions, Manifestations, And Items. For example the designator “adaption” may be used to express a relations ship from a work “based on” a work and the original work. Note: used in both bibliographic and authority records (formerly known as “see also” references). Appendix K: Relationship Designators: Relationships Between Persons, Families, And Corporate Bodies. For example the designator “alternate identity” relates a pseudonymous or other identity assumed by a person to the person. The designator “real identity” relates the real person to an assumed alternate identity. Note: used only in name authority records (formerly known as “see also” references).

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 The RDA relationship designators are in three appendices for different categories of relationships. They are not closed lists. If a term is missing for the relationship you want to give, RDA says to use another term. The term can be taken from some other list of controlled terms, or it could be devised by the cataloger. PCC encourages its catalogers to make proposals to add needed new terms to RDA. In most situations, apply cataloger judgment about giving a relationship designator. LC policy for specific relationships is given in this module and in LC-PCC PSs. The decision to include relationships other than those identified as core elements will be cataloger’s judgment. You will want to investigate what other relationships are possible in the various RDA chapters cited in this module, and decide which relationships you think are important to help users find the specific resource or entity you’re identifying. 9

[Screen image from the RDA Toolkit (www. rdatoolkit [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)] Example from Appendix I: Appendix I lists the “relationship designators” or roles played by the persons, families, and corporate bodies associated with Works, Expressions, Manifestations, and Items. The list of terms for relationship designators in RDA can be used at a general level or a specific level, depending on the application. For example, using chapter 19, we could just identify a “creator” of a work, or, we could use Appendix I for a more specific relationship type for that creator – such as an artist, a composer, an author, and so on. In the MARC format we can add a subfield $e for the relator term to an authorized access point for a person, family, or corporate body to show this. We will look at specific examples in the next unit. 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 Digital fortress. There are four methods in RDA for expressing relationships and partly depends on the category of relationship being expressed. The use of an identifier alone is not permitted in LC or PCC cataloging. The relationship between creator to a work is being expressed in the first two examples. A structured description is a formatted type note such as a linking field in this example of an equivalent manifestation relationship shown with the 776 field. Another example of a structured description could also be a note with ISBD punctuation. These three methods of expressing relationships are reflected in summary coding tables in your hand out. For example looking at page 8 in your manual for relationships given with authorized access point. On page 16 methods of coding relationships between resources are given.

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 Providing the relationship in the authorized access point, use $e designator in 100-110 and 700-710 entry fields to show relationships between people and resources. For 111 and 711 use $j for relationship designator because $e is defined as subordinate unit for conferences. Providing relationships between resources $i of 76X-78X linking entry fields to show relationships between resources. $e/$j - Relator term Designation of function that describes the relationship between a name and a work, e.g. author, editor, editor of compilation, illustrator, translator, collector. $i – 700-730 give a term phrase such as “translation of” from appendix J preceding the authorized access point for a name title. $i - Relationship information Designation of a relationship between the resource described in the 76X-78X field and the resource described in the 1XX/245 of the record. This may be in the form of uncontrolled text or a controlled text value. The second indicator contains value 8 (No display constant generated) except in fields 780 and 785 when data in this subfield is intended to be displayed. The data in subfield $i can be displayed preceding the other data contained in the field. 76X-78X - Linking Entries-General Information Second Indicator - Type of relationship Identifies the type of relationship…. See the description under the section for field … For that field, the display constants are specified in Input Conventions. PCC Guidelines: “Relationships should be coded explicitly and not inferred from MARC or other parts of the record.” PCC Guidelines: Guideline 14. If a cataloger wishes to indicate a known relationship to a known resource, and the $i relationship information subfield is defined for the MARC 7XX field being used, provide a relationship designator. Do so even if the field coding otherwise already expresses a relationship.

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 Guidelines for citing another resource In MARC 700-730 fields Give the form represented by an existing NAR* If there is no NAR, give the RDA form (follow DCM Z1 guidelines about when to make an NAR) *Exception: Do not use AACR2 NAR having “Polyglot” or more than one language in subfield $l for multiple expressions. There is more information about this exception for expressions at the end of the PCC-Post-RDA-Test guidelines (at http://www.loc.gov/catdir/pcc/PCC-Post-RDA-Test.html). In MARC 760-787 fields Copy paste what is in the existing record for that resource and adjust the subfield coding as appropriate * Exception: Do not use AACR2 NAR with “Polyglot” or more than one language in subfield $l for multiple expressions.

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 Guidelines for citing another resource In MARC 700-730 fields Give the form represented by an existing NAR* If there is no NAR, give the RDA form (follow DCM Z1 guidelines about when to make an NAR) *Exception: Do not use AACR2 NAR having “Polyglot” or more than one language in subfield $l for multiple expressions. There is more information about this exception for expressions at the end of the PCC-Post-RDA-Test guidelines (at http://www.loc.gov/catdir/pcc/PCC-Post-RDA-Test.html). In MARC 760-787 fields Copy paste what is in the existing record for that resource and adjust the subfield coding as appropriate

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) Subfield e is never used in authority records. More on the coding of optional relationships at the end of the module $w - Control subfield Up to four character positions (designated as $w/0, etc.) that indicate whether special instructions apply to the display of the heading in the 4XX or 5XX field and whether a tracing is restricted to the reference structure of a particular type of authority. Subfield $w need not be used if none of the characteristics is applicable. Because the definitions of the codes in subfield $w are dependent on the character position in which they occur, the coding of any character position mandates that each preceding character position contains a code or a fill character (|); succeeding character positions need not be used. For example, if $w/0 and $w/1 are not applicable but $w/2 is applicable, then $w/0 and $w/1 each contain code n (Not applicable) or a fill character (|).

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

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) In FRBR terms, Relationships between persons/families/bodies and resources are known as: Relationships expressed in bibliographic records: Relationships between Group 1 and Group 2 entities The slide displays the four chapters corresponding to the relationships Group 2 entities (persons, families, corporate bodies) can have with bibliographic resources Persons, families, and corporate bodies related to a resource -- relationships in bibliographic records Creators and others associated with works (ch. 19) - Contributors associated with expressions (ch. 20) Entities related to manifestations (ch. 21) Entities related to items (ch. 22) 17

Creator relationships Persons/families/bodies related to works author compiler filmmaker interviewer programmer and others … (RDA Appendix I) The creator relationship is expressed in the 1XX field for the single or first creator with other creators given in 7XX fields. Relationship designators may be used in subfield $e of those 1XX and 7XX fields. The list in appendix I.2 is not closed; if you need another term, you can choose an appropriate term. If there is more than one creator of a work, you may provide additional creators in the 7XX fields. If you create authority records, do not include that term in the 1XX of the authority record.

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.2 If there is more than one creator responsible for the work, only the creator having principal responsibility named first in resources embodying the work or in reference sources is required. If principal responsibility is not indicated, only the first-named creator is required. LC practice/PCC practice for Core element when there is more than one creator: After satisfying the RDA core requirement, catalogers may provide additional authorized access points according to cataloger’s judgment.

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 The creator relationship is expressed in the 1XX field for the single or first creator with other creators given in 7XX fields. Relationship designators may be used in subfield $e of those 1XX and 7XX fields. The list in appendix I.2 is not closed; if you need another term, you can choose an appropriate term. If you create authority records, do not include that $e term in the 1XX of the authority record. PCC Guidelines: Include a relationship designator for all creators, whether they are coded MARC 1XX or MARC 7XX. If the MARC 1XX is not a creator, the addition of a relationship designator is optional though strongly encouraged.  Add a relationship designator even if the MARC field definition already implies a relationship. Relationships should be coded explicitly and not inferred from MARC or other parts of the record.

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. Shown here are examples of creators with the appropriate relationship designators. Two creators are shown with the 110 and the 710 If a creator is part of the authorized access point for the work, a relationship designator from appendix I can be given with the creator in the 1XX of the bibliographic record to show the type of relationship between the creator and the work. If there is more than one creator, the appropriate relationship designator can be given in the 7XX fields. The other examples show use of other creator relationship designators from appendix I 110 1_ $a Israel, $e enacting jurisdiction.

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. There are other roles than creator associated with works; those relationships are covered in RDA 19.3. “Other person, family or corporate body associated with a work” Examples of common types in the slide. 700 1_ $a Fox, Eytan, $d 1964- $e film director. 700 1_ $a Chazan, Robert, $e honouree. 22 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

Contributor relationships Persons/families/bodies related to expressions Translators Editors of compilations Performers Illustrators Arrangers of music Compilers Relationships to expressions: Contributors are those persons, families, or corporate bodies that are associated with expressions. Types of relationships for contributors at the expression level include editors of compilations, translators, performers, illustrators, arrangers of music, compilers, writers of added commentary, and so on. Contributor (RDA 20.2): 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 LC-PCC PS for 20.2. CORE ELEMENT FOR LC LC practice: Contributor is a core element for LC only for illustrators of resources intended for children. If multiple illustrators are present, apply cataloger judgment to give more than the first. PCC practice: Record contributors if they are considered important for identification.

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 In the MARC format, we code the related entities as authorized access points in MARC 7XX fields in the bibliographic record. Notice that you would not normally include these relationship designators in authority records, as they apply to the resource you are cataloging in the bib record. You will want to apply library policy or cataloger’s judgment to use the relationship designator for any contributor you add to a bibliographic 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 This is an example of the one required expression level relationship for LC catalogers. This example shows the contributor, Don Wood, with subfield $e to represent the relationship to the expression that is embodied in this manifestation that we are describing. That access point doesn’t need to be justified by including the 2nd statement of responsibility (illustrated by Don Wood) as shown in the example. In fact that second statement of responsibility is not “core” in RDA, so can be omitted, while still keeping the 700 field. 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. This slide and the following examples show relationships that may be important for certain types of materials. Here’s an example for a translator. The decision about whether or not to include the relationship designators in subfield $e of the 100 and 700 fields is cataloger’s judgment. PCC guidelines highly encourage it whenever the nature of the relationship is clear. 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.* This slide shows an example with two contributors to the expression. Whether to include the 7XX fields at all is either library policy or cataloger judgment; the same is true for including the relationship designators in the 7XX fields. PCC guidelines highly encourage relationship designators for all access points whenever the nature of the relationship is clear. * Could have used the more general “$e performer” for Alsop.

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 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 Relationships at the manifestation level apply to those roles that can change from one manifestation to the other. Chapter 21 lists Producers, publishers, manufactures, distributors as types of relationships. These are separate elements in RDA and already in your record. 31

Relatively few terms are listed in Appendix I.4 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: Guideline 4 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. Note: This departure from RDA is necessary in our current MARC environment to express the relationship because not all RDA elements have dedicated MARC fields. However, do not propose RDA element names for inclusion in RDA relationship designator lists.

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 2011- 710 2# $a West Publishing Company, $e publisher. Here are two examples of relationships to manifestations. Broadcaster is a type of publisher, the term comes from the appendix for manifestation relationships. The 264 #1 indicates “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.”

Relationships to items Persons/families/bodies related to items (RDA 22.0, Appendix I.5) Owners Custodians Curators Binders Inscribers Cataloger judgment Here are a few of the possible relationships to items: remember that this has to be a relationship to only one instance of the manifestation (for example, one copy of a book but not all copies of the book). 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. These examples show relationships that apply to only one instance of a manifestation. So, these relationships apply generally at the local level only. Do you have any questions about relationships of persons, families, corporate bodies to works, expressions, manifestations, items?

Summary Works: Expression: Manifestations: Cataloger judgment 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 Review For relationships between persons/families/corporate bodies and resoruces

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) Now let’s look at relationships between works, expressions, manifestations and items. Each Group 1 entity is addressed in a separate relationships chapter: ch. 25-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) Chapter 25 of RDA addresses the relationship between a work and other works: whole-part relationships, derivative relationships like adaptations, parodies, accompanying relationships like supplements, and sequential relationships like earlier/later serials, etc. See details in LC-PCC PS 25.1 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 LC-PCC PS for 25.1. Related Work CORE ELEMENT FOR LC LC practice: Related work is a core element for LC for compilations: give a MARC 505 contents note unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). There is no limit on the number of works in the contents note unless burdensome. For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Disregard contributions such as a preface or introductory chapter. Generally, do not apply this core element to anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, and similar resources. Related work is also a core element for serial relationships such as “Continues,” “Continued by,” etc.; generally, give these as reciprocal relationships. If RDA 6.27.1.6 is being applied to identify the work as a commentary, include in the bibliographic record an authorized access point for the original resource as a related work. PCC practice: Give complete contents in a MARC 505 contents note unless considered burdensome or unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Optionally, give analytical authorized access points for works other than the predominant or first work, if considered important for access. Disregard contributions such as a preface or introductory chapter. Generally, it is not necessary to give contents notes for anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, chapters of mutlivolume monographs cataloged as monographic sets and similar resources.

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 This slide describes LC and PCC policy on providing whole-part relationships for compilations. LC-PCC PS for 25.1. Related Work CORE ELEMENT FOR LC LC practice: Related work is a core element for LC for compilations: give a MARC 505 contents note unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). There is no limit on the number of works in the contents note unless burdensome. For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Disregard contributions such as a preface or introductory chapter. Generally, do not apply this core element to anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, and similar resources. Related work is also a core element for serial relationships such as “Continues,” “Continued by,” etc.; generally, give these as reciprocal relationships. If RDA 6.27.1.6 is being applied to identify the work as a commentary, include in the bibliographic record an authorized access point for the original resource as a related work. PCC practice: Give complete contents in a MARC 505 contents note unless considered burdensome or unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Optionally, give analytical authorized access points for works other than the predominant or first work, if considered important for access. Disregard contributions such as a preface or introductory chapter. Generally, it is not necessary to give contents notes for anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, chapters of mutlivolume monographs cataloged as monographic sets and similar resources. There are three RDA possibilities for expressing the relationship between works: an identifier (not used by itself), an authorized access point, and either a structured or unstructured description. 40

Example: Whole-part work Authorized access points for the works: 100 1# $a Shakespeare, William, $d 1564- 1616. 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. In this example authorized access points are used to represent the relationship between the parts to the whole. Because the second indicator identifies the relationship (the 2 = analytical entry), a relationship designator from appendix J wouldn’t be necessary in the 700 fields. * 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 In this example of a title change of a serial, a structured description also containing three identifiers is used to show the relationship between the earlier and later serial. However, the PCC guidelines say not to rely just on the MARC coding and to give relationship designators in linking fields that have $i defined. 785 indicators 00 = relationship “Continued by” 780 indicators 00 = relationship “Continues” 42

Authority record, work relationship 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) Cataloger’s judgment, not an LC core requirement, but other institutions are creating such authority records. Here is an example of using a relationship designator for a work to work relationship, the term is from Appendix J. The play is a work and the term used shows its relationship to the motion picture. Notice also the 046 subfield $k the date of the creation of the work and the 380 added to show the form of the work. A reciprocal work record for the motion picture also exists. 530 See also would appear on reciprocal records. $w is a control field, r indicates that a relationship designator is being given in $i

Related expressions RDA 26.1 Common expression relationships: Whole-part (e.g., translations in a compilation) Revisions Editions Translations Language editions Abridgements Chapter 26 addresses the relationship between an expression and other expressions, which includes whole/part relationships and derivative relationships, such as revisions, editions, translations, and 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

Example 1: Whole-part expression Authorized access points for the expressions: 100 1# $a Petterson, Per, $d 1952- 245 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. 740 02 $a To Siberia. Give an analytical authorized access point for the predominant or first expression in the compilation when it represents a substantial part of a resource (e.g., usually not the preface or introduction) In this example authorized access points are used to represent the relationship between the parts to the whole. The second indicator of “2” in the 700 fields identifies the relationship (as being an analytical entry). Example 1) The work Two Norwegian novels is a compilation of two separate English language expressions of two separate works 2) The first 700 12 meets the core LC requirement for giving expressions in the compilation, the second is optional but very helpful (best advice: provide both to help user) 3) the 740's are optional but very helpful LC-PCC PS for 26.1 CORE ELEMENT FOR LC/PCC Related expression is a core element for LC and PCC for compilations: give a MARC 505 contents note unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). There is no limit on the number of expressions in the contents note unless burdensome. When the original expression and one translation are in a compilation, give an analytical authorized access point for each expression. If the compilation contains the original expression and more than one translation, give analytical authorized access points for the original expression and at least one translation. Follow the same policy for language editions in a compilation. See Policy Statement 6.27.3. For other compilations of expressions, give an analytical authorized access point for the predominant or first expression in the compilation when it represents a substantial part of the resource. Disregard contributions such as a preface or introductory chapter. Generally, do not apply this core element to anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, and similar resources. Related expression is also a core element for serial relationships such as “Continues,” “Continued by,” etc.; generally, give these as reciprocal relationships. 46

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. Language editions are related expressions. In this example of a serial, an structured description in field 775 is used to give the relationship. The reciprocal relationship would be given in the bibliographic record for the Spanish edition. 47

Example 3: Related expression - translation Authorized access point: 100 1# $a Brown, Dan, $d 1964- 240 10 $a Digital fortress. $l French 245 10 $a Forteresse digitale. 700 1# $i Translation of: $a Brown, Dan, $d 1964- $t Digital fortress. The expression-level relationship for a translation is not required in RDA. But this slide and those following are included to illustrate the range of possibilities available when including other relationships. The authorized access point shows the relationship between the translation being cataloged and the original; the relationship designator from appendix J is in subfield $i (translation of). 48

Example 4: Related expression - translation Structured description in 500 field: 100 1# $a Brown, Dan, $d 1964- 240 10 $a Digital fortress. $l French 245 10 $a Forteresse digitale / $c Dan Brown. 500 ## $a Translation of: Digital fortress / Dan Brown. -- 1st ed. -- New York : St. Martin’s Press, 1998. -- 371 pages ; 22 cm. This example illustrates the use of a structured description using a note; the 500 field begins with the appendix J relationship designator and then contains the elements of a description in an ISBD display format with each element separated by ISBD punctuation. 49

Example 5: Related expression - translation Structured description in 765 field: 100 1# $a Brown, Dan, $d 1964- 240 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 The same descriptive information on the previous slide could be given with subfield coding in a 765 field. Although the 2nd indicator value of blank could identify the relationship (blank = “translation of”), PCC policy is to give a relationship designator in subfield $i in linking fields that have subfield $i defined. * 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 1964- 240 10 $a Digital fortress. $l French 245 10 $a Forteresse digitale / $c Dan Brown. 500 ## $a Translation of the author’s novel Digital fortress. The last possible method for giving the relationship is an unstructured description in a simple 500 note that has not been structured with specific tagging. 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. Chapter 27 addresses the relationship between a manifestation and other manifestations: reproductions, different formats, special issues, inserts, etc. LC-PCC PS 27.1 CORE ELEMENT FOR LC/PCC Related manifestation is a core element for LC and PCC for reproductions. The word “reproduction” is being used in its broadest sense to include all resources formerly identified as reproductions, republications, reprints, reissues, facsimiles, etc., that still represent equivalent content between an original resource and a reproduction of that original. Revised editions represent different expressions and are not treated as 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 the original (no need to upgrade) Here again we can use an identifier and/or a structured or unstructured description to show the relationship. But notice that an authorized access point is not one of the methods available to give relationships to other manifestations. This is something that could change in the future. You should apply cataloger’s judgment about including other manifestation relationships in bibliographic records and using relationship designators that are found in Appendix J.4 of RDA. In case the question of Provider Neutral and terms “reproduction of (manifestation)” come up: LC-PCC PS 27.1.1.3 Note: The PCC is in the process of forming a task group to address issues related to reproductions. LC practice/PCC practice: When the decision has been made to create a separate record for the reproduction, generally follow the guidelines below for giving MARC 775 and MARC 776 fields. The guidelines do not apply when the “single-record” or “provider neutral” technique is being used. Relationship to the original: on the record for the reproduction, use a structured description to give the attributes of the original. 1. MARC field: a) Carrier of reproduction is the same as the carrier of the original: use MARC field 775. b) Carrier of reproduction is not the same as the carrier of the original: use MARC field 776. 2. Use the relationship designator “Reproduction of (manifestation)” unless a particular PCC program (e.g., CONSER) recommends the use of other relationship information. 53

Examples of recording manifestation relationships from LC-PCC PS 27. 1

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 Here again we can use an identifier and/or a structured or unstructured description to show the relationship. But notice that an authorized access point is not one of the methods available to give relationships to other manifestations. This is something that could change in the future. You should apply cataloger’s judgment about including other manifestation relationships in bibliographic records and using relationship designators that are found in Appendix J.4 of RDA. In case the question of Provider Neutral and terms “reproduction of (manifestation)” come up: LC-PCC PS 27.1.1.3 Note: The PCC is in the process of forming a task group to address issues related to reproductions. LC practice/PCC practice: When the decision has been made to create a separate record for the reproduction, generally follow the guidelines below for giving MARC 775 and MARC 776 fields. The guidelines do not apply when the “single-record” or “provider neutral” technique is being used. Relationship to the original: on the record for the reproduction, use a structured description to give the attributes of the original. 1. MARC field: a) Carrier of reproduction is the same as the carrier of the original: use MARC field 775. b) Carrier of reproduction is not the same as the carrier of the original: use MARC field 776. 2. Use the relationship designator “Reproduction of (manifestation)” unless a particular PCC program (e.g., CONSER) recommends the use of other relationship information. 55

OCLC record for microfilm reproduction of a serial, showing structured relationship in field 776 to the related manifestation.

OCLC record for the original print serial showing reciprocal link to the reproduction.

Example: Related manifestations 245 00 $a Health statistics for elementary -school children. 264 #1 $a Baltimore : $b Johns Hopkins University, $c 2009- 300 ## $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. This example of a related manifestation is the same expression in a different format. The printed text is being cataloged but there is also a CD-ROM version.

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 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 to the user. If the reproduction is a facsimile of a manuscript and attributes of the original for use in a MARC 775/776 linking field are not readily ascertainable, give a bibliographic history note with the information you have.

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 Chapter 28 addresses the relationship between an item and other items, such as reproductions of a specific copy of a manifestation, bound withs, items added to an individual copy of a manifestation in a special collection, etc. 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” LC-PCC PS 28.1 Related Item CORE ELEMENT FOR LC Related item is a core element for LC for reproductions when it is important to identify the specific item that was reproduced (see Policy Statement 27.1 for general situations where relating manifestations is adequate), special relationships for rare materials if warranted, and “bound withs.” Follow LC’s local policies for “bound withs” in Policy Statement 28.1.1.3 and in local holdings and item records guidelines.

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 Chapter 28 addresses the relationship between an item and other items, such as reproductions of a specific copy of a manifestation, bound withs, items added to an individual copy of a manifestation in a special collection, etc. As we noticed for manifestations, an authorized access point is not one of the methods available to give relationships to other items. You can apply cataloger’s judgment about including other item relationships in bibliographic records and using relationship designators. LC-PCC PS for 28.1.1.3 Relationship to the original: on the record for the reproduction, use a structured description to give the attributes of the original. 1. MARC field: a) Carrier of reproduction is the same as the carrier of original: use MARC field 775. b) Carrier of reproduction is not the same as the carrier of original: use MARC field 776. 2. Use the relationship designator “Reproduction of (item)” 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 Here are two examples of relationships for related items. A “bound with” situation applies only in a local library; it is not the “issued with” relationship that would apply to all items of a manifestation. Some reproductions are relationships at the manifestation level and some are at the item level as shown in the slide. A local library has made a copy of an item in its collection, perhaps for preservation purposes. The LC-PCC PS for 27.1.1.3 has detailed instructions for notes for items bound tgether. 775 $i Reproduction of (item): $t Hiking in Unicoi State Park $d Helen, GA : RST Publishers, 1955 $h 22 p. : ill. ; 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) The relationships within Group 2 (families, persons, and corporate bodies) exist only in authority records. You may not be creating authority records but you need to understand the relationships you see in authority records you’re using. 64

Relationships between persons, families, and corporate bodies LC/PCC core relationships: Different identities for persons (LC-PCC PS 30.1) Immediately preceding/succeeding corporate bodies (LC-PCC PS 32.1) LC’s core relationships for Group 2 entities are different identities for persons and immediately preceding/succeeding corporate bodies. Do not give relationships between earlier and later conferences, exhibitions, etc. LC-PCC PS 30.1 CORE ELEMENT FOR LC/PCC Related person is a core element for LC/PCC for different identities. LC-PCC PS 32.1 Related corporate body is a core element for LC and PCC for sequential relationships with immediately preceding and immediately succeeding corporate bodies. See Policy Statement 11.13.1.8.1-11.13.1.8.2 for guidelines on making sequential relationships for ongoing conferences. 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 Relationships between Group 2 entities are given in 5XX fields in authority records. LC-PCC PS 30.1.1.3 LC practice/PCC practice: When creating name authority records for a person with different identities, follow the guidelines in the Descriptive Cataloging Manual Z1 sections for MARC fields 663 and 667. More information is available in the FAQ on personal names (http://www.loc.gov/catdir/cpso/pseud.pdf). 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 The LC policy for different identities is stated here with three related name authority records on this and the next slide. 663 is “Complex see also” field, refer to DCM Z1

Example: 2 identities RDA would allow coding as: 100 1# $a King, Stephen, $d 1947- 500 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 1947- 500 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 The LC policy for different identities is stated here with three related name authority records on this and the next slide.

Examples: 3+ different identities 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 Authorized access point in authority records: 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

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 The relationship shown here between the two corporate bodies is indicated here by the codes in subfield $w: “a” for earlier name and “b” for later name. 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 The relationship shown here between the two corporate bodies is indicated here by the codes in subfield $w: “a” for earlier name and “b” for later name. 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 For other relationships, the LC policy is cataloger judgment about giving the relationship and including a relationship designator from Appendix K in subfield $i of the 5XX field. If you give a relationship designator in subfield $i, you also need to give value “r” in subfield $w. 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 Here are two examples of persons with related corporate bodies and related families. Remember these are in the authority records: in the first example, a subfield $i in the 510 field explains the relationship between the corporate body and the person (it’s the employer) the second example shows a related family in the 500 field. 73

Module 4: Relationships 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 Remember that “relate” is one of the main user tasks in RDA – coming from FRAD. We can show the relationships between and among Group 1 and 2 entities. RDA provides terms to use for the relationship designators in Appendices I, J, and K, and those lists of terms are NOT closed lists. Are there any questions about the relationships included in this module? 74

Module 4: Relationships in RDA Questions? If there is time remind them: Detailed information on LC core elements and coding are given in Documents R-1 pages 8-9, R-5. Module 2, Appendix 1 which you received contains information about relationships. There are specialized modules dealing specifically with relationships available here: RDA Refresher Training at LC: Special Topics http://www.loc.gov/aba/rda/Refresher_training_dec_2011.html Topics: Compilations [PPT, 1.85 MB]  RDA Elements in NARs [PPT, 2.5 MB]  Relationship Designators in RDA NARs [PPT, 999 KB]  Revised editions [PPT, 507 KB]  75