1. 1 LC Training for RDA: Resource Description & Access Module 2: Describing Carriers and Identifying Works Cooperative and Instructional Programs Division, Library of Congress 2012 Adapted by the National Library of New Zealand, October 2012

2. 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.  It incorporates the “Refresher Training” conducted for LC’s RDA Testers in October 2011.  COIN gratefully acknowledges PSD’s permission to adapt the material for the present purpose

3. 3 About This Material  This training material has been created for a primary audience of Library of Congress staff. Other audiences are welcome to utilize it as they see fit.  However, it should be understood that they reflect policies for LC staff, and should not necessarily be interpreted to either prohibit or require specific practices for persons external to LC.

4. 4 This version of this material  Adapted from the original Library of Congress training programme by the National Library of New Zealand  Some slides have been edited in red  Other slides have been removed to fit with the way training has been organised by the National Library of New Zealand  Extra slides have been added with red title boxes to distinguish them from the LC originals.

5. 5 Online Quiz on manifestations and items  Online Graded Quiz – 15 minutes Multiple Choice True/False Graded results at end of quiz  http://www.loc.gov/catworkshop/RDA%20training%20materials/ LC%20RDA%20Training/LC%20RDA%20course%20table.html http://www.loc.gov/catworkshop/RDA%20training%20materials/ LC%20RDA%20Training/LC%20RDA%20course%20table.html  A link to the quiz is also available in Wharenui  Some answers only apply to LC cataloguers, so skip questions if they don’t appear relevant to NLNZ

6. 6 Learning Objectives for Module 2 -- Describing Carriers and Identifying Works o Describing Carriers o Other Elements of Manifestations and Items o Introduction to Works – Nov 12-16 o Elements for Works -

7. 7 Unit 1: Describing Carriers oRDA Chapter 3 oWill not discuss specific elements for resources of special formats (films, maps, scores, etc.) oExamples available in RDA, in MARC documentation, and in LC compilation of examples oThe purpose of providing these elements is to help the user select the resource he or she wants.

8. 8 Replacement for GMD (General Material Designation) - 245 $h  Three new MARC fields - developed with ONIX publishing community: Content type -- RDA 6.9 -- MARC 336 field  This is an expression level attribute and will be covered in detail later in the course. The focus at this stage is on the manifestation or item, i.e. the physical object Media type -- RDA 3.2 -- MARC 337 field Carrier type -- RDA 3.3 -- MARC 338 field

9. 9 MARC for Media and Carrier  In each of the two fields for these elements (337 & 338): $a term $b code $2 “rdamedia” or “rdacarrier” as appropriate $3 materials specified - give if appropriate (if there is more than one physical part of a resource)

10. 10 Controlled Vocabularies for Media, Carrier Types  Closed lists in RDA, 3.2.1.3, 3.3.1.3  If more than one term appropriate, two choices: Give all: repeat field (and use $3 to show which bit you’re referring to) Pick the term representing the predominant or most substantial content, media, carrier NLNZ preliminary policy is to record the terms for the most substantial parts of a resource. This might be only one term, but could be more than one. We have a definition of substantial in our policy document  If the information is unknown, record “unspecified” (maybe for CiPs?)  If no term is appropriate, record “other” and notify LC via a message to LChelp4rda@loc.gov perhaps notify the rest of Collection Description first? Via CatSubs?LChelp4rda@loc.gov

11. 11 Media Type  LC & NLNZ CORE ELEMENT not core in RDA  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

12. 12 Carrier Type  CORE ELEMENT i.e. RDA 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

13. 13 Example: MARC 337 & 338 Fields Book: 337 $a unmediated $2 rdamedia 338 $a volume $2 rdacarrier

14. 14 Extent  LC CORE ELEMENT RDA core if item is complete or extent is known NLNZ hasn’t record a decision yet  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

