1 LC Training for RDA: Resource Description & Access Module 2: Identifying Works and Expressions Cooperative and Instructional Programs Division, Library of Congress 2012

2 Acknowledgements  This course has been adapted from training delivered by Barbara Tillett and Judith Kuhagen, Library of Congress Policy and Standards Division, to the Georgia Public Library Cataloging Summit, August 2011  COIN gratefully acknowledges their permission to adapt the material for the present purpose

3 Learning Objectives for Module 2 -- Identifying Works and Expressions o Introduction to the Module o Elements for Works o Elements for Expressions o Content of Works and Expressions o Creators, Contributors, and Relationship Designators o Miscellaneous Changes from AACR2

4 Unit 1: Introduction to the Unit  Where are the Instructions?  Naming the Work  LC Decisions on … Bibliographic or Authority? Core Elements to Distinguish Language and Script  Terminology  Sources  Authorized Access Points for Works

5 Introduction to Works and Expressions: 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”

6 Naming the Work -- Same as Determining “Main Entry”?  Also called “naming the work” and “naming the expression”  Same as AACR2 “main entry” if the manifestation contains that work/expression: Bibliographic RecordsAuthority Records 100/110/ /110/111 $a $t 100/110/ /110/111 $a $t

7 LC 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: 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

8 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 always give as additions to the authorized access point cataloger judgment to also give as separate elements in authority records

9 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 LCPS 5.4), can also give variant access points (MARC 4XX) in original language/script in authority records  Other attributes for a work in RDA chapter 6 in language and script prescribed in instructions

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

11 Sources of Information – Preferred Titles (RDA )  For a work created after 1500 From resources embodying the work or from reference sources The most common form of the title 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

12 Sources of Information – Other Elements (RDA 6.1.1)  For all other identifying attributes of works and expressions  Take the information from any source

13 Authorized Access Points for Works RDA  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  Links back to the instructions on recording each of the specific elements

14 Unit 2: Elements for Works  Preferred Title for the Work  Entities Responsible for a Work  Compilations vs. Collaborations  Additions to Access Points for Works  Variant Access Points for Works  MARC Authority Fields for Works

15 Preferred Title for the Work -- Overview  CORE ELEMENT  General instructions (RDA and 6.2.2)  Specific instructions (RDA , , and later instructions in Chapter 6)

16 Preferred Title for the Work – General Instructions  RDA Recording titles (i.e., in general) Scope: “… by which a work is known.” Capitalization; Numbers; Diacritics; Articles; Spacing; Abbreviations  RDA – Scope and sources Choosing preferred titles Recording preferred titles

17 Preferred Title for the Work – Specific Categories  some musical works (RDA )  some legal works (RDA )  some religious works (RDA )  some official communications (RDA )

18 Preferred Title – Parts of a Work (RDA )  Other than musical or religious works  How many parts? one (RDA ) two or more (RDA )

19 Parts of a Work – One Part (RDA )  “Record the preferred title for the part, applying the basic instructions on recording titles of works given under ” Preferred title for a part of J.R.R. Tolkien’s The lord of the rings:  Two towers Preferred title for a part of the television program The Simpsons:  King of the hill

20 Parts of a Work – Two or More Parts (RDA )  Consecutively numbered, with only a general designation “Record the designation of the parts … followed by the inclusive numbers of the parts”  Preferred title for the first six books of Homer’s Iliad:  Book 1–6  Two or more unnumbered or non- consecutively numbered parts “Record the preferred title for each of the parts”  Preferred title for a part of Divina commedia in a compilation also comprising the part Paradiso:  Purgatorio

21 Parts of a Work – Two or More Parts (Alternative)  Alternative instruction for unnumbered or non-consecutive parts  LC practice (LCPS ) “Instead of recording the preferred title for each of the parts, record the conventional collective title Selections as the preferred title for the parts.” Preferred title for the parts of the work in a compilation comprising books 1 and 6 of Homer’s Iliad  Selections

