Jumping into RDA Texas Library Association 2013 Annual Conference

Jumping into RDA Texas Library Association 2013 Annual Conference Wednesday, April 24, 2013 8:00 AM 4:00 PM

Assumptions You have heard of RDA (as a new resource) You might not ever have encountered an RDA bibliographic or authority record You know a little about the MARC 21 Bibliographic and Authority Formats You are interested in learning more You are flexible and can tolerate ambiguity 2

Assumptions You know there is a lot of RDA training material already freely available we can look at it later We have less than seven hours today -- that is a good thing You can name the movie with the line But you are, Blanche, you are So 3

Overview After an RDA and FRBR introduction, we will look at ten big areas: 1. TRANSCRIPTION 2. Title + Statement of Responsibility (MARC 21 245 field) 3. Production, etc. (MARC 21 264 field) 4

Overview 4. General Materials Designator (MARC 21 245 subfield $h) 5. Extent (MARC 21 300 field) 6. Works (FRBR concept) 7. Compilations and Collaborations 8. Expressions (FRBR concept) 9. Relationships (FRBR concept) 10. Authorities 5

Why RDA? Why don t we just revise AACR2? Evolving cataloging environment RDA an improvement over AACR2 6

The Cataloging Environment -- Internet Catalogs are no longer in isolation Global access to data linked data systems Integrate bibliographic data with wider Internet environment Share data beyond institutions Any user any place any time 7

The Cataloging Environment Databases, Repositories LCSH VIAF Web front end Services 8

The Cataloging Environment -- Web-based Current Wide range of information carriers More types of content and complexity of content Metadata (bibliographic information) Created by a wider range of personnel in and outside libraries Element-based metadata schemas Dublin Core, ONIX, etc. 9

The Problems with AACR2 Increasingly complex Lack of logical structure Mix of content and carrier data Hierarchical relationships are missing Anglo-American centric Pre-dates FRBR Not enough support for collocation Did not foresee Internet and well-formed metadata or vocabularies 10

A Tool for the Digital World Optimized for use as an online product RDA Toolkit Description and access of all resources All types of content and media Resulting records usable in the digital environment (Internet, Web OPACs, etc.) Resulting records readily adaptable to newly emerging database structures 11

RDA Specific Goals Easy to use and interpret Applicable to an online, networked environment Provide effective bibliographic control for all types of media Encourage use beyond library community Compatible with other similar standards Have a logical structure based on internationally agreed-upon principles Separate content and carrier data, and separate content from display Examples numerous and appropriate 12

FRBR as a Foundation of RDA Functional Requirements for Bibliographic Records (FRBR; 1998) Functional Requirements for Authority Data (FRAD; 2009) Statement of International Cataloguing Principles (ICP; 2009) 13

FRBR/FRAD Refresher Relationships Work is realized through Inherent Group 1 Relationships Expression is embodied in Manifestation is exemplified by Item 14

FRBR/FRAD Refresher Relationships Work Expression Relationships Between Groups 1 and 2 Manifestation Item is owned by is produced by is realized by is created by Person Family Corporate Body 15

FRBR and RDA FRBR offers a structure to address user tasks FRBR entities and elements translate into RDA data elements RDA combines FRBR conceptual model with cataloging principles Foundations for: cataloger judgment better systems for the future FRBR not a cataloging code -- but shows how users can benefit from a system based on FRBR entities and relationships 16

Family of Works Equivalent Microform Reproduction Facsimile Reprint Copy Exact Reproduction Simultaneous Publication Translation Variations or Versions Edition Revision Illustrated Edition Derivative Abridged Edition Expurgated Edition Arrangement Slight Modification Summary Abstract Digest Change of Genre Adaptation Free Translation Dramatization Novelization Screenplay Libretto Parody Imitation Same Style or Thematic Content Descriptive Review Criticism Annotated Edition Casebook Evaluation Commentary Original Work - Same Expression Same Work New Expression Cataloging Rules Cut-Off Point New Work

How FRBR/RDA is Already Evident in LC ILS Shakespeare, William, 1564-1616. Hamlet. French. LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title :... Hamlet, traduit par Andre Gide. Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm. CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or Area Studies Reading Rms

Person Shakespeare, William, 1564-1616. Hamlet. French. Work LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title :... Hamlet, traduit par Andre Gide. Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm. CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or Area Studies Reading Rms

Shakespeare, William, 1564-1616. Hamlet. French. LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title :... Hamlet, traduit par Andre Gide. Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm. Expression CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or Area Studies Reading Rms 20

Shakespeare, William, 1564-1616. Hamlet. French. Manifestation LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title :... Hamlet, traduit par Andre Gide. Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm. CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or Area Studies Reading Rms 21

Shakespeare, William, 1564-1616. Hamlet. French. LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title :... Hamlet, traduit par Andre Gide. Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm. CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or Area Studies Reading Rms Item 22

What am I Cataloging? 23

You see, FRBR is not so very different from what we do now! But what about RDA? And what about CORE elements? And LC CORE? And PCC CORE? And PCC Policies and Best practices? 24

1. TRANSCRIPTION Where it all started

Transcription: Take What You See and Accept What You Get ICP Principle of Representation Generally, do not alter what is on the resource Accurate representation Encourage re-use of found data 26

Transcription: Take What You See and Accept What You Get What does this mean for you? Alternatives at RDA 1.7.1 allow for in-house guidelines for capitalization, punctuation, numerals, symbols, abbreviations, etc. (in lieu of RDA instructions) LC-PCC PS 1.7.1 General guidelines on transcription LC policy generally adheres to Take What You See and Accept What You Get. 27

Transcription: Capitalization RDA 1.7.2 Apply the instructions on capitalization found in Appendix A. LC-PCC PS 1.7.1 First Alternative For capitalization of transcribed elements, either take what you see on the resource or follow [Appendix] A. Your choice! 28

Transcription: Capitalization Accepting found capitalization: 245 10 $a Cairo : $b THE CITY VICTORIOUS / $c Max Rodenbeck. 250 ## $a FIRST VINTAGE DEPARTURES EDITION. Changing found capitalization: 245 10 $a Cairo : $b the city victorious / $c Max Rodenbeck. 250 ## $a First Vintage Departures edition. These are equally acceptable! 29

