The Content Standard, US RDA Test, Your Preparations

1. The Content Standard, US RDA Test, Your Preparations Judith A. Kuhagen Policy and Standards Division, Library of Congress Special Library Association Philadelphia -- June 14, 2011

2. Background and Structure of RDA

3. What’s wrong with AACR? Increasingly complex Lack of logical structure Mixing content and carrier data Hierarchical relationships missing Anglo-American centric viewpoint Written before FRBR Not enough support for collocation Before Internet and well-formed metadata Based on slide from Ann Chapman, UKOLN

4. 1997 International Conference on the Principles and Future Development of AACR Toronto, Canada JSC invited worldwide experts Issues leading to RDA Principles Content vs. carrier Logical structure of AACR Seriality Internationalization

5. AACR3

6. Metadata groups IFLA: models, principles, ISBD ISSN ONIX (publishers): content, etc., types Dublin Core, W3C, IEEE/LOM, Semantic web: data modeling MARBI: MARC revisions Library groups, e.g., Law: treaties Hebraica: Bible Manuscripts and archives: DACS Moving image and music: AMIM Still image: CCO JSC collaborations

7. GOALS: RDA will be … A new standard for resource description and access Designed for the digitalworld Optimized for use as an online product Description and access of all resources All types of content and media Resulting records usable in the digital environment (Internet, Web OPACs, etc.)

8. RDA based on IFLA’s international models and principles • Functional Requirements for Bibliographic Records (FRBR; 1998) • Functional Requirements for Authority Data (FRAD; 2009) • Statement of International Cataloguing Principles (ICP; 2009) the successor to the Paris Principles

9. General Principles (ICP) Convenience of user Representation Common usage Accuracy Sufficiency and necessity Significance Economy • Consistency and Standardization • Integration • Defensible, not arbitrary • If contradict, take a defensible, practical solution.

10. FRBR: Find Identify Select Obtain FRAD: Find Identify Contextualize Justify Addresses user tasks • ICP’s highest principle = “convenience of • the user”

11. FRBR’s Entity-Relationship Model Entities Relationships Attributes (data elements) National level required elements relationship One Entity Another Entity

12. FRBR’s Entity-Relationship Model Person Work created was created by Shakespeare Hamlet

13. Terminology • FRBR & FRAD “attributes” = “elements” in RDA • FRBR and FRAD Group 1 entities (bibliographic resources) – aka “WEMI”: • Work • Expression • Manifestation • Item

14. FRBR “Group 1” entities “Book” • Door prop (item) • Publication • at bookstore -- • any copy • (manifestation)

15. FRBR “Group 1” entities “Book” • Who translated? • (expression) • Who wrote? • (work)

16. Group 1 Work is realized through Expression is embodied in Manifestation recursive is exemplified by one Item many

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

18. Group 2 Person Family Corporate Body Work FRBR Expression Manifestation Item is owned by is produced by is realized by is created by many

19. FRBR Entities Group 3:Subjects of works Groups 1 & 2 plus Concept Object Event Place

20. Group 3 Work Expression Manifestation Item Person Corporate Body Concept Object Event Place Work has as subject FRBR Family has as subject has as subject many

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 André 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

22. Person 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 André 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 Work

23. Shakespeare, William, 1564-1616. Hamlet. French. Expression 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 André 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

24. 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 André 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

25. 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 André 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

26. Collocation Cervantes Objectives of a catalog: display Don Quixote • All the works associated with aperson, etc. • All the expressions of the same work • All the manifestations of the same expression • All items/copies of the same manifestation Exemplary novels English Text French German Spanish Madrid, 1979 Library of Congress Copy 1 Green leather binding

27. Relationships Pathways to Related Works Cervantes Author of Wasserman Author of Derivative works Don Quixote The Man of La Mancha Exemplary novels English Text French Movies … German Spanish Subject Madrid, 1979 Library of Congress Copy 1 Green leather binding

28. Internet “Cloud” Databases, Repositories Services VIAF LCSH Web front end

29. Current Cataloging Environment Web-based Wide range of information carriers More complex content Metadata (bibliographic information) Created by a wider range of personnel in and outside libraries Sometimes part of the resource Element-based metadata schemas Dublin Core, ONIX, etc.

30. Database/format Scenarios Based on Gordon Dunsire’s slide Bib record (flat-file) Z 666.7 .L55 2009 Lee, T. B. Cataloguing has a future 1 sound disc Spoken word. Donated by the author. 1. Metadata

31. Database/format Scenarios Based on Gordon Dunsire’s slide Bib record (flat-file) 100 01 $a Lee, T. B. 245 00 $a Cataloguing has a future 300 $a 1 sound disc 500 $a Spoken word. 561 1 $a Donated by the author. 650 0 $a Metadata

