RDA Resource Description and Access

1. RDAResource Description and Access

2. RDA: Resource Description and Access • The successor to AACR2 • To be released in 2009 • Primarily web-based, but also in but also in print form at a later stage • Text is not read in a linear fashion • Text is repeated whenever needed to support Hyperlink • Based on concepts from FRBR (Functional Requirements for Bibliographic Records)

3. RDA: Who is responsible? • Joint Steering Committee (JSC) • American Library Association (ALA) • Australian Committee on Cataloguing (ACOC) • British Library (BL) • Canadian Committee on Cataloguing (CCC) • Chartered Institute of Library and Information Professionals (CILIP) • Library of Congress (LC) • Assisted by JSC Secretary and RDA Project Manager • JSC reports to the Committee of Principals (CoP)

4. RDA Acronyms • FRBR • Functional Requirements for Bibliographic Records • FRAD • Functional Requirements for Authority Data • FRSAR • Functional Requirements for Subject Authority Records • ISBD • International Standard Bibliographic Description

5. Adopting RDA • Who is RDA for? • Libraries • Metadata community • Museums, archives, educators, publishers • Dublin Core compatibility • What about training? • NLA will be working with various training agencies in Australia to make the materials available and accessible to all users

6. New standard : why? • Simplify rules • Encourage use as a content standard for metadata schema • Encourage international applicability • Goes past AACR2 in cataloguing digital resources • Flexibility to accommodate newly emerging resources • Support flexible catalogues • It’s about recording data, not the presentation of this data • Provide more consistency • Rules will be applied independent of any particular syntax or structure

7. New standard : why? – cont. • Emphasis on helping users by providing information • they need to find, identify, select and obtain information resources • Recognizes that libraries now operate in a digital web based environment. • Support integration of library catalogue records with those produced by other metadata communities.

8. New standard : why? – cont. • Address current problems • Principle-based • To build cataloguer’s judgment • Encourage application of FRBR/FRAD

9. Key FRBR concepts • An entity relationship model • FRBR Group 1 entities: • Work • Expression • Manifestation • Item • FRBR Group 2 entities: • Persons, corporate bodies • FRBR user tasks: • Find, Identify, Select, Obtain

10. is realized through is embodied in is exemplified by FRBR Entity Relationships Work Expression Manifestation one Item many Slide by Barbara Tillett, LC Based on the slide by Barbara Tillett, LC

11. FRBR Entity Relationships Is created by Person or Corporate body Work Is realized by Person or Corporate body Language edition of the text Videorecording of the text Print version Videocassette Abridged edition version DVD Online version is produced by Person or Corporate body Work Expression Manifestation Item Copies owned by the library

12. The “idea” of TheLord of the Rings: e.g., the novel; the “movie”; the score. Work Group 1 entities The realisation of The Lord of the Rings in one or more modes of expression: e.g. “English text”, “French translation”, “performance”, the director’s cut. Expression Manifestation The embodiment of TheLord of the Rings: e.g. CDaudio book ISBN-13: 978-0007141326 ; or Audio Cassette  ISBN 0007127448 Item An exemplar of a manifestation of, “The Lord of the Rings”, e.g.: My copy!. Slide by Alan Danskin, British Library

13. FRBR Benefits • Collocation • Better organization of the catalogue • Easier cataloging • The ability to customize rules to suit a specific type of material. RDA will make it easier to identify basic instructions and ignore detailed instructions that are required for a more complex level of description • The ability to retrieve rules for unfamiliar formats and save them as a workflow • The ability to add users’ notes online and integrate rule interpretations and any institution policies

14. FRBR Benefits • Reduction in cataloging load • Work only catalogued once for all expressions of it • Expression only cataloged once for all manifestations of it • Item cataloging (already simple) remains the same • Circulation • Place holds at Work or Expression level rather than only at Manifestation level

15. Critical Differences (Changes) Between AACR2 and RDA • Level of description • Comprehensive description • Analytical description • Multilevel description • Structure • GMD/SMD [content: carrier or the physical format] • Includes the carrier and type of media • Music CD might be displayed as [music recording: CD audio], and • Videocassette might be displayed as [moving image: video VHS] • Map or Atlas on CD-ROM might be displayed as [cartographic resource: digital] • Global edit and replace function will be able to map the existing GMD to its new value in the new field

16. Critical Differences (Changes) Between AACR2 and RDA – cont. • Punctuation • punctuation not integralBUT • Can be mapped to existing MARC punctuation or any other Schema used (such as Dublin Core, .HTML, etc.) • Retrospective cataloguing is not required as there will be no significant changes • Compatible with AACR2 • Instructions are not different but grouped and presented differently • Retrospective adjustment will be minimal – only where rules on access point creation have changed • Terminology