2. Title MARC 21 Field 245 Title (RDA 2.3) Statement of Responsibility (RDA 2.4)

CORE ELEMENT RDA 2.3.2 Title Proper Scope = the chief name of a resource (i.e., the title normally used when citing the resource) = the title on what s being cataloged Sources: Preferred source of information: 2.2.2-2.2.3 If no title within the resource: 2.2.4 MARC 245 $a $n $p 31

Title Proper Transcription General guidelines on titles (RDA 2.3.1) Principle of representation (RDA 2.3.1.4) Don t correct errors for monographs no more [sic] or [i.e., ] give note to explain Do correct errors for serials and integrating resources to have a stable title Changes in title proper (RDA 2.3.2.12-2.3.2.13) same as AACR2 32

Examples: Error in Title Proper AACR2 record for a monograph: 245 $a Teusday s [i.e. Tuesday s] tasks RDA record for this monograph: 245 $a Teusday s tasks 246 $i Corrected title: $a Tuesday s tasks RDA record for a serial: 245 $a Zoology studies 246 $i Misspelled title on number 1: $a Zooology studies 33

Statement of Responsibility Relating to Title Proper - Scope CORE ELEMENT if it relates to title proper RDA 2.4.1 Scope = a statement associated with the title proper of a resource that relates to the identification and/or function of any persons, families, or corporate bodies responsible for the creation of, or contributing to the realization of, the intellectual or artistic content of the resource MARC 245 $c 34

Statement of Responsibility Relating to Title Proper - Sources Take statements of responsibility relating to title proper from the following sources (in order of preference): a) the same source as the title proper b) another source within the resource itself c) one of the other sources of information specified under 2.2.4 Sources expanded: square brackets only if from outside the resource 35

Statement of Responsibility Relating to Title Proper - Transcription Transcribe a statement of responsibility in the form in which it appears on the source of information (follow general guideline in RDA 1.7) LC-PCC PS: Generally do not abridge a statement of responsibility. Source: Dr. Logan Carroll, Harvard Medical School RDA/LC-PCC PS: 245 / $c Dr. Logan Carroll, Harvard Medical School. RDA allows: 245 / $c Dr. Logan Carroll. 36

Statement of Responsibility Relating to Title Proper - Transcription LC-PCC PS: Generally do not omit names in a statement of responsibility. Rule of Three -- Change from AACR2! Source: by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson. RDA allows: 245 $a / $c by Susan Brown [and four others]. RDA/LC-PCC PS: 245 $a / $c by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson. AACR2: 245 $a / $c by Susan Brown [et al.]. 37

If Multiple Statements... Only the first recorded is required If you record more than the first Record them in the order indicated by the sequence, layout, or typography of the source of information (RDA 2.4.1.6) If not giving all statements of responsibility, give preference to those that identify creators of intellectual or artistic content (RDA 2.4.2.3) On source: introduction by written by If only transcribing one in 245 $c, give written by 38

3. Production, Publication, Distribution, Manufacture, and Copyright Notice, or, What Happened to the MARC 21 260 Field? Production Statement (RDA 2.7) Publication Statement (RDA 2.8) Distribution Statement (RDA 2.9) Manufacture Statement (RDA 2.10) Copyright Date (RDA 2.11)

What MARC 21 Field Replaces the 260 field? 40

Production Statement Date of production is an LC CORE ELEMENT for resource in unpublished form RDA 2.7 Scope a statement identifying the place or places of production, producer or producers, and date or dates of production of a resource in an unpublished form 41

Publication Statement CORE ELEMENT for published resources RDA 2.8 Scope a statement identifying the place or places of publication, publisher or publishers, and date or dates of publication of a resource MARC field 264, second indicator 1 42

Place of Publication CORE ELEMENT: if more than one, only the first recorded is required RDA 2.8.2 Transcribe places of publication in the form in which they appear on the source Include both local place name and name of the larger jurisdiction if present Option to add a larger jurisdiction if not already on the resource cataloger judgment 43

More Than One Place of Publication If more than one, only the first recorded is required No home country provision No need to look for a place in the U.S. 44

Place of Publication in More Than One Language If the place of publication appears in more than one language or script, record the form that is in the language or script of the title proper 45

Place of Publication Not Identified Supply the place of publication or a probable place of publication whenever possible for benefit of users and catalogers, if the place of publication is not identified LC-PCC PS 2.8.2.6 instructs catalogers to supply a place of publication if possible, rather than record [Place of publication not identified] 46

Examples: Supplying Place Known local place: Probable local place: [Toronto] [Munich?] Known country, state, etc.: [Canada] Probable country, state, etc.: [Spain?] 47

Place of Publication: RDA Changes Only first place of publication is core [S.l.] is no longer permitted Do not correct fictitious or incorrect information; make a note to explain 48

Examples: Place of Publication On resource: London -- New York Boston 264 #1 $a London or 264 #1 $a London ; $a New York ; $a Boston 264 #1 $a Red Oak [Iowa] (addition OK, but not required) 264 #1 $a [Place of publication not identified] (Generally, no! LC-PCC PS says to supply a place if you can, even if just the country) 49

Publisher s Name CORE ELEMENT: If more than one, only the first is required RDA 2.8.4 Record the publisher's name in the form in which it appears on the source of information 50

Publisher s Name Not Identified If no publisher is identified within the resource or from other sources, record [publisher not identified] Not [s.n.] 51

Examples: Publisher s Name 264 #1 $a New York : $b J.J. Wilson Publishing Company Not: 264 #1 $b Wilson Pub. Co. Source: Humanities Association, Literature Division, Renaissance Literature Section 264 #1 $a Chicago : $b Humanities Association, Literature Division, Renaissance Literature Section Source: Toronto -- Pilkington Pub. Co. Houston -- Davidson Publishers 264 #1 $a Toronto : $b Pilkington Pub. Co. 264 #1 $b [publisher not identified] 52