15. 15 Recording Extent  Give if the resource is complete or if the total extent is known  RDA 3.4.1.3 Give number of units and appropriate term:  Sometimes a term from carrier type list (RDA 3.3.1.3)  Several categories covered by exceptions (e.g., text, still images, notated music, cartographic resources)  Another term to designate the type of unit if term not in list, or prefer a term in common use (RDA 3.4.1.5) NLNZ has not developed a set of preferred or common use terms yet.

16. 16 Extent of Text  Single Volume with Numbered Pages, Leaves, or Columns (3.4.5.2)  Single Volume with Unnumbered Pages, Leaves, or Columns (3.4.5.3) RDA lists three options LCPS 3.4.5.3 continues AACR2 practice  For LC original cataloging, usually follow method c) 1 volume (unpaged) NLNZ will follow method a) (& count) for non-juvenile material that is less than 50 pages and otherwise method c)

17. 17 Extent of Text (contd.)  NLNZ defines Substantial as 20% or more of resource (3.4.5.3.1)  Complicated or Irregular Paging (3.4.5.8) RDA lists three options LCPS 3.4.5.3 continues AACR2 practice  For LC original cataloging, usually follow method c) 1 volume (various pagings) NLNZ will follow method a) (& record each sequence) for non-juvenile resources that are less than 50 pages, otherwise method c) will be followed

18. 18 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”

19. 19 Dimensions RDA 3.5  LC CORE for resources other than serials and online electronic resources & NLNZ? We haven’t been explicit  “Measurements of the carrier or carriers and/or the container of a resource”  Rounded up to next whole centimeter  “cm” and “mm” are symbols, not abbreviations use ISBD full stop after symbol only if a 490 field appears in the record – “ Field 300 ends with a period if there is a 4XX in the record; otherwise it ends with a period unless another mark of punctuation or a closing parentheses is present” – I read this to mean that there will almost always be a full stop at the end of the 300, Unless the field ends with a parenthesis and there is no 4XX field in the record  MARC 300 $c

20. 20 Examples: MARC 300 $a, 337-338 Book: 300 $a 123 pages, 28 unnumbered pages 337 $a unmediated $b n $2 rdamedia 338 $a volume $b nc $2 rdacarrier Music CD: 300 $a 1 audio disc {or: 1 CD} 337 $a audio $2 rdamedia 338 $a audio disc $2 rdacarrier $b is optional (for LC). Codes are on MARC website. NLNZ has not decided about codes yet.

21. 21 Example: MARC 300 $a, 337&338 Book with accompanying CD of lecture: $3 and $e 300 $a 244 pages... + $e 1 CD 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 $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. * The use of $3 in this example is optional. NLNZ has not made any decisions about accompanying material yet

22. 22 Unit 3: Other Elements of Manifestations and Items Acquisition and Access Information (RDA Chapter 4)  Terms of availability (RDA 4.2)  Contact information (RDA 4.3)  Restrictions on access (RDA 4.4)  Restrictions on use (RDA 4.5)  Uniform Resource Locator (RDA 4.6)

23. 23 Terms of Availability  RDA 4.2  LCPS: Generally do not provide prices or other availability information except for rental scores or rental performance materials  NLNZ policy – see document – continue current practice for NZNB titles. Example: 020 $a 0460044524 : $c $20.00

24. 24 Contact Information  RDA 4.3  Record contact information for a publisher, distributor, etc., if it is considered to be important for acquisition or access  See NLNZ policy document for full details Examples: http://www.HaworthPress.com Alabama Department of Archives and History. 624 Washington Avenue, Montgomery, AL 36130-0100

25. 25 Restrictions on Access  RDA 4.4 NLNZ core for items with legally binding restrictions (e.g. Office of Film and Literature Classification ratings)  Record all restrictions on access to the resource, including the nature and duration of the restriction, as specifically as possible. The absence of restrictions may also be noted if it is considered to be important Example: 506 ‡a R18. Indecent in the hands of persons under 18 years of age, ‡b Indecent Publications Tribunal.