22 Authorized Access Point for Part(s) of a Work (RDA )  Generally: preferred title for part(s), preceded by authorized access point for the creator, if appropriate  Exceptions: preferred title for part(s), preceded by authorized access point for the work non-distinctive titles serials and integrating resources television/radio programs consecutively-numbered parts

23 Preferred Title – Compilations of One P - F - CB (RDA )  Has compilation become known by a title? Not usually e.g., Leaves of Grass is not a compilation  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 works in same form or different forms = add “Selections” to the appropriate conventional collective title

24 Preferred Title – Compilations of One P - F - CB (cont.)  Major change from AACR2!  Under RDA, LC 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”

25 Preferred Title – Compilations of Works by Different Creators  Identify the compilation by its preferred title (RDA )  Either Title by which the compilation has become known (uncommon), or The title proper of the manifestation  Resource described: The best of Broadway (A set of five CDs with selections from original cast recordings of various musicals by various composers)  Best of Broadway

26 What if Such a Manifestation Lacks a Collective Title?  A work that is part of a larger work is considered a whole-part “related work” RDA and LCPS 25.1 Generally:  Use the title proper of the first work in the compilation as the preferred title, and  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, d o not devise a title to use as a preferred title.  LC does not apply the alternative to  Change in LC policy from the RDA Test!

27 Examples of Compilations – AACR2 vs. RDA  The next four slides illustrate examples of various ‘compilation’ situations  RDA attempts to ‘correct’ the misleading misidentification of works that sometimes occurred in AACR2

28 Examples of Compilations – 2 Works by the Same Creator AACR2:use the 1st work as the preferred title, which misidentifies the compilation 100 1# $a Miller, Arthur, $d $a Archbishop’s ceiling $a Two plays / $c Arthur Miller # $a The Archbishop’s ceiling -- The American clock $a Miller, Arthur, $d $t American clock.

29 Examples of Compilations – 2 Works by the Same Creator 100 1# $a Miller, Arthur, $d $a Plays. $k Selections $a Two plays / $c Arthur Miller # $a The Archbishop’s ceiling -- The American clock $a Miller, Arthur, $d $t Archbishop’s ceiling. * $a Miller, Arthur, $d $t American clock. RDA:apply the alternative to use a conventional collective title * Not a core requirement but helpful to the user

30 Examples of Compilations – Different Creators, No Collective Title 100 1# $a Polk, Sharon $a Community band concerts $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson $a Swanson, Terri. $t Fall harvest festivals. AACR2:use the 1st work as the preferred title (this misidentifies the compilation)

31 Examples of Compilations – Different Creators, No Collective Title RDA: u se the title proper of the first work as the preferred title; do not devise a title $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson $a Polk, Sharon. $t Community band concerts. * $a Swanson, Terri. $t Fall harvest festivals. * Not a core requirement but helpful to the user

32 Entities Responsible for a Work  RDA  “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”

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

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

35 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 (i.e., is a “collaboration”): 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 LCPS 19.2 says to use cataloger judgment in deciding whether to provide authorized access points for additional creators, beyond the core

36 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

37 Compilers and Modifiers as Creators ( )  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.

38 Collaborative Works  Creators may perform the same or different roles (RDA )  Principally-responsible, or first-named creator  Exceptions not to use the first-named creator (RDA ) most moving image resources (named by preferred title); some resources involving both corporate bodies and persons; most serials (per LCPS; proposal to revise RDA)

39 Example: Multiple Creators with Principal Responsibility 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: LCPS 19.3 = cataloger judgment

40 Example: Multiple Creators -- No Principal Responsibility Indicated 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 (LCPS 19.3) Under AACR2, this would have been entered under title, with no 1XX field

41 Corporate Bodies as Creators  Categories of works (RDA ) Similar to AACR2 21.1B2  Corporate body takes precedence over a first-named person or family as creator  LCPS, similar to RI for 21.21B2  RDA on government and religious officials as creators

42 Compilations vs. Collaborations  Important distinction  Determines how each is ‘identified’  Compilations RDA  Collaborations RDA

