1. Changes from AACR2 for Texts Barbara B. Tillett, Chief, Policy and Standards Division For LC Digital Futures and You Jan. 12, 2010

2. 2 General overview Changes: – from AACR2 or from AACR2 practice –MARC 21 changes Represents LC practice for the RDA Test – some decisions still tentative/in process Specific details in training sessions for LC participants in the RDA Test

3. 3 RDA Test (United States) For more information, go to the Web site maintained by the RDA Test Coordinating Committee: http://www.loc.gov/bibliographic-future/rda/

4. 4 Reminder: foundations of RDA Functional Requirements for Bibliographic Records (FRBR; 1998) Functional Requirements for Authority Data (FRAD; 2009) IFLA Statement of International Cataloguing Principles (ICP; 2009)

5. 5 RDA structure Not by class of materials: no separate chapters for books, printed music, etc. Basic goals: identify and relate (from FRBR and FRAD user tasks ) Chapters: separate elements for goals –Assemble those elements when need access points (end of chapters)

6. 6 Summary of organization Ch. 1-7: identify the resource Ch. 8-11, 16: identify the person, family, corporate body associated with the resource Ch. 17-22: relationships between persons, families, corporate bodies and resources Ch. 24-28: relationships between resources Ch. 29-32: relationships between persons, families, and corporate bodies

7. 7 AACR2 to RDA vocabulary heading author, composer, etc. main entry uniform title see reference authorized access point creator preferred title + authorized access point for creator if appropriate 1) preferred title (+ other information to differentiate); 2) conventional collective title Variant access point

8. 8 FRBR terminology Group 1 entities: –Work, expression, manifestation, item Group 2 entities: –Person, family, corporate body Group 3 entities: –Groups 1 and 2 –Concept, object, event, place [not yet in RDA]

9. 9 RDA Test and “bridge” period Continue –MARC 21 to encode bibliographic and authority data using –ISBD punctuation and structure (appendix D) to present bibliographic data –AACR2 punctuation style (appendix E) to present name access points

10. 10 RDA core elements Core elements chosen based on FRBR- identified attributes mandatory for a national level bibliographic record to meet user tasks: –Find, identify, select, obtain “LC Core+” = the RDA core list + those other elements LC usually includes Beyond LC Core+: cataloger’s judgment

11. 11 Choices in RDA Alternatives –Something different from previous instruction Optional omissions/additions –Less or more than in previous instruction “or” instructions –Related to the resource or cataloger’s judgment “Policy of agency”: language and script of the catalog, calendar, etc.

12. 12 Cataloging documentation More emphasis on cataloger judgment Approximately 1/4 of existing LCRIs are being retained and revised/simplified for RDA (see separate sheet) Revised LCRI content, policy decisions for alternatives/options and other choices, and identification of LC Core+ will be added to RDA Online

13. 13 TOOLSRESOURCES

14. 14 Annotations and comments in a “Sticky note”

15. 15 Annotations in RDA Will contain LC practice for the RDA Test: –Retained and rewritten LCRI content –Decisions on options, alternatives, agency policy, etc., if cataloger judgment not to be applied Catalogers can add their own comments

16. 16 RDA: Workflows

17. 17 Other possible workflows Multipart monograph Reproduction of a monograph Early printed book Book with multiple languages/scripts Serial Integrating loose- leaf Integrating website Direct access electronic resource Identifying a person Identifying a corporate body Recording a relationship to a related work

18. 18 ICP “representation” principle “Take what you see” “Accept what you get” –Example: Do not abbreviate words in transcribed fields MARC 260: ABC Publishing Company – do not change to “ABC Pub. Co.” MARC 250: Third revised edition – do not change to “3rd rev. ed.”

19. 19 Representation and errors Do not correct errors in transcribed fields –No more “[sic]” or “[i.e., _____]” –AACR2 exception retained for title proper of serial or of integrating resource –Explain in note, give access point if important 245$a Teusday’s tasks. 246 $i Corrected title: $a Tuesday’s tasks 260 $a Chicago : $b Smith Pubblishers, $c 2010.