Date of Publication CORE ELEMENT RDA 2.8.6 Record date as it appears on the source LC-PCC PS 1.8.2 (First Alternative), transcribe roman numerals for publication dates; do not convert to Arabic. Add dates of Gregorian or Julian calendar if it s not already on the source Record supplied date in numerals if it appears in the form of chronogram; indicate that the information was taken from a source outside the resource itself 53

Date of Publication: RDA Changes (Single Part Resource) If no publication date on resource, supply a probable date whenever possible Follow LC-PCC PS 2.8.6.6 on supplying a probable date of publication, rather than giving [date of publication not identified] 54

Examples: Supplying Dates Title page verso: Copyright 2009 Prefaced signed: June 2009 Date of publication: not given Transcription: 264 #1 $a $b $c [2009] 008/06: s 008/07-10: 2009 008/11-14: #### Title page verso: 2009 Item received in: 2008 Date of publication: not given Transcription: 264 #1 $a $b $c [2009] optionally: 264 #4 $c 2009 008/06: t 008/07-10: 2009 008/11-14: 2009 55

Examples: Supplying Dates Title page verso: 1980//1980 printing Date of publication: not given Transcription: 264 #1 $a $b $c [1980] 008/06: s 008/07-10: 1980 008/11-14: #### Title page verso: 1978//Sixth Printing 1980 Prefaced signed: June 1978 Date of publication: not given Transcription: 264 #1 $a $b $c [1978] optionally: 264 #3 $a $b $c 1980. 588 ## $a Description based on sixth printing, 1980. 008/06: s 008/07-10: 1978 008/11-14: #### 56

Examples: Supplying Dates Title page verso: Distributed 2008 Bibliography includes citations to 2007 publications Date of publication: not given Transcription: 264 #1 $a London :$b Gay Mens Press, $c [2008] optionally: also give 264 #2 $a Chicago, IL : $b Distributed in North America by InBook/LPC Group, $c 2008 008/06: s 008/07-10: 2008 008/11-14: #### Title page verso: Distributed in the USA in 1999 Prefaced signed: London, January 1993 Date of publication: not given Transcription: 264 #1 $a :$b $c [between 1993 and 1999] 008/06: q 008/07-10: 1993 008/11-14: 1999 57

Examples: Supplying Dates Title page verso: First Printing 1980 Date of publication: not given Transcription: 264 #1 $a :$b $c [1980] 008/06: s 008/07-10: 1980 008/11-14: #### Title page verso: 15th Impression 1980 Date of publication: not given Transcription: 264 #1 $a :$b $c [not after 1980] optionally: 588 ## $a Description based on 15th impression, 1980. 008/06: q 008/07-10: uuuu 008/11-14: 1980 58

Supplying Dates 5 Categories in RDA 1.9 Actual year known 264 $ c [2010] Either one of two consecutive years 264 $ c [2009 or 2010] Probable year 264 $ c [2010?] Probable range of years ( between and? ) 264 $ c [between 2008 and 2010?] Earliest and/or latest possible date known ( not before, not after, or between and ) 264 $ c [not before January 15, 2010] 59

Importance of Supplying Probable Place and Date of Publication Strongly encouraged to supply a probable place of publication and a probable date of publication when this information is not on the resource Use distribution or manufacture information to help supply place and date of publication. Distribution elements are core elements ONLY if Publication data can not be identified Give a complete distribution statement if distribution data elements are being given in lieu of missing publication data elements 60

Examples: Supplying Publication Data On source: ABC Publishers, 2009 Distributed by Iverson Company, Seattle RDA: 264 #1 $a [Place of publication not identified] : $b ABC Publishers, $c 2009. 264 #2 $a Seattle : $b Distributed by Iverson Company, $c [2009] Recommended: 264 #1 $a [Seattle?] : $b ABC Publishers, $c 2009. 61

Examples: Supplying Publication Data On source: On title page: On title page verso: Means Pub. Co., Omaha, Nebraska 2009 distribution RDA: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co., $c [date of publication not identified] 264 #2 $a [Place of distribution not identified]: $b [distributor not identified], $c 2009. Recommended: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co, $c [2009?] 62

Examples: Supplying Publication Data Sometimes, distribution information must be provided On jewel box: Published in 2010 in Providence; distributed in Boston and Ottawa by KL, Inc. RDA and LC: 264 #1 $a Providence :$b [publisher not identified], $c 2010. 264 #2 $a Boston ; $a Ottawa : $b KL, Inc., $c [2010] 63

Recording Distribution Information CORE ELEMENT only when publication information is not identified for a resource in a published form RDA 2.9 LC-PCC PS: When given in lieu of missing publication data, give a complete distribution statement Generally do not omit levels in corporate hierarchy 64

Manufacture Information (RDA 2.10) Manufacture elements are core elements for a resource in a published form only when neither publication nor distribution information can be identified Give a complete manufacture statement, if manufacture data elements are being given in lieu of missing publication and missing distribution elements Generally do not omit levels in corporate hierarchy 65

Copyright Date CORE ELEMENT if publication and distribution dates not identified for a single-part monograph Copyright dates are not required for multipart monographs, serials, and integrating resources RDA 2.11 Precede by copyright symbol ( ) or phonogram symbol ( ) MARC field 264, second indicator 4; $c is the only subfield used; no ending period. Examples: 264 #4 $c 2002 264 #4 $c 1983 66

Exercises: Identifying Manifestations 67

4. GMD R.I.P. General Materials Designation MARC 21 245 Field subfield $h Replaced with

New MARC Fields Developed with the ONIX Publishing Community Content type -- RDA 6.9 -- MARC 336 field Media type -- RDA 3.2 -- MARC 337 field Carrier type -- RDA 3.3 -- MARC 338 field 69

MARC for Content, Media, Carrier In each of the three fields for these elements (336-338): $a $b $2 $3 term code rdacontent or rdamedia or rdacarrier as appropriate materials specified - give if appropriate 70

Controlled Vocabularies for Content, Media, Carrier Types Closed lists in RDA 6.9.1.3, 3.2.1.3, 3.3.1.3 If more than one term appropriate, two choices: Give all: repeat field Pick the term representing the predominant or most substantial content, media, carrier If the information is unknown, record unspecified If no term is appropriate, record other 71