43 Compilations vs. Collaborations – One Creator  Multiple works by a single creator Treated as a compilation  Identified by Creator + Preferred title

44 Compilations vs. Collaborations – Multiple Creators  Compilation Preferred title  Collaboration Creator (principal or first-named) + Preferred title

45 Compilations vs. Collaborations – 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

46 Commentary, Etc., Added to a Previously Existing Work –  If presented as the work of the entity responsible for the commentary, etc. construct the authorized access point by combining  the authorized access point representing the entity responsible for the commentary, and  the preferred title for the commentary.  Example: Akram, Malik M. Comprehensive and exhaustive commentary on the Transfer of Property Act, 1882 (A commentary by Akram that includes the text of the law and its amendments) *If more than one person is responsible for the added commentary, etc., apply the instructions on collaborative works

47 Commentary, Etc., Added to a Previously Existing Work –  If presented as an edition, treat it as an expression use the authorized access point representing the previously existing work If it is considered important for identification, construct an authorized access point representing the expression  Example: Joyce, James, 1882–1941. Dubliners (Resource described: James Joyce’s Dubliners : an illustrated edition with annotations / [edited by] John Wyse Jackson & Bernard McGinley)

48 Additions to Access Points Representing Works  Reminder on how to formulate the Authorized Access Point Start with preferred title Precede by creator, if appropriate Addition(s) to make it distinct  RDA Each possible addition discussed further in earlier provisions of chapter 6

49 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

50 Additions to Access Points Representing Works -- LCPS  Differentiating all works  Specific guidelines for categories of resources  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

51 Additions to Access Points Representing Works -- LCPS  “… 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

52 Additions to Access Points Representing Works -- LCPS  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

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

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

55 Additions to Access Points -- Date of Work (RDA 6.3)  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 $a Annual report (2005)

56 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.) $a Renaissance history : $b a re- examination.

57 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

58 Variant Access Points for Works RDA  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

59 Variant Access Points for Works (cont.)  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)

60 Variant Access Points for Works (cont.)  LC Policy: Apply cataloger judgment Consider user needs  LC does not create or maintain SARs LCPS

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

62 MARC Authority Fields for Works – For More Guidance  R-documents ing_oct_2011.html LC policy for encoding information in MARC authority records: document R-5 NAR examples: document R-6  Examples folder for authority records on LC RDA site:  LC Network Development and MARC Standards Office:

63 Unit 3: Exercises on Works  Document R-6 Examples  Exercise #5 Determining Creator  Exercise #6 Identifying Works

64 Unit 4: Elements for Expressions  “Expression” – the FRBR Entity  Naming the Expression  Authorized Access Point Representing an Expression  Additions to Authorized Access Points for Expressions  Variant Access Points for Expressions  MARC Authority Fields for Expressions

65 Expression – the FRBR Entity  ‘the way in which a work (the idea in the creator’s mind) is expressed’  through … Language Sound Movement Performance etc.

66 Naming the Expression — Similar to “Naming the Work”  Same as AACR2 concept of “main entry” if the manifestation contains that expression  Forms of authorized access points are according to RDA chapter 6 Appendix E and LCPS for punctuation, etc.  Authorized access points are used in bibliographic records to identify the expression being cataloged; also as 6XX and 7XX to represent relationships to other expressions

67  Always identify the expression by giving information in the bibliographic record sometimes (see DCM Z1) also identify the expression 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 LC Policies – Bibliographic or Authority?

68  LCPS  Identify these expressions by using an authorized access point 1. Music resources (RDA ) 2. Sacred scriptures (RDA ) 3. Translations and language editions LC Policies – Three Categories

69  For expressions in other categories, LC will include the identifying expression attributes in other fields in the bibliographic record Date of expression (often the date of manifestation in 264 field is used) Content type in 336 field LC Policies – Other Expressions

70  No existing NAR … 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  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 LC Policies – NARs

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

72  Not “Title of an Expression” “Title of Expression” doesn’t exist in the FRBR/FRAD conceptual models  Constructing the Access Point Authorized access point for the work is the basis Additions to the authorized access point for the work Authorized Access Point Representing an Expression

