RDA Test “Train the Trainer”

1. RDA Test “Train the Trainer” Module 4: Identifying Works and Expressions [Content as of Mar. 31, 2010]

2. Bibliographic or authority data? • RDA does not prescribe if attributes about the work/expression and the access points are to be recorded as bibliographic data or authority data • Agency decision related to implementation functionality, to analysis policy, etc. • For initial implementation, most often establish the access point with authority data

3. Language and script • Title for a work in the language and script in which it appears in the resource – RDA 5.4 • Alternative: a transliterated form as a substitute for or in addition to the found form • Descriptive attributes for a work or expression in RDA chapter 7 in language and script preferred by the agency • Other attributes for a work or expression in RDA chapter 6 in language and script prescribed in instructions

4. Title of an expression? • No! -- Doesn’t exist in the FRBR/FRAD models • Instead, build the access point for an expression by adding identifying attributes to the access point for the work (RDA 5.5/5.6)

5. Authorized access point for a manifestation? • Not included in RDA yet • Will be added when the FRBR model is extended to subject entities because most often need to have such an access point for a subject relationship

6. Yes, create an authorized access point for a manifestation • However, at times do need an access point for a manifestation for non-subject reasons (e.g., for a monographic series issued in different carriers): • Build on the access point for the expression by adding a distinguishing characteristic 130 $a R&D studies (CD-ROM)

7. General guidelines for titles (RDA 6.2.1) • Capitalization of title – see RDA appendix A.3 • Numbers in title in found form • For parts of works, see RDA 6.2.2.9 • Accents in title as found; optionally, can add

8. General guidelines for titles (RDA 6.2.1) • Omit initial article unless accessed by that article • Do not give space between a period and an initial • If initials lacking periods have spaces, retain spaces • Abbreviations in title – see RDA appendix B.3

9. Terminology • Title of the work: “word, character, or group of words and/or characters by which a work is known” • Preferred title • For current implementations = the form of title used when constructing the authorized access point • Variant title • For current implementations = the form of title used when constructing a variant access point

10. Sources of information • Sources for preferred title for work (6.2.2.2): • For a work created after 1500: from resources embodying the work (usually the first manifestation received) or reference sources • For a work created before 1501: from modern reference sources

11. Sources of information • If the evidence of modern reference sources is inconclusive for a work created before 1501, use (in this order of preference): a) modern editions b) early editions c) manuscript copies • All other elements for works and expressions: any source

12. Reminder: changes in the resource • Some changes affect the identification of the work (RDA 6.1.3) • Related to some of the reasons for new descriptions (RDA 1.6) discussed in module 3 • Depends upon basis of identification for the specific mode of issuance

13. Elements covered in this module • Works: Core and Core if … • Expressions: Core and Core if … • Other elements if change from AACR2 • MARC 21 changes included in the above • Other MARC changes

14. Core elements forWorks

15. Preferred title for the work • General instructions in RDA 6.2 • Specific instructions: • parts (RDA 6.2.2) • compilations (RDA 6.2.2) • some musical works (RDA 6.14.2) • some legal works (RDA 6.19.2) • some religious works (RDA 6.23.2) • some official communications (RDA 6.26.2)

16. Preferred title: changes from AACR2 • No longer routinely omit introductory phrases (e.g., “Here beginneth …”) and statements of responsibility • Preferred title based on first manifestation received • If later manifestations have different forms, determine the most common form of the preferred title -- it may not have such a phrase or statement

17. Preferred title: Other changes from AACR2 • “Selections” not used alone as the preferred title -- instead, “Works. Selections” • For simultaneous publications with different titles: choice based on first resource received

18. Simultaneous publication: different titles in same language • Choose the preferred title based on title of the resource first received (not the resource published in the home country) U.K. volume received first: Walking in Britain U.S. volume received later: Day walks in Britain Preferred title = Walking in Britain

19. Simultaneous publication: different titles/languages • No longer a priority order of languages – use title in resource first received Serial published simultaneously in German and English versions German-language version received first English-language version received later Preferred title = title from German-language version

20. Preferred titles: parts of the Bible • Refer to the Old and New Testaments by their spelled-out forms (not “O.T.” and “N.T.”) • Omit the name of the testament in the preferred title for individual books or groups of books

21. Bible examples 130 $a Bible. $p New Testament not130 $a Bible. $p N.T. 130 $a Bible. $p Genesis not130 $a Bible. $p O.T. $p Genesis 130 $a Bible. $p Gospels not130 $a Bible. $p N.T. $p Gospels

22. Entity related to work • RDA 0.6.3 and RDA 6.27.1: 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 work

23. Chapter 19: entity responsible for a work • Sources (RDA 19.1.1): • Preferred sources of information (RDA 2.2.2) • Other statements appearing prominently in the resource • Information appearing only in the content • Other sources

24. Creator • Creator = “person, family, or corporate body responsible for the creation of a work” = core element (RDA 19.2) • If more than one, only the creator having principal responsibility named first in resource is required • If more than one and principal responsibility not indicated, only the first-named creator is required

25. Collaborative works • For collaborative works, the creators may perform the same or different roles (RDA 19.2.1) • Choosing the first-named creator to name the work may mean that the result is not the same as applying the AACR2 rule due to the order of names on the source

26. Example: creators with principal responsibility 100 $a Sweet, Martha. 245 $a … / $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: agency decision

27. Example: creators with no principal responsibility indicated 100 $a Brown, Susan. 245 $a … / $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. * number of access points for other creators: agency decision