20. 20 GMD replacement Three elements: –Content type* (MARC 336) –Media type(MARC 337) –Carrier type*(MARC 338) Caution: don’t confuse Carrier type with Extent (300 $a) * Core elements

21. 21 336-338 encoding Repeat as needed to represent resource Subfield $2 for vocabulary Templates in Voyager for resources Leader/06: continue to give primary content type if more than one (336) 006: continue to give for some serials and some electronic resources

22. 22 336-338 examples Book: 300 $a 238 pages : $b … 336 $a text $2 marccontent 337 $a unmediated $2 marcmedia 338 $a volume $2 marccarrier Print serial: 300 $a volumes : $b … 336 $a text $2 marccontent 337 $a unmediated $2 marcmedia 338 $a volume $2 marccarrier

23. 23 336-338 examples Website (with maps, text, and photographs): 300 $a 1 online resource 336 $a text $2 marccontent 336 $a cartographic image $2 marccontent 336 $a still image $2 marccontent 337 $a computer $2 marcmedia 338 $a online resource $2 marccarrier Online PDF: 300 $a 1 online resource (39 pages): $b… 336 $a text $2 marccontent 337 $a computer $2 marcmedia 338 $a online resource $2 marccarrier

24. 24 Statements of responsibility Single statement naming more than one person, family, or corporate body –RDA instruction for RDA Test: transcribe as found (no longer “rule of 3”) –RDA option generally not applied by LC for RDA Test: transcribe first name and give bracketed summary about information not transcribed Related action: how many access points for those persons/families/bodies

25. 25 Statement of responsibility example 245 $a … / $c by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson. Or, if option applied: 245 $a … / $c by Susan Brown [and four others]