73 Additions to the Authorized Access Point for the Expression  6.9 content type *  6.10 date of the expression *  6.11 language of the expression *  6.12 another distinguishing characteristic of the expression * * if needed to differentiate “and/or”

74 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  Access point:in subfield $h 130 $a ____________ $h Spoken word [For the audiobook of a printed text]

75 Content Type Recorded in 336 Field  New records One content type present in ILS templates  Existing records One content type added by macro  May add another field if appropriate  Use $3 if multiple components and term does not apply to all

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

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

78 Instead of 300 $e, can repeat 300 field 300 $a 244 pages $a 1 CD... Instead of $e, can give a note 500 $a Accompanied by a CD. 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 Examples of 336 Field (also showing )

79 Additions to Access Points for Expressions -- Date of Expression  RDA 6.10  Not a CORE ELEMENT for LC Only for music, sacred scripture  “earliest date associated with an expression” May use date of manifestation  Take from any source  No longer add in subfield $f for “Works” and “Works. Selections” 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 $a Works

80 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 of the same work, each in a different language or languages

81 One Expression  Manifestation with one expression in one language -- give subfield $l if a translation  Manifestation with one expression in more than one language -- do not give subfield $l unless a translation 100 1# $a Brunhoff, Jean de, $d $a Babar en famille. $l English $a Babar and his children.

82 Two or More Expressions o Original and one translation: record the original expression (without the language) in an analytical authorized access point, and the translation (with the language) in a separate analytical authorized access point. o Original and more than one translation: give analytical authorized access points for the original expression (without the language) and at least one translation. o Two or more expressions in different languages, and the original expression is not present: record at least one of the translations in an analytical authorized access point. o Two or more expressions of the same work in different languages, and you cannot determine the original: If two language editions, provide analytical authorized access points for each expression and record the language of each in subfield $l If more than two language editions, give analytical authorized access points for the first language edition and at least one other edition.

83 Examples -- Compilation: Different Expressions of the Same Work Original + Spanish translation in the same resource AACR # $a eng $a spa $h eng 100 1# $a Macken, JoAnn Early, $d $a Mail carrier. $l Spanish & English $a Mail carrier = $b El cartero / $c JoAnn Early Macken $a Cartero 546 ## $a English and Spanish.

84 Examples -- Compilation: Different Expressions of the Same Work Original + Spanish translation in the same resource RDA 041 1# $a eng $a spa $h eng 100 1# $a Macken, JoAnn Early, $d $a Mail carrier = $b El cartero / $c JoAnn Early Macken $a Cartero 546 ## $a English and Spanish $a Macken, JoAnn Early, $d $t Mail carrier $a Macken, JoAnn Early, $d $t Mail carrier. $l Spanish.

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

86 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

87 Examples – Other Distinguishing Characteristic 130 #0 $a Nutcracker (Choreographic work : Baryshnikov) 100 1# $a Dickens, Charles, $d $a Oliver Twist. $k Selections 130 #0 $a Bible. $l English. $s Authorized. $f # $a Schubert, Franz, $d $a Songs, $k Selections; $o arranged

88 Variant Access Points for Expressions -- RDA  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  May be a form with a variant of the addition in the authorized access point  LC Practice: add the date of expression when the authorized access point uses a conventional collective title that begins with "Works"

89 Examples -- Variant Access Points for Expressions 100 $a Lindgren, Astrid, $d $t Pippi Långstrump. $l English 400 $a Lindgren, Astrid, $d $t 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

90 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 $k beginning or single date created $l ending date created  336: Content type

91 MARC Authority Fields for Expressions – For More Guidance  “Refresher documents” R5 and R6 LC policy for encoding data: document R-5 NAR examples: document R-6  Examples folder for authority records on LC RDA site  LC Network Development and MARC Standards Office

92 Unit 5: Exercises on Expressions  Document R-6 Example 14  Exercise #7 Expressions