26. 26 Restrictions on Use  RDA 4.5 NLNZ core when information on use restrictions is supplied (e.g. with digitised materials)  LCPS: The CORE requirement is limited to the non-General Collections at the Library of Congress  MARC 540 field  Example: This file is provided for research purposes only and must not be reproduced without the permission of the Alexander Turnbull Library.

27. 27 Uniform Resource Locator  LC CORE ELEMENT  RDA 4.6  Address of the remote access resource being catalogued  LCPS 4.2.1.3 - If there is more than one Uniform Resource Locator for the resource, record all  MARC 856 field

28. 28 Uniform Resource Locator  Changes Requiring the Addition, Revision, or Deletion of a Uniform Resource Locator  LCPS 4.6.1.4 provides LC practice for two situations: When the original URI is no longer active When the original URI is still active, but the original resource is no longer available NLNZ has a policy for this too, but we need to review it in relation to archived resources as the LCPS has an interesting approach.

29. 29 I’ve identified the physical object – now what?

30. 30 Works in FRBR  Group 1 entity  Abstract, intellectual content  Embodied in a manifestation (i.e. the physical objects we’ve been describing up till now)

31. 31 Why do we need to identify the work?  To bring works together that users might think are different  To distinguish works that might appear to be the same  To show that different versions or formats of the same work are available to users

32. 32 Unit 4: Introduction to Works  Where are the Instructions?  Naming the work  Terminology  Authorized access points for works  Sources

33. 33 Where are the Instructions?  Generally, the instructions for identifying works 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”

34. 34 “Naming the Work”  Just like ‘naming’ persons and corporate bodies (and now, families)  Similar to AACR2 concept of “main entry” broader than the concept of “uniform title”  The “name” of the work is used when a reference to the work is needed

35. 35 Decisions on … Bibliographic or Authority Data?  RDA does not include the distinction between bibliographic records or authority records, so we need to decide where we will record information about works  NLNZ Policy?: Always identify the work in the bibliographic record ( we’ll cover how this works a little later) NACO cataloguers will cover when/whether we create authority records for works

36. 36 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 (but only if you are creating an authority record, doesn’t apply in bibliographic records) “see references” in AACR2

37. 37 Terminology related to Works (continued)  Authorized Access points for Works (6.27.1.1 - 6.27.1.8) = A standardized access point representing a work

38. 38 Constructing an authorized access point  Start with Preferred title  Add Authorized access point for the creator before the preferred title (if the work has a creator)  Add Additional data elements after the preferred title (if needed to identify the work) (6.27.1.9)  [ Creator] + Preferred Title + [Additions]

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

40. 40 Sources of Information – Sources for Other Elements (6.1.1)  For all other identifying attributes of works (i.e. other than the title itself)  Take the information from any source

41. 41 Unit 5: Elements for Works  Preferred Title for the Work  Entities Responsible for a Work  Compilations vs. Collaborations  Authorized access points for works in MARC bibliographic records

42. 42 Preferred Title for the Work  CORE ELEMENT  General instructions  Specific instructions

43. 43 General Instructions on Recording Titles (6.2.1)  Scope: “… by which a work is known”  Sources: “… from any source”  Capitalization  Numbers  Diacritics  Articles  Spacing  Abbreviations

44. 44 Instructions on Recording Preferred Titles (6.2.2)  Scope and sources 6.2.2.1 – 6.2.2.2  Choosing preferred titles 6.2.2.3 – 6.2.2.7  Recording preferred titles 6.2.2.8 – 6.2.2.10

45. 45 Preferred Title for the Work – Specific Categories  some musical works (6.14.2)  some legal works (6.19.2)  some religious works (6.23.2)  some official communications (6.26.2)

46. 46 Other types of works & preferred titles (RDA has special rules)  Parts of a work (6.2.2.9) Authorized access point (6.27.2)  Compilations (6.2.2.10) Authorized access point (6.27.1.4)  Collaborations (no special rules for choosing titles) Authorized access points (6.27.1.3)

47. 47 Preferred title: 6.2.2.4  In the original language  As known through either “resources embodying the work” (i.e. manifestations) OR Reference sources