26. 26 Numbering for serials Transcribe terms and months as on the resource Alternative applied by LC for numerals: record numerals as found on the resource Possible to give numbering as an unformatted note (MARC 362 1#)

27. 27 Serial numbering examples Volume X, number 1 – do not change to “Vol. 10, no. 1” January 2010 – do not change to “Jan. 2010”

28. 28 Publication, etc., statements lacking information Not using “[s.l.]” and “[s.n.]”; instead: –[Place of publication not identified] –[Publisher not identified] –[Date of publication not identified] Macros in Voyager for supplied wording related to publication, distribution, and manufacture

29. 29 300 examples (Description of carrier) 300 $a v, 199 pages : $b illustrations (some color), maps, color portraits ; $c 30 cm. 300 $a 86 pages, 21 unnumbered pages : $b illustrations, 1 folded map ; $c 24 cm + $e 1 manual (5 pages ; 20 cm). 300$a volumes : $b illustrations ; $c 26 cm.

30. 30 300 examples (Description of carrier) 300 $a 1 online resource (Carrier description for an updating Web site: may choose to omit elements for file type, encoding format, and file size due to frequent changes in the integrating resource over time.) 300$a 1 CD-ROM ; ‡c 4 3/4 in.

31. 31 Series statement (4XX) Transcribe series numbering as found volume 32 – do not change to “v. 32” tomo 4 – do not change to “t. 4” Band LXXXVIII – do not change to “Bd. 88”

32. 32 Naming a work Multiple creators No longer “rule of 3” Always: –Creator with primary responsibility –If primary responsibility is shared or not stated, first-named creator Related decision: how many additional access points for other creators

33. 33 Multiple creators: example 100 $a Brown, Susan. 245 $a Heroes / $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. [AACR2: entered under title if more than three creators]

34. 34 Treaties First-named signatory for all treaties AACR2 exception retained for treaties with one government on one side and 2+ governments on other side: use single government Related decision: how many additional access points for other signatories

35. 35 Bible Do not abbreviate “Old Testament” and “New Testament” to “O.T.” and “N.T.” Use “Bible. Old Testament,” “Bible. New Testament,” and “Bible. Apocrypha” when naming those aggregate works For individual books and other groups of books, do not include name of testament after “Bible”

36. 36 “Polyglot” no longer used Access points for each language expression 245$a Antigo Testamento Poliglota : $b Hebraico, Grego, Português, Inglês. 546 $a Text in Greek, Hebrew, Portuguese, and English in columns on facing pages. 730$a Bible. $p Old Testament. $l Hebrew … 730$a Bible. $p Old Testament. $l Greek … 730$a Bible. $p Old Testament. $l Portuguese … 730$a Bible. $p Old Testament. $l English …

37. 37 Authority data elements from FRAD For persons, families, and corporate bodies (Group 2 entities) Not all will be included in authorized access points (headings) but could be available for identification and for later differentiation as needed

38. 38 Person attributes added to MARC 21 authority format 046: special coded dates 370: associated place 371: address 372: field of activity 373: affiliation 374: occupation 375: gender 377: associated language

39. 39 Non-human entities Now in scope as persons, e.g., –Miss Piggy –Snoopy LC to consider as persons? –If in the Subject file, move to the Names file

40. 40 Corporate body attributes added to MARC 21 authority format 046: special coded dates 370: associated place 371: address 372: field of activity 377: associated language

41. 41 Relationships Persons/families/corporate bodies with resources Shakespeare is the author of Hamlet Between resources Serial abc is continued by XYZ Serial Between persons/families/corporate bodies X relates to Y

42. 42 Persons … with resources Two methods to relate persons with resources: –Identifier: LC will not use alone for RDA Test –Authorized access point Relationship designators in RDA appendix I Recorded in bibliographic and/or authority data

43. 43 Examples: persons … with resources Authorized access point: 100 $a Lindgren, Astrid, $d 1907-2002. 240 $a Pippi Långstrump. $l English 245 $a Pippi Longstocking / $c Astrid Lindgren ; translated by Tiina Nunnally. 700$a Nunnally, Tiina, $d 1952- $e translator

44. 44 Between resources Three methods: –Identifier: LC will not use alone for RDA Test –Authorized access point –Description (structured or unstructured) Relationship designators in appendix J Recorded in bibliographic and/or authority data

45. 45 Examples: between resources Authorized access point (probably LC’s choice): 100 $a Brown, Dan, $d 1964- 240 $a Digital fortress. $l French 245 $a Forteresse digitale. 700 $i Translation of $a Brown, Dan, $d 1964- $t Digital fortress. Structured description : 100 $a Brown, Dan, $d 1964- 240 $a Digital fortress. $l French 245 $a Forteresse digitale. 500 $a Translation of: Digital fortress / Dan Brown. –- 1st ed. -- New York : St. Martin’s Press, 1998. –- 371 pages ; 22 cm

46. 46 Examples: between resources Unstructured description and three identifiers: 245 $a Journal of professional counseling, practice, theory, & research. 780 00 $t TCA journal ‡x 1556-4223 ‡w (DLC)93645762 ‡w (OCoLC)26906768 [780 indicators 00 = relationship “Continues”]

47. 47 Between persons … corporate bodies Two methods: –Identifier: not used alone by LC for RDA Test –Authorized access point Relationship designators in appendix K Recorded in authority data

48. 48 Examples: between persons … corporate bodies Authorized access point: 100$a Snodgrass, Quintus Curtius, $d 1835-1910 500$a Clemens, Samuel, $d 1835-1910 $i real identity

49. 49 TOOLSRESOURCES

50. 50 Webcasts for review “FRBR: Things You Should Know, But Were Afraid to Ask” http://www.loc.gov/today/cyberlc/feature_wdesc.php?rec=4554 “Cataloging Principles and RDA” http://www.loc.gov/today/cyberlc/feature_wdesc.php?rec=4327 “Resource Description and Access: Background Overview” http://www.loc.gov/today/cyberlc/feature_wdesc.php?rec=4320

51. 51 Questions about RDA? Contact PSD via email: policy@loc.gov