Content Type CORE ELEMENT RDA 6.9 the fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived Terms from Table 6.1 Instead of recording all, you may record the content type that applies to the predominant or most substantial parts of the resource MARC 336 field Examples: performed music still image text 72

Media Type CORE ELEMENT RDA 3.2 the general type of intermediation device required to view, play, run, etc., the content of a resource Terms from Table 3.1 Instead of recording all, may record the media type that applies to the predominant or most substantial parts of the resource MARC 337 field Examples: audio computer microform unmediated 73

Carrier Type CORE ELEMENT RDA 3.3 the format of the storage medium and housing of a carrier in combination with the type of intermediation device required Terms listed in 3.3.1.3 Instead of recording all, may record the carrier type that applies to the predominant or most substantial parts of the resource MARC 338 field Examples: audio disc computer disc microfiche volume videodisc 74

Example: MARC 336-338 Fields Book: 336 $a text $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a volume $2 rdacarrier 75

5. Extent, or, Do I Add a Period After cm?? MARC 21 Field 300 76

Extent CORE ELEMENT RDA 3.4 The number and type of units and/or subunits making up a resource Unit = a physical or logical constituent of a resource (e.g., a volume) Subunit = a physical or logical subdivision of a unit (e.g., a page of a volume) MARC 300 $a 77

Changes From AACR2 Related to Extent Do not use abbreviations for terms (e.g., pages, volumes, not p., v. ) Use approximately (rather than ca. ) and that is (rather than i.e. ) Use unnumbered, rather than square brackets enclosing the numeral Be aware of changes in vocabulary from AACR2, e.g.: computer disc is used for both computer disk and computer optical disc 78

Examples: MARC 300 $a, 336-338 Book: 300 $a 123 pages, 28 unnumbered pages 336 $a text $b txt $2 rdacontent 337 $a unmediated $b n $2 rdamedia 338 $a volume $b nc $2 rdacarrier $b is optional Music CD: 300 $a 1 audio disc {or: 1 CD} 336 $a performed music $2 rdacontent 337 $a audio $2 rdamedia 338 $a audio disc $2 rdacarrier 79

Examples: MARC 300 $a, 336-338 DVD: 300 $a 1 DVD {or: 1 videodisc} 336 $a two-dimensional moving image $2 rdacontent 337 $a video $2 rdamedia 338 $a videodisc $2 rdacarrier Online PDF: 300 $a 1 online resource (39 pages) 336 $a text $2 rdacontent 337 $a computer $2 rdamedia 338 $a online resource $2 rdacarrier 80

Example: MARC 300 $a, 336-338 Website (with maps, text, and photographs): 300 $a 1 online resource 336 $a text $2 rdacontent 336 $a cartographic image $2 rdacontent 336 $a still image $2 rdacontent 337 $a computer $2 rdamedia 338 $a online resource $2 rdacarrier Note: If copied records include repeated subfields $a, rather than multiple fields, you can accept them as is: 336 $a text $a cartographic image $a still image $2 rdacontent 81

Example: MARC 300 $a, 336-338 Book with accompanying CD of lecture: $3 and $e 300 $a 244 pages... + $e 1 CD 336 $3 book $a text $2 rdacontent 336 $3 CD $a spoken word $2 rdacontent 337 $3 book $a unmediated $2 rdamedia 337 $3 CD $a audio $2 rdamedia 338 $3 book $a volume $2 rdacarrier 338 $3 CD $ audio disc $2 rdacarrier * The use of $3 in this example is optional. Instead of $e, can repeat 300 field 300 $a 244 pages... 300 $a 1 CD... Instead of $e, can give a note 500 $a Accompanied by a CD. 82

Examples: MARC 300 $a, 336-338 Oral history CD: 300 $a 1 CD 336 $a spoken word $2 rdacontent 337 $a audio $2 rdamedia 338 $a audio disc $2 rdacarrier Playaway audiobook: 300 $a 1 Playaway (or 1 audio media player or 1 digital media player) 336 $a spoken word $2 rdacontent 337 $a audio $2 rdamedia 338 $a other $2 rdacarrier 83

Example: MARC 300 $a, 336-338 Kit (contains a book about a fireman, a CD narrating the book, and a fireman s hat): 300 $a 1 CD, 1 book, 1 plastic helmet 336 $a spoken word $a text $a threedimensional form $2 rdacontent 337 $a audio $a unmediated $2 rdamedia 338 $a audio disc $a volume $a object $2 rdacarrier * The use of multiple subfields $a in the 336 field is acceptable if this is a copied record, but for LC cataloging, you would record separate 33X fields 84

Examples: MARC 300 $a, 336-338 Score: 300 $a 1 vocal score (xii, 300 pages) 336 $a notated music $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a volume $2 rdacarrier Map: 300 $a 1 map 336 $a cartographic image $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a sheet $2 rdacarrier 85

Exercises: Carriers 86

6. Works And back to FRBR Multiple MARC 21 Fields Bibliographic Format Authority Format 87

Works: Where are the Instructions? Generally, the instructions for identifying Works and Expressions are in Chapter 6. You will also need to consult the related instructions in: Chapter 19, Persons, Families, and Corporate Bodies Associated with a Work Chapter 20, Persons, Families, and Corporate Bodies Associated with an Expression 88

Naming the Work Just like naming persons and corporate bodies (and now, families) Similar to AACR2 concept of main entry MARC has four possibilities for where this information can be coded 1XX + 240 1XX + 245 130 245 89

Decisions on Bibliographic or Authority Data? RDA does not prescribe if attributes about the work and the access points are to be recorded as bibliographic data or authority data LC Policy as a guide: Always identify the work by giving the access point in the bibliographic record Sometimes identify the work by making a title or name/title authority record -- no changes from policy in DCM Z1 90

Decisions on Core Elements to Distinguish If elements are being recorded to distinguish one work from another or from the name of a person, family, or corporate body, RDA gives choices for recording the elements (RDA 0.6.3): LC policy as a guide always give as additions to the authorized access point cataloger judgment to also give as separate elements in authority records 91

Decisions on Language and Script Title for a work in the language and script in which it appears in the resource (RDA 5.4) U.S.: in authorized and variant access points: apply the alternative to give a romanized form For some languages (see LC-PCC PS 5.4), can also give variant access points (MARC 4XX) in original language/script in authority records 92