48. 48 Choosing the preferred title: Examples: what is the preferred title?  Everyday / Peter Gordon First published in 2012  Cléo et Sam : une amitié au-delà de la mort / Helen Brown Titre original: Cleo, How an Uppity Cat Helped Heal a Family. Première publication en 2009 par Allen & Unwin

49. 49 Our examples?  Everyday  Cleo

50. 50 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”

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

52. 52 Entities Responsible for a Work – Sources  Preferred sources of information  Other statements appearing prominently in the resource  Information appearing only in the content  Other sources

53. 53 Creator (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 (just like AACR2)

54. 54 Our examples?  Peter Gordon  Authorised access point Gordon, Peter, 1963-  Helen Brown  Authorised access point Brown, Helen, 1954-

55. 55  “ … contributing to the realization of a work through an expression”  Editors, translators, illustrators, arrangers of music, performers, writers of commentary, and others  Covered in next module on Expressions What About Contributors?

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

57. 57 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; (e.g. compilers of bibliographies, but not editors of collections)  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. (e.g. adaptations)

58. 58 Corporate Bodies as Creators  Categories of works (RDA 19.2.1.1.1) Similar (!! – identical!) to AACR2 21.1B2  Corporate body takes precedence over a first-named person or family as creator this is the same in AACR2 (e.g. annual report of corp. body with named author still under corp body)  LCPS, similar to RI for 21.21B2  RDA 19.2.1.1.2 on government and religious officials as creators

59. 59 Compilations and Collaborations  Important distinction – also important in AACR2  Determines how each is ‘identified’  Compilations RDA 6.27.1.4  Collaborations RDA 6.27.1.3

60. 60 How to Decide? If the publication doesn’t tell you specifically  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

61. 61 Example: Multiple Creators -- 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: NLNZ still to determine policy – not required by RDA No change from AACR2, except for ‘added entries’

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

63. 63 Example: Multiple Creators -- No Principal Responsibility 100 $a Brown, Susan. Change from AAACR2 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: NLNZ policy to be determined RDA:precede preferred title by first-named creator

64. 64 Authorized access points when there is a creator 6.27.1.2  Authorized access point for creator Followed by  Preferred title for the work Example: Paul, Gregor. Top 10 of everything rugby

65. 65 Our examples:  Gordon, Peter, 1963-. Everyday  Brown, Helen, 1954-. Cleo Does the authorized access point identify the work? Yes – the access point is complete No – look at the rules for additions to access points for works (next week!)

66. 66 What about MARC?  Title statement for manifestation: 245 10 $a Everyday /$c Peter Gordon  Authorized access point for work: Gordon, Peter, 1963-. Everyday  What parts of the authorised access point are already present in the bibliographic record? Everyday  Add missing parts in appropriate MARC field 100 1 $a Gordon, Peter, $d 1963- 245 10 $a Everyday /$c Peter Gordon

67. 67 Cleo  Title statement: 245 10 $a Cléo et Sam : une amitié au-delà de la mort / Helen Brown  Authorised access point for the work Brown, Helen, 1954-. Cleo  What parts of the authorised access point are already present in the bibliographic record? None  Add missing parts in appropriate MARC field 100 1 $a Brown, Helen, $d 1954- 240 10 $a Cleo 245 10 $a Cléo et Sam : une amitié au-delà de la mort / Helen Brown

68. 68 And another one  Title statement for manifestation: 245 00 $a Making global self-regulation effective in developing countries /$c edited by Dana L. Brown and Ngaire Woods. Authorized access point for work: Making global self-regulation effective in developing countries  What parts of the authorised access point are already present in the bibliographic record? All of it.  No missing parts to add, so there is nothing to change in your manifestation record, except to check first indicator in the 245.

69. 69 Practice  Construct authorized access points for the works represented in the manifestations you’ve worked in in earlier modules  Try and look for a variety of situations to test the steps in this process work out where the data would go in MARC  There is a new template that includes work elements in the RDA training folder on the G drive.