1. Or, Life after AACR2 1

2. A new standard for resource description & access, designed for the digital worldJoint Steering Committee for Development of RDA (JSC)-- http://www.collectionscanada.gc.ca/jsc/rda.html 2

3. The JSC plans for the new guidelines to be adaptable for use with any database structure, not just MARC21, using XML or its offshoots, Dublin Core, or a future format not yet even invented. 3

4. RDA will be an online resource Hyperlinks will take users from place to place within the chapters. Example: 6.17.3.0.2 For other types of musical expressions, construct the preferred access point following the instructions given under 6.1.3. 4

5. Final draft is due in early 2009, but LC may not implement until late in the year. LC training organizations are planning to offer training to RDA users. 5

6. Mappings to various encoding & presentation schemes RDA will provide mappings for use with MARC21, ISBD, & DC (Dublin Core) 6

7. The rules are based on and aligned with Functional Requirements for Bibliographic Records (FRBR) and the still-developing Functional Requirements for Authority Data (FRAD) 7

8. Each RDA chapter will directly relate to a FRBR user task: Find Identify Select Obtain 8

9. So what is FRBR, anyway? a model for bibliographic description developed by the IFLA in the 1990s. includes a conceptual model of entities and relationships and attributes identifies specific user tasks that bibliographic records are intended to fulfill: find, identify, select, obtain; And, recommends a set of elements for inclusion in national bibliographic records. 9

10. How will RDA use FRBR? RDA will include lots of FRBR terminology (for example, use of the names of bibliographic entities: work, expression, manifestation, and item). RDA will use the FRBR attributes as the basis for specific data elements in bibliographic descriptions (person, family, corporate body, concept, object, event or a place). It will address relationships between attributes, and will use the FRBR user tasks (Find, Identify, Select, Obtain) as the basis for defining a set of mandatory data elements. 10

11. So, whats a work? Hamlet is a work, as Shakespeare first imagined it in his head. 11

12. Whats an expression? The play as Shakespeare first wrote it is his expression of his original idea. 12

13. A manifestation, the 1605 edition of the play, printed in London : 13

14. Another manifestation would be a spoken word recording of that 1605 text of the play 14

15. A copy of that 1605 edition is an item. 15

16. Or, another way of looking at it? Work is a title Expression is a format Manifestation is an edition Item is a copy 16

17. So, whats an attribute? An element associated with an entity (work, expression, manifestation, item, etc Works, manifestations, expressions, & items all have attributes and relationships between them. And so do persons, families, corporate bodies, concepts, objects, events, & places. For instance, an attribute of William Shakespeare might be his birth and death dates, 1564-1616. 17

18. Heres some more new RDA terminology AACR2 termsRDA terms HeadingAccess point Authorized headingPreferred name Main entryPrimary access point Added entryAccess point Authority controlAccess point control Uniform titlePreferred access point representing a work, expression, manifestation 18

19. What else could change? Terminology for Media, Carrier, and Content Types to replace GMDs File characteristics for digital materials Video format characteristics Custodial information for archival resources Braille characteristics 19

20. RDA will be divided in sections Sections 1-4 will give guidelines for recording attributes. Sections 5-10 will give guidelines for recording the relationships between and among the attributes. Each section will have one or more chapters. The guidelines will designate which descriptive elements are required and which are optional. For a list of required elements, see http://www.collectionscanada.gc.ca/jsc/docs/rdafaq- requelements-20080103.pdf 20

21. Sections 1-4 will cover attributes. SectionAttribute 1Manifestation and item 2Work and expression 3Person, family, & corporate body 4Concept, object, event, & place 21

22. Sections 5-10 will cover the relationships among the various attributes. SectionRelationship 5Between work, expression, manifestation, & item 6To persons, families, & corporate bodies 7To associated concepts, objects, events, & places 8Between works, expressions, manifestations, & items 9Between persons, families, & corporate bodies 10Between concepts, objects, events & places 22

23. The new rules are NOT intended to be used with any SPECIFIC record structure, such as MARC21. They will flexible enough for bibliographic description in libraries, archives, museums, databases, etc. 23

24. We can fit RDA into MARC21 Our existing MARC21 records will not have to be modified either. Our old records and new RDA records will sit side by side in the same catalogs. There may be some changes to the MARC21 codes for GMDs and SMDs, and for electronic resources, but those arent out yet. 24

25. 25

26. A new cataloging standard will Encourage use as a content standard for metadata schema Encourage international applicability, for a much more global, non-English specific standard 26

27. A Task Group is developing A defined RDA Element analysis in Dublin Core, and RDA Value Vocabularies for use in the Semantic Web, using RDF/RDFS/SKOS technologies, Thus making RDA a very Web-compatible standard The DC vocabulary is already available at: http://www.collectionscanada.gc.ca/jsc/docs/5rda- elementanalysisrev.pdf http://www.collectionscanada.gc.ca/jsc/docs/5rda- elementanalysisrev.pdf 27

28. What will RDA include? Guidelines to govern resource description Example: 5.3.1. When recording data identifying a work or expression, include as a minimum the elements listed below that are applicable to that work or expression. Title Preferred title for the work Identifier Identifier for the work Identifier for the expression 28

29. Guidelines to govern choice & form of access points Example: 6.1.1.1.1. If one person, family, or corporate body is responsible for creating the work, construct the preferred access point representing the work by combining (in this order): a) the preferred access point for that person, family, or corporate body, formulated according to the guidelines and instructions given under 9.1.1, 10.1.1, or 11.1.1, as applicable b) the preferred title for the work, formulated according to the instructions given under 6.2. 29