Terminology Related to Works Title of the work (RDA 6.2.1.1) word, character, or group of words and/or characters by which a work is known Preferred title for the work (RDA 6.2.2.1) the form of title used when constructing the authorized access point Variant title for the work (RDA 6.2.3.1) the form of title used when constructing a variant access point aka see references 93

Sources of Information Sources for Preferred Titles (6.2.2.2) Commonly-known title For a work created after 1500 From resources embodying the work or from reference sources Sometimes: title proper of the first manifestation received For a work created before 1501 From modern reference sources If this evidence is inconclusive, use (in this order): a) modern editions b) early editions c) manuscript copies 94

Sources of Information Sources for Other Elements (6.1.1) For all other identifying attributes of works and expressions Take the information from any source 95

Authorized Access Points for Works (6.27.1.1-6.27.1.8) How to put together the elements to construct an authorized access point Preferred title is the basis Authorized access point for the creator precedes the preferred title, as applicable Additions to the preferred title as instructed under 6.27.1.9 Links back to the instructions on recording each of the specific elements 96

Entities Responsible for a Work RDA 0.6.3 when creating the authorized access point for the work, precede the preferred title for the work, if appropriate, by the authorized access point representing the person, family, or corporate body responsible for the intellectual or artistic content of the work 97

Entities Responsible for a Work Where are the Instructions? Creator is a relationship to a work; it isn t an attribute of the work. So we will find the instructions about creators in Chapter 19, not Chapter 6. contributors are responsible for an expression discussed in RDA Chapter 20 98

Entities Responsible for a Work Sources Preferred sources of information Other statements appearing prominently in the resource Use cataloger judgment Information appearing in the content Other sources 99

Creator (RDA 19.2) CORE ELEMENT person, family, or corporate body responsible for the creation of a work If more than one entity is responsible for the work as a whole: The creator having principal responsibility named first in the resource is required If principal responsibility is not indicated, only the first-named creator is required LC-PCC PS 19.2 says to use cataloger judgment in deciding whether to provide authorized access points for additional creators, beyond the core 100

What About Contributors? contributing to the realization of a work through an Expression Editors, translators, illustrators, arrangers of music, performers, writers of commentary, and others 101

Creator Changes from AACR2 No rule of three to identify the work only by its preferred title when there are more than three creators Performer of works by different composers presented in a sound recording is not automatically considered a creator 102

Compilers and Modifiers as Creators (19.2.1.1) An entity responsible for compiling an aggregate work may be considered a creator of the compilation if the selection, arrangement, editing, etc., of content for the compilation effectively results in the creation of a new work; An entity responsible for modifying a previously existing work in a way that substantially changes the nature or content of the original is considered a creator of the new work. 103

Corporate Bodies as Creators Categories of works (RDA 19.2.1.1.1) Similar to AACR2 21.1B2 Corporate body takes precedence over a first-named person or family as creator LC-PCC PS 19.2.1.1.1, similar to LCRI for AACR2 21.21B2 RDA 19.2.1.1.2 on government and religious officials as creators 104

Preferred Title for the Work CORE ELEMENT General instructions Specific instructions (Music, Law, etc.) 105

7. Compilations and Collaborations Poor Walt Whitman 106

Compilations and Collaborations Important distinction Determines how each is identified Compilations RDA 6.27.1.4 Collaborations RDA 6.27.1.3 107

How to Decide? Clues that you have a compilation: Indication of who created what From the preferred source, table of contents, preface, program notes, home page, other components in the resource Assume it is a collaboration if: you have no indication who created what you are in doubt 108

Multiple Works by One Creator Must be treated as a compilation i.e., there are no collaborators Identified by Creator + Preferred title 109

Preferred Title Compilations by One Entity (6.2.2.10) Has compilation become known by a title? Not usually But, e.g., Leaves of grass is an example of a compilation known by a title If not, use a conventional collective title (doesn t matter if title proper is distinctive): Complete works = use Works Complete works in a single form = use term chosen by cataloger Other compilations of two or more (but not all) works in same form or different forms = add Selections to the conventional collective title 110

Preferred Title Compilations by One Entity (6.2.2.10) Major changes from AACR2! Under RDA, catalogers will no longer need to: Determine if the creator created works only in a single form Determine if the title proper of the compilation is distinctive 111

Example: Compilation of Two Works by the Same Creator AACR2: use the 1st work as the preferred title (but this misidentifies the compilation) 100 1# $a Miller, Arthur, $d 1915-2005 240 10 $a Archbishop s ceiling 245 10 $a Two plays / $c Arthur Miller. 505 0# $a The Archbishop s ceiling -- The American clock. 700 12 $a Miller, Arthur, $d 1915-2005. $t American clock. 112

Example: Compilation of Two Works by the Same Creator RDA: apply the alternative to use a conventional collective title 100 1# $a Miller, Arthur, $d 1915-2005 240 10 $a Plays. $k Selections 245 10 $a Two plays / $c Arthur Miller. 505 0# $a The Archbishop s ceiling -- The American clock. 700 12 $a Miller, Arthur, $d 1915-2005. $t Archbishop s ceiling. *700 12 $a Miller, Arthur, $d 1915-2005. $t American clock. * 2 nd 700 not a core requirement but helpful to the user 113

Multiple Works by Multiple Creators -- Compilations vs. Compilation Preferred title Collaborations Without a creator, because there is no single creator of the individual works Collaboration Creator (principal or first-named) + Preferred title 114

Preferred Title Compilations of Works by Different Creators Compilation of separate works Identify the compilation by its preferred title (6.27.1.4) Either Title by which the compilation has become known (uncommon), or The title proper of the manifestation e.g., Best of Broadway (for a set of five CDs with selections from original cast recordings of various musicals by various composers) But see next slide 115

What if Such a Compilation Lacks a Collective Title? RDA and LC-PCC PS 25.1 How to treat: 1. For the preferred title, use the title proper of the first work in the compilation, and 2. Provide an analytical authorized access point for the predominant or first work in the compilation, when it represents a substantial part of the resource. Generally, do not devise a title to use as a preferred title. LC does not apply the alternative to 6.27.1.4 A work that is part of a larger work is considered a whole-part related work 116