17. Further Changes: Rules for Access Points • Few abbreviations will be used in RDA • Bible. O.T. • After RDA: Bible. Old Testament • Bible. O.T. Job • After RDA: Bible. Job • Rule of three • Selections • Lacking collective title

18. AACR2 terms Heading Authorized heading Main Entry Added Entry Authority control Uniform title RDA terms Access point Preferred Access point Primary Access point Secondary Access point Access point control Preferred title Name of the work (to include name of creator when applicable) New Terminology

19. Mandatory Elements of Description • Title • Statement of responsibility • Edition • Numbering • Publisher, etc. • Date of Publication • Title proper of series • Numbering within series • Resource identifier • Form of carrier • Extent • Scale of cartographic content • Coordinates of cartographic content

20. RDA & MARC21 • AACR2 and MARC 21 are two different standards designed for two different purposes. • AACR2 is largely a content and display standard while MARC 21 is an encoding standard. • RDA will contain guidelines for choosing and recording data to include in bibliographic and authority records. • MARC 21 is one possible schema for encoding records created using RDA, but it will also be possible to encode records created using RDA in other schemas, such as MODS or Dublin Core.

21. Examples • Harry Potter and the philosopher’s stone / J.K. Rowling. WORK • Language material – English EXPRESSION • Harry Potter and the philosopher’s stone / J. K. Rowling. London : Bloomsbury, 1999 MANIFESTATION • Harry Potter and the philosopher’s stone / J. K. Rowling. London : Bloomsbury, 2000. Edition: Abridged ed. MANIFESTATION • Harry Potter and the philosopher’s stone / J. K. Rowling. London : Church House Publishing, 2007. Edition: Large print ed. MANIFESTATION • Harry Potter and the philosopher’s stone [Online] MANIFESTATION

22. Examples • Sound recording EXPRESSION • Harry Potter and the philosopher’s stone [Audiocassette] MANIFESTATION • Harry Potter and the philosopher’s stone [CD audio] MANIFESTATION • Harry Potter and the philosopher’s stone - the movie WORK • Videorecording EXPRESSION • Harry Potter and the philosopher’s stone [DVD] MANIFESTATION • Harry Potter and the philosopher’s stone [VHS] MANIFESTATION

23. RDA Structure (Content) • Part one: Recording attributes of entities • Part two: Recording relationships between entities

24. Attributes of Entities • Sect. 1. Recording attributes of manifestation and item • Sect. 2. Recording attributes of work and expression • Sect. 3. Recording attributes of person, family, and corporate body • Sect. 4. Recording attributes of concept, object, event and place

25. Relationships between entities - Internal relationships • Sect. 5 – Primary relationships between a work/expressions/manifestations/items • Sect. 6 – Relationships to persons, families or corporate bodies • Sect. 7 – Subject relationships

26. Relationships between entities - External relationships • Sect. 8 – Relationships between different works, expressions, manifestations and items • Sect. 9 – Relationships between different persons, families, corporate bodies • Sect. 10 –Relationships between concepts, objects, events and places

27. Key Dates for RDA • 30 October 2008 – full draft of content released in online product for comment • 19 January 2009 – comment period closes • Early March 2009 – JSC and CoP meet in Chicago, to finalize the review of comments revised • Third quarter 2009 – RDA is released • Last quarter 2009 – Early 2010 – CoP National libraries evaluate RDA prior to implementation

28. How to prepare for RDA • Identify local system changes required • Look for training courses advertised • Check ACOC website for any new information and useful links available http://www.nla.gov.au/lis/stndrds/grps/acoc/index.html • Up-to-date information on what is happening in Australia • Join the e-mail distribution list for RDA (i.e. RDA-l) http://www.collectionscanada.gc.ca/jsc/rdadiscuss.html Send an e-mail to the following address:LISTSERV@INFOSERV.NLC-BNC.CA In the body of the message:Subscribe RDA-L Firstname Lastname • Obtain available documents on the internet and through the National Library.

29. How to prepare for RDA • Financial and technical consideration • Budgeting • There will most likely be a sliding pricing scale depending on various elements such as number of users, size of institution, type of institution, etc. Pricing information will be announced once it is set. • Training, documentation • Record conversion costs (when needed) • System changes • Managing cataloguing documentation online • Familiarisation with RDA online

30. Online tool • Browse, search, display • Links within and beyond RDA • Annotations and bookmarks • Updates • Profiles – persistent settings • Views - e.g. core elements • Workflows – step-by-step processes

31. Product Development Snapshot Nannette NaughtJune 28, 2008 A Visual Tour of the Development Process

32. RDA Home: Quick Search

33. RDA On Ramp: AACR2

34. RDA On Ramp: Mappings

35. RDA On Ramp: Core View

36. RDA On Ramp: Advanced Search