28. Corporate body as creator • Categories of works given in RDA 19.1.1 • Includes government and religious officials for some categories of works • Corporate body takes precedence over a first-named person or family as creator

29. Compilation of works • RDA: do not name the compilation by the first work in the compilation as AACR2 does in some situations, because doing so misidentifies the aggregate work • Can give authorized access points for each work/expression • If no collective title, alternative is to devise a title proper

30. Preferred title for compilations of one person, family, body • RDA 6.2.2.10 • Categories: • 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 = give preferred title for each work

31. Alternative for “Other compilations …” • Instead of or in addition to giving the preferred title for each work, use a conventional collective title, e.g.,: • Works. Selections • Posters. Selections • Orchestra music. Selections

32. Compilation of two works by same creator AACR2: 100 $a Miller, Arthur, $d 1915-2005 240 $aArchbishop’s ceiling 245 $a Two plays / $c Arthur Miller. 505 $a The Archbishop’s ceiling -- The American clock. 700 $a Miller, Arthur, $d 1915-2005. $t American clock.

33. Compilation of two works by same creator RDA with alternative for conventional collective title: 100 $a Miller, Arthur, $d 1915-2005 240 $a Plays. $k Selections 245 $a Two plays / $c Arthur Miller. 505 $a The Archbishop’s ceiling -- The American clock. 700 $a Miller, Arthur, $d 1915-2005. $t Archbishop’s ceiling. 700 $a Miller, Arthur, $d 1915-2005. $t American clock.

34. Compilation of works by different creators AACR2: 100 $a Polk, Sharon. 240 $a Community band concerts $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. $a Swanson, Terri. $t Fall harvest festivals.

35. Compilation of works by different creators RDA without alternative for devised title: $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. 700 $a Polk, Sharon. $t Community band concerts. 700 $a Swanson, Terri. $t Fall harvest festivals.

36. Compilation of works by different creators RDA with alternative for devised title: 245 $a [Two United States Midwest memoirs] 505 $a Community band concerts / Sharon Polk -- Fall harvest festivals / Terri Swanson. 700 $a Polk, Sharon. $t Community band concerts. 700 $a Swanson, Terri. $t Fall harvest festivals.

37. Signatory to a treaty, etc. • RDA 6.22 • Scope = “government or other party that has formally signed a treaty, etc., as an adherent to its terms and conditions” • In the form of the authorized access point (ch. 11)

38. Signatory to a treaty, etc. • Core: • first-named signatory as part of creating the authorized access point for the work (RDA 6.29.1.15+) • both signatories if the work is a bilateral treaty • 2nd signatory as part of authorized access point for the treaty (can also give separate access point for the 2nd signatory)

39. Authorized access point for treaties • First-named signatory regardless of number of signatories + preferred title (RDA 6.19.2.7-6.19.2.8) • Not based on English alphabetic order • Exception: if one party on one side and two or more on other side, use the single party even if not first-named • Additions to the access point: 6.29.1.33

40. Bilateral treaty 110 $a Barbados. 240 $a Treaties, etc. $g Finland $d 1989 June 15 245 $a Convention between Barbados and Finland : $b for the avoidance of double taxation with respect to taxes on income. *710 $a Finland. * Agency decision if including separate access point for party in 240 $g.

41. Multilateral treaty 110 $a Sweden. 240 $a Treaties, etc. $d 2009 May 28. 245 $a Treaty on import duties between Sweden, Finland, Denmark, Norway, and Iceland. *710 $a Finland. *710 $a Denmark. *710 $a Norway. *710 $a Iceland. * Agency decision on number of additional access points.

42. Other person, family, body • Other person, family, or corporate body associated with a work = core element ifused when creating the authorized access point for the work (RDA 6.27-6.31) • RDA 19.3 • Scope = “a person, family, or corporate body associated with a work other than as a creator”

43. Other person, family, body used in work’s authorized access point • Won’t occur often • One example: • Jurisdiction governed by laws is not the jurisdiction enacting the laws (not the creator) • But RDA 6.29.1.2 says to construct the authorized access point for laws governing one jurisdiction by combining the authorized access point for the jurisdiction governed and the preferred title for the laws

44. Identifier for the work • RDA 6.8 • Scope: “a character string uniquely associated with a work, or with a surrogate for a work (e.g., an authority record) that serves to differentiate that work from other works” • Precede the identifier with indication of person or agency, etc., responsible for assigning the identifier

45. MARC for Identifier for a work • In access point in bibliographic records, record control number in MARC subfield $0 (Authority record control number) • In authority records: • a record control number in field 001, 010, etc. • other identifiers in field 024 with first indicator “7” (ensure that source of code has been added to MARC list cited in subfield $2)

46. Core if … elements for Works

47. 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, record the elements: • either as additions to the authorized access point representing the work [RDA Test], • as separate elements, or • as both • In a “core context,” application would generally be as additions to the authorized access point

48. Form of work • RDA 6.3 • Scope = class or genre to which a work belongs -- no controlled vocabulary • Core if needed to differentiate a work

49. MARC for Form of work • Access point: added in parentheses to preferred title for the work (subfielding will vary) • 380 field: subfield $a 130 0# $a Ocean’s eleven (Motion picture) 380 ## $a Motion picture

50. Date of work • RDA 6.4 • Scope: earliest date associated with a work • Date work was created, or • Date work was first published or released • Core if needed to differentiate a work