Example: Compilation of Works by Different Creators (No Collective Title) AACR2: use the 1st work as the preferred title (but this misidentifies the compilation) 100 1# $a Polk, Sharon. 240 10 $a Community band concerts 245 10 $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. 700 12 $a Swanson, Terri. $t Fall harvest festivals. 117

Example: Compilation of Works by Different Creators (No Collective Title) RDA: use the title proper of the first work as the preferred title (do not devise a title) 245 00 $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. 700 12 $a Polk, Sharon. $t Community band concerts. *700 12 $a Swanson, Terri. $t Fall harvest festivals. * 2 nd 700 not a core requirement but helpful to the user 118

Collaborative Works Single Work, Multiple Creators Principally-responsible, or first-named creator Exceptions listed in 6.27.1.3 moving image resources some resources involving both corporate bodies and persons some musical collaborations treaties most serials (per LC-PCC PS; proposal to revise RDA) 119

Example: Multiple Creators -- Principal Responsibility No change from AACR2, except for added entries 100 $a Sweet, Martha. 245 $a Georgia history / $c by Martha Sweet and Linda Bruce with contributions by Gus Peterson and Marilee James. *700 $a Bruce, Linda. *700 $a Peterson, Gus. *700 $a James, Marilee. * number of access points for other creators: LC-PCC PS 19.3 = cataloger judgment 120

Example: Multiple Creators -- No Principal Responsibility AACR2: enter under title, with no 1XX field 245 $a Architecture / $c by Susan Brown [et al.]. *700 $a Susan Brown Other authors (Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson) listed on source, but not recorded in 245. 121

Example: Multiple Creators -- No Principal Responsibility RDA: precede preferred title by first-named creator 100 $a Brown, Susan. 245 $a Architecture / $c by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson. *700 $a Carlson, Melanie. *700 $a Lindell, Stephen. *700 $a Ott, Kevin. *700 $a Wilson, Janet. access points for other creators: cataloger judgment (LC-PCC PS 19.3) 122

Additions to Access Points Representing Works Formulating the Authorized Access Point Start with preferred title Precede by creator, if appropriate Addition(s) to make it distinct RDA 6.27.1.9 Each possible addition discussed in detail in earlier provisions of chapter 6 123

Additions to Access Points Representing Works Form of work (6.3) Date of the work (6.4) Place of origin of the work (6.5) Another distinguishing characteristic of the work (6.6) no priority order can give more than one if needed 124

LC Policy on Differentiating Works -- LC-PCC PS 6.27.1.9 Generally: catalog = the file against which cataloging is being done; may also take into account any resource which is known use the a.a.p. whenever the resource is referred to in other a.p. s (including subjects) or in notes citing relationships between resources resolve the conflict by making an addition to the a.a.p. in the bibliographic record being created; do not also modify the existing record do not predict a conflict when a resource is republished or reproduced, the a.a.p. for the original is used for any republication 125

LC Policy on Differentiating Works -- LC-PCC PS 6.27.1.9 with a parenthetical qualifier Choice of qualifying term: Use judgment. corporate body date of publication descriptive data elements, e.g., edition statement place of publication any word(s) that will serve to distinguish the works more than one qualifier if needed list not prescriptive, not in priority order 126

LC Policy on Differentiating Works -- LC-PCC PS 6.27.1.9 Form of qualifying term: Corporate body: use the authorized access point Place of publication: use the authorized access point without any cataloger s addition Multiple qualifiers: separate the qualifiers with a space-colon-space within one set of parentheses 127

Additions to Access Points -- Examples Advocate (Boise, Idaho) Advocate (Nairobi, Kenya) Dublin magazine (1762) Dublin magazine (1965) distinguish with place distinguish with date Bulletin (New York State Museum : 1945) Bulletin (New York State Museum : 1976) use of two qualifiers (corporate body and date) 128

Additions to Access Points -- Form of Work (RDA 6.3) CORE ELEMENT when needed to differentiate class or genre to which a work belongs Take from any source No controlled vocabulary Added after preferred title in parentheses 130 0# $a Chanson de Roland (Poem) 129

Additions to Access Points -- Date of Work (RDA 6.4) CORE ELEMENT when needed to differentiate earliest date associated with a work created, first published, or released Take from any source Year(s) alone Added after preferred title in parentheses 110 2# $a Connecticut Commission on Children. 240 10 $a Annual report (2005) 130

Additions to Access Points -- Place of Origin of Work (RDA 6.5) CORE ELEMENT when needed to differentiate the country or other territorial jurisdiction from which a work originated Take from any source In form prescribed in Chapter 16 Added after preferred title in parentheses 130 0# $a Renaissance history (Boston, Mass.) 245 10 $a Renaissance history : $b a reexamination. 131

Additions to Access Points -- Other Distinguishing Characteristic (RDA 6.6) CORE ELEMENT when needed to differentiate a characteristic other than form of work, date of work, or place of origin of the work that serves to differentiate a work from another work or from the name of a person, family, or corporate body Take from any source In established form Added after preferred title in parentheses 132

Variant Access Points for Works 6.27.4.1-6.27.4.4 General principle: use a variant title for the work as the basis for a variant access point. Example: Authorized access point for the work Dickens, Charles, 1812 1870. Pickwick papers Variant access point for the work Dickens, Charles, 1812 1870. Posthumous papers of the Pickwick Club Posthumous papers of the Pickwick Club 133

Variant Access Points for Works RDA also allows a variant access point, using just the preferred title, and formulated using other creators (e.g., collaborators not chosen as the principal creator). Example: Authorized access point for the work: Christo, 1935. Wrapped Reichstag. Variant access point for the work: Jeanne-Claude, 1935. Wrapped Reichstag (A work of art created jointly by Christo and Jeanne- Claude; variant access point considered important for subject access) Wrapped Reichstag 134

MARC Authority Fields for Works Cataloger judgment whether to include these fields in authority records 046 370 380 381 382 383 384 Date of work Place of origin of work Form of work Other distinguishing characteristics Medium of performance Numeric designation of a musical work Key 135

Exercise: Works 136

8. Expressions And once again back to FRBR Multiple MARC 21 Fields Bibliographic Format Authority Format 137

Expression the FRBR Entity the way in which a work (the idea in the creator s mind) is expressed through Language (i.e., alpha-numeric) Sound Movement Performance etc. 138

Identifying the Expression Authorized access points are used in bibliographic records to identify the expression being cataloged; also in 6XX and 7XX to represent relationships to other expressions Forms according to RDA Chapter 6 Two steps (similar to identifying the Work) Name the work Add expression-level identifying information 139

Decisions on Bibliographic or Authority? Always identify the expression by recording in the bibliographic record sometimes (per DCM Z1) also by making a title or name/title authority record Authorized access points are used in other authority records as 5XX fields (relationships to other expressions) for treaties and in cases of cataloger judgment 140

Decisions on How to Identify Expressions LC-PCC PS 0.6.3 Identify these expressions by adding an attribute to the authorized access point Music resources (6.28.3) Sacred scriptures (6.30.3) Translations and language editions (6.27.3) 141

Decisions on How to Identify Expressions For other categories, LC will include the expression attributes in other fields in the bibliographic record Content type 336 field Language 008/35-37 041 field 546 field 142

Decisions on How to Identify Expressions Do not add another characteristic to differentiate one expression from another e.g., do not differentiate one translation of Hamlet in French from another French translation e.g., do not differentiate one arrangement of Berlioz Corsaire from another arrangement 143

Decisions on Using Existing NARs Already an AACR2 NAR If only one expression represented by NAR Use the form in the NAR If more than one expression represented by NAR Do not use that form in your bibliographic 7XX field Instead, give separate access points for each expression in the bibliographic record 7XX fields Already an RDA NAR Use it in your bibliographic record, even if it includes an additional expression attribute LC wouldn t include 144

Contributors contributing to the realization of a work through an expression Chapter 20 Editors, translators, illustrators, arrangers of music, performers, writers of commentary, and others CORE ELEMENT for LC only for illustrators of resources intended for children RDA Appendix I.3.1 for relationship designators 145

Constructing the Authorized Access Point Representing an 6.27 Expression The basis is the authorized access point for the work Additions as outlined in 6.27.3 Goncourt, Edmond de, 1822 1896. Frères Zemganno. English. 146

Additions to Authorized Access Points for Expressions content type * (6.9) date of the expression * (6.10) language of the expression * (6.11) another distinguishing characteristic of the expression * (6.12) and/or * if needed to differentiate 147

Additions to Access Points for Expressions -- Content Type RDA 6.9 CORE ELEMENT when needed to differentiate fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived... Take from any source Controlled vocabulary in RDA 6.9.1.3 Access point: in subfield $h 130 $a $h Spoken word [For the audiobook of a printed text] 148

Content Type Recorded in 336 Field Use $3 if multiple components and term does not apply to all 149

Score: Examples of 336 Field (also showing 337-338) Book or printed text serial: 336 $a text $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a volume $2 rdacarrier 336 $a notated music $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a volume $2 rdacarrier 150

Map: CD of text: Examples of 336 Field (also showing 337-338) 336 $a cartographic image $2 rdacontent 337 $a unmediated $2 rdamedia 338 $a sheet $2 rdacarrier 336 $a text $2 rdacontent 337 $a computer $2 rdamedia 338 $a computer disc $2 rdacarrier 151

Examples of 336 Field (also showing 337-338) Book with accompanying CD of lecture: $3 and $e 300 $a 244 pages... + $e 1 CD 336 $3 book $a text $2 rdacontent 336 $3 CD $a spoken word $2 rdacontent 337 $3 book $a unmediated $2 rdamedia 337 $3 CD $a audio $2 rdamedia 338 $3 book $a volume $2 rdacarrier 338 $3 CD $ audio disc $2 rdacarrier Instead of 300 $e, can repeat 300 field 300 $a 244 pages... 300 $a 1 CD... Instead of $e, can give a note 500 $a Accompanied by a CD. 152

Additions to Access Points for Expressions -- Date of Expression RDA 6.10 Change! Not a CORE ELEMENT for LC Only for music, sacred scripture, translations LC catalogers are no longer required to add $f for Works and Works. Selections Take from any source earliest date associated with an expression May use date of manifestation If you find a NAR with this additional element, you may use it; do not create such NARs; do not perform authority maintenance 100 1# $a Bernstein, Leonard, $d 1918-1990. 240 10 $a Works 153

Additions to Access Points for Expressions -- Language of Expression RDA 6.11 CORE ELEMENT when needed to differentiate language in which a work is expressed Take from any source Use term(s) from the MARC 21 list of languages Access point: in subfield $l (not repeatable) Distinguish between: one expression in more than one language two or more expressions 154

If One Expression One language give $l only if a translation 100 1# $a Brunhoff, Jean de, $d 1899-1937. 240 10 $a Babar en famille. $l English 245 10 $a Babar and his children. More than one language do not give $l unless a translation Tolstoy, Leo, graf, 1828-1910. Voi na i mir. 155

If Two or More Expressions Original and One Translation If the manifestation is a compilation of the original and one translation of the same work record an analytical authorized access point for the original expression (without $l for the language) record a separate analytical authorized access point for the translation (with $l for the language) Examples of AACR2 and RDA on next 2 slides 156

Examples: Two Expressions -- Original and One Translation Original + Spanish translation in the same resource AACR2 041 1# $a eng $a spa $h eng 100 1# $a Macken, JoAnn Early, $d 1953-240 10 $a Mail carrier. $l Spanish & English 245 10 $a Mail carrier = $b El cartero / $c JoAnn Early Macken. 246 31 $a Cartero 546 ## $a English and Spanish. 157

Examples: Two Expressions -- Original and One Translation Original + Spanish translation in the same resource RDA 041 1# $a eng $a spa $h eng 100 1# $a Macken, JoAnn Early, $d 1953-245 10 $a Mail carrier = $b El cartero / $c JoAnn Early Macken. 246 31 $a Cartero 546 ## $a English and Spanish. 700 12 $a Macken, JoAnn Early, $d 1953- $t Mail carrier. 700 12 $a Macken, JoAnn Early, $d 1953- $t Mail carrier. $l Spanish. 158