30. It will include guidelines for references 9.3.1.3.1. If the preferred name or names for an individual are pseudonyms, and he or she does not use his or her real name as a creator or contributor, record the individuals real name, if known, as a variant name. Cross, Marian Evans (Pseudonym recorded as preferred name: Eliot, George) Dudevant, Amandine-Aurore-Lucile (Pseudonym recorded as preferred name: Sand, George) Munro, Hector Hugh (Pseudonym recorded as preferred name: Saki) Jackson, Curtis 30

31. And guidelines for relationships 29.3.1. When recording relationships between persons, families, and corporate bodies, include as a minimum the elements listed below that are applicable to the related person, family, or corporate body. Name Preferred name for the [person, family, or corporate body] Identifier Identifier for the [person, family, or corporate body] 31

32. There will be plenty of examples-- Hemingway, Ernest, 1899-1961. Sun also rises Cassatt, Mary, 1844-1926. Children playing on the beach Barner (Family). Barner family newsletter Coldplay (Musical group). Parachutes Swift, Jonathan, 1667-1745. Tale of a tub (Originally published anonymously but known to be by Jonathan Swift) 32

33. What will RDA not include? Instructions for creating classification or cutter numbers Instructions for use of such data structures as MARC21, or Information about mark-up languages such as XML and its offshoots. RDA will include guidelines for creating subject headings, in Section 10 and Chpt. 23, but they wont be part of the first rollout. 33

34. Each sections chapters will be associated with specific FRBR user tasks. This will help catalogers think in terms of enabling users to succeed at the FRBR user tasks, and Help system designers create new resource discovery tools that will house these FRBR-based records. 34

35. RDA Planned Appendices Appendix A. Capitalization Appendix B. Abbreviations Appendix C. Initial articles Appendix D. Record syntaxes for descriptive data Appendix E. Record syntaxes for access point control data Appendix F. Additional instructions on names of persons Appendix G. Titles of nobility, terms of rank, etc. Appendix H. Conversion of dates to the Gregorian calendar Appendix J. Relationship designators: Relationships between a resource and persons, families, and corporate bodies associated with the resource Appendix K. Relationship designators: Relationships between works, expressions, manifestations, and items Appendix L. Relationship designators: Relationships between persons, families, and corporate bodies Appendix M. Relationship designators: Relationships between concepts, objects, events, and places* 35

36. Want to read the drafts they already have written now? Go to http://www.collectionscanada.gc.ca/jsc/rda.ht ml#drafts http://www.collectionscanada.gc.ca/jsc/rda.ht ml#drafts 36

37. Best way to prepare for RDA: Get familiar with the principles, concepts, & terminology of FRBR FRAD, & the Statement of International Cataloging Principles 37

38. Where to find info on these concepts FRBR – http://www.loc.gov/cds/FRBR FRAD – http://www.ifla.org/VII/d4/htmlFRANAR- ConceptualModel-2ndReview.pdf Statement of International Cataloguing Principles – http://www.loc.gov/loc/ifla/imeicc/pdf/statement- draft3_apr06cleancopy.pdf 38

39. Where to find me Michele Seikel michele.seikel@okstate.edu 39