32. Database/format Scenarios Based on Gordon Dunsire’s slide FRBR registry (IFLA) Future record RDA element registry FRBR record Bib record (flat-file) Bib record (description) Work information Name authority record Author: Lee, T. B. Title: Cataloguing has a future Name: Work title: Cataloguing has a future Identifier: … Content type: Spoken word Expression information Carrier type: Audio disc Subject authority record Subject: Metadata Manifestation information Provenance: Donated by the author Label: Identifier: … ONIX RDA content type registry Item information Label: Spoken word Identifier: … RDA carrier type registry

33. Linked Data Work information Name authority record Author: Subject: Name: Lee, T. B. Work Title: Cataloguing has a future Cataloguing has a future Identifier: … Expression information Subject authority record Content type: Manifestation information Metadata Label: Title: Cataloguing has a future Identifier: … Carrier type: RDA content type registry Item information Provenance: Donated by the author Label: Spoken word RDA carrier type registry Identifier: … Audio disc

34. Package for Data Sharing Communication format record Work information Name authority record Author: Subject: Name: Lee, T. B. Lee, T. B. Work Title: Cataloguing has a future Cataloguing has a future Identifier: … Expression information Content type: Subject authority record Manifestation information Metadata Metadata Label: Title: Cataloguing has a future Identifier: … Carrier type: RDA content type registry Item information Provenance: Donated by the author Label: Spoken word Spoken word Identifier: … RDA carrier type registry Audio disc Audio disc

35. RDA is a contentstandard • Not a display standard (as is AACR2) • Does have appendix D for ISBD and appendix E for AACR2 style for access points • Not an encoding standard • Use whatever schema you prefer (MARC 21, Dublin Core, etc.)

36. Mappings, etc., for transition • RDA Appendix D mappings: • ISBD to RDA • MARC 21 bibliographic format to RDA • RDA Appendix E: • Presentation and punctuation of access points • MARC 21 authority format mapping to RDA • Other mappings in the RDA Toolkit

37. Access to RDA • Online RDA Toolkit -- information at http://www.rdatoolkit.org/ (also webinars, blog, training information) • Printed text version of RDA • Printed version of the RDA element set (a subset of the RDA content) in summer 2011

38. Implementation scenarios • Scenario 3: “Flat file” database structure (no links) • Scenario 2: Linked bibliographic and authority records • Scenario 1: Relational/object-oriented database structure (to get full benefit of RDA) • Does not mean cataloger creates 4 records (WEMI) for each resource • JSC document on scenarios: http://www.rda-jsc.org/working2.html#ed-2 

39. Moving beyond MARC ... • “Transforming our Bibliographic Framework” -- a statement from Deanna Marcum http://www.loc.gov/marc/transition/news/framework-051311.html • “Bibliographic Framework Transition Initiative” -- can join the BIBFRAME list http://www.loc.gov/marc/transition/

40. RDA “new and different”-- an overview

41. For wider scope of resources • Response to what’s being acquired in libraries • More elements for non-printed text resources • More elements for non-text resources • More elements for unpublished resources • If a specialized library or collection, supplement RDA with specialist manuals

42. More international • Focus on local userneeds • Choice of agency preparing the description: • Language of additions to access points • Language of supplied data • Script and transliteration • Calendar • Numeric system

43. Core elements in RDA (not areas) • Based on attributes mandatory for a national level record in FRBR and FRAD • More use of pre-existing data (e.g., ONIX) • Easier reuse of well-formed metadata • Core elements listed as a group in RDA 0.6 and separately in appropriate chapters • Agency, consortium, etc., can add others

44. “Core-ness” identified at element level in RDA • If always a core element (if applicable and available), label CORE ELEMENT appears below element name • If use as a core element depends upon the situation, the label CORE ELEMENT is followed by an explanation of the situation

45. [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)]

46. [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)]

47. Other choices in RDA • Alternatives and options • “or” instructions • “agency preparing …” instructions If LC implements RDA, LC will reconsider additional core elements, other choices, and policy decisions.

48. Has controlled vocabularies • Only a few closed: content, media, and carrier types; mode of issuance; etc. • Most are open: cataloger can supply term if needed term not in list • Vocabularies being registered on the Web (http://metadataregistry.org/rdabrowse.htm) -- goal of multiple languages and/or scripts • Want vendors to provide drop-down menus

49. RDA Structure General introduction Identifying elements(entities and their attributes) Ch. 1-7: work, expression, manifestation, item Ch. 8-16: person, family, corporate body, place Relationships:ch. 17-22, 24-32 Appendices Glossary Index

50. RDA structure • Not by class of materials: no separate chapters for books, printed music, etc. • Overarching principles applicable to all • Basic goals: identify and relate (from FRBR/FRAD user tasks and ICP) • Chapters: separate elements for goals • Assemble those elements when need authorized access points (instructions at end of chapters 6, 9-11)