If Two or More Expressions Original and More than One Translation If the compilation contains the original expression and more than one translation record an authorized access point for the original expression (without $l for the language) record an authorized access point for at least one translation (with $l for the language) Giving additional analytical access points is cataloger judgment 159

Other Language Situations Two or more expressions in different languages, and the original expression is not present Record at least one expression in an analytical a.a.p., with $l for the language 160

Other Language Situations Two or more expressions in different languages, and you cannot determine the original For the purpose of choosing the preferred title, choose the title proper named first on the preferred source of information as the preferred title of the work (i.e., treat the first as if it is the original edition) For the purpose of providing analytical a.a.p. s, treat the manifestation as if you have a compilation of the original and one or more translations (see slide 24): o Provide an analytical a.a.p. for the expression designated as the original, without subfield $l for the language o Provide an analytical a.a.p. point for at least one more expression, with subfield $l for the language 161

No Longer Use Polyglot Single subfield with multiple languages e.g., French & English Provide specific information about all the languages of each expression. 162

Additions to Access Points for Expressions -- Other Distinguishing Characteristic RDA 6.12 CORE ELEMENT when needed to differentiate a characteristic other than content type, language of expression, or date of expression that serves to differentiate an expression Take from any source Access point: at end of last subfield unless a separate subfield is available subfield $o for musical expressions (e.g., arranged ) subfield $s for versions of the Bible, etc. 163

Examples Other Distinguishing Characteristic 130 #0 $a Nutcracker (Choreographic work : Baryshnikov) 130 #0 $a Bible. $l English. $s Authorized. $f 2004 164

Variant Access Points for Expressions -- RDA 6.27.4.5 LC policy: cataloger judgment -- consider if important for user to find or identify Catalogers are users, too May be: based on a variant title of the work associated with a particular expression a form with a variant of the addition in the authorized access point 165

Examples -- Variant Access Points for Expressions 100 $a Lindgren, Astrid, $d 1907-2002. $t Pippi Långstrump. $l English 400 $a Lindgren, Astrid, $d 1907-2002. $t Pippi Longstocking 430 $a Pippi Longstocking 100 $a Hartmann, $c von Aue, $d active 12th century. $t Works. $l English 400 $a Hartmann, $c von Aue, $d active 12th century. $t Arthurian romances, tales, and lyric poetry 430 $a Arthurian romances, tales, and lyric poetry 166

MARC Authority Fields for Expressions Apply cataloger judgment when deciding whether to include these fields in any name authority records made for expressions. 046: Special coded dates 336: Content type 167

For More Guidance -- Constructing Access Points LC-PCC PS 6.27 -- Constructing Access Points to Represent Works and Expressions Use established forms in existing NARs If need to create, create RDA NAR Do not create hybrid NARs Do not add 7XX fields for RDA forms to AACR2 records or AACR2 forms for RDA records 168

Exercise: Expressions 169

Purpose of a Uniform Title to relate all expressions of a work UT used to connect if the title proper has changed from one expression to another, or from one manifestation to another MARC fields 1XX/240 130 170

What Constitutes a New Work? A different creator Not an additional creator A very different scope of content even if title proper/preferred title is the same No Work Authorized Access Point needed because the works are not the same 171

New Title, Content Not Revised New Manifestation UT (240) for preferred title -- same as AACR2 Original: 100 $a Smith, Lacey Baldwin, $d 1922-245 $a A Tudor tragedy : $b the life and times of Catherine Howard. 260 $a [New York] : $b Pantheon Books, $c [1961] Later title (no indication of revision): 100 $a Smith, Lacey Baldwin, $d 1922-240 $a Tudor tragedy 245 $a Catherine Howard / $c Lacey Baldwin Smith. 260 $a Stroud Gloucestershire : $b Amberley, $c [2010], 2010. 500 $a Originally published under title: A Tudor tragedy 172

Same Title, Content Revised New Expression no UT -- same as AACR2 Original: 100 $a Harwood, Gregory W. 245 $a Giuseppe Verdi : $b a guide to research / $c Gregory Harwood. 260 $a New York : $b Garland Pub., $c 1998. Revision: 100 $a Harwood, Gregory W. 245 $a Giuseppe Verdi : $b a research and information guide / $c Gregory W. Harwood. 250 $a Second edition. 260 $a New York, NY ; $a Abingdon, Oxon : $b Routledge, $c 2012. 173

New Title, Content Revised New Expression UT (240) field change from AACR2 Original: 100 $a Monson, Craig. 245 $a Disembodied voices : $b music and culture in an early modern Italian convent / $c Craig A. Monson. 260 $a Berkeley : $b University of California Press, $c 1995. Revision: 100 $a Monson, Craig. 240 $a Disembodied voices 245 $a Divas in the convent : $b nuns, music, and defiance in seventeenth-century Italy / $c Craig A. Monson. 260 $a Chicago : $b University of Chicago Press, $c 2012. 500 $a Revision of the author s Disembodied voices. 174

New Title, Content Revised New Expression UT (130) field change from AACR2 Original: 245 $a Contemporary art and multicultural education / $c edited by Susan Cahan and Zoya Kucor. 260 $a New York : $b New Museum of Contemporary Art : $b Routledge, $c 1996. Revision: 130 $a Contemporary art and multicultural education 245 $a Rethinking Contemporary Art and Multicultural Education / $c The New Museum of Contemporary Art. 250 $a Fully revised second edition. 260 $a New York, NY : $b Routledge, $c 2011. 175

9. Relationships Very little AACR2 precedent Intrinsic to RDA and to FRBR 176

Basics of Relationships What are relationships? Why relationships? Expressing Relationships: Helps users find what they want! 177

Basics of Relationships Entities being related? Types of relationships 178

Entities Being Related Relationships between: Resources and associated persons, families, and corporate bodies Resources (works, expressions, manifestations, items) Persons, families, corporate bodies 179

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 180

Relationship Designators RDA Appendices I, J, and K Not closed lists If needed term is missing, decide on a term and notify the PCC SCS 181

[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)] 182