93 Unit 6: Content of Works and Expressions  General Guidelines  Content Attributes of Works  Content Attributes of Expressions

94 General Guidelines on Describing Content  RDA Chapter 7  Sources Take information used to describe content from the resource itself In certain cases the information may be taken from sources outside the resource as well

95 Attributes of Works – Nature of the Content  RDA 7.2  Character of primary content  Record if considered important  Examples: Singspiel in two acts Cross-cultural survey

96 Attributes of Works – Coverage of the Content  RDA 7.3  Chronological or geographic coverage  Record if considered important  Examples: Based on 1981 statistics Shows all of western Europe and some of eastern Europe

97 Attributes of Works – Coordinates of Cartographic Content  RDA 7.4  Longitude and latitude are CORE for LC  Not covered in depth in this class

98 Attributes of Works – Intended Audience  RDA 7.7  CORE ELEMENT for LC for resources intended for children  Class of user  Examples: For children aged 7-9 For remedial reading programs

99 Attributes of Works – Dissertation or Thesis Information  RDA 7.9  CORE ELEMENT for LC  Formal requirements for a degree Degree; institution; year 502 ## $b Ph.D. $c University of Toronto $d 1974

100 Attributes of Works – Dissertation or Thesis Information  LCPS  If the resource lacks a formal thesis statement, state its origin as a thesis in a general note in MARC field ## $a Revision of the author’s thesis *LC catalogers rarely catalog original theses or dissertations; you will usually construct a 500 field rather than a 502 field

101 Attributes of Expressions – Cartographic Resources  4 LC CORE ELEMENTS Horizontal scale (7.25.3) Vertical scale (7.25.4) Additional scale information (7.25.3) Projection of cartographic content (7.26)

102 Attributes of Expressions – Music Resources  3 LC CORE ELEMENTS Form of musical notation (7.13.3) Format of notated music (7.20) Medium of performance of musical content (7.21)

103 Attributes of Expressions – Summarization of the Content  RDA 7.10  CORE ELEMENT for LC  Abstract, summary, synopsis, etc.  Record if considered important  LCPS on use of MARC fields 520 and 856

104 Attributes of Expressions – Language of the Content  RDA 7.12  CORE ELEMENT for LC  Abstract, summary, synopsis, etc.  Record if considered important  LCPS In addition to primary content, also supply languages of other content (summaries, tables of contents, etc.) if it will assist in identification and selection Use form of name found in MARC Code List for Languages

105 Attributes of Expressions – Form of Notation - Script  RDA  CORE ELEMENT for LC for some scripts and for form of musical notation  Set of characters and/or symbols used to express the written language content  Examples: 1. Devanagari 2. Armenian Cyrillic (Resource written in both scripts)  LCPS

106 Attributes of Expressions – Supplementary Content  RDA 7.16  CORE ELEMENT for LC for indexes and bibliographies in monographs  Record if considered important  LCPS Routinely for: bibliographical references, discographies, filmographies, indexes, appendices, errata slips not printed as part of the publication If bibliographical citations in any form, generally use:  504 ## $a Includes bibliographical references. If a single bibliography, add the foliation/pagination:  504 ## $a Includes bibliographical references (pages ). If an index to its own contents:  500 ## $a Includes index.  500 ## $a Includes indexes. Bibliography note and index note may be combined.  504 ## $a Includes bibliographical references and index.

107 Unit 7: Exercise on Content of Works and Expressions  Exercise #8Describing Content of Works and Expressions

108 Appendix 1: Creators, Contributors, and Relationship Designators  RDA Appendix I  I.2. Relationship Designators for Persons, Families, and Corporate Bodies Associated with a Work I.2.1. Relationship Designators for Creators I.2.2. Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work  I.3. Relationship Designators for Persons, Families, and Corporate Bodies Associated with an Expression I.3.1. Relationship Designators for Contributors

109 Appendix 2: Miscellaneous Changes from AACR2  Primarily special formats Motion pictures Scriptures Music Law  “There is no limit on the number of authorized access points for compilations of works by different persons, families, or corporate bodies”