FRBR, FRAD and RDA: From Conceptual Models to Cataloging Applications

1. FRBR, FRAD and RDA: From Conceptual Models to Cataloging Applications Marjorie E. Bloss LACONI February 25, 2011

2. In This Presentation • Why RDA? • The Foundation for RDA (FRBR and FRAD) • RDA Content – rules and examples • RDA Toolkit – what it looks like and how it works • What’s next?

3. Anglo-American Cataloging Traditions • Began with Panizzi, Jewett, and Cutter to a number of cataloging codes through the 1960s • Attempts to develop one set of cataloging rules for both the US and the UK • Development of Lubetzky’s “Paris Principles” led to AACR • AACR2: one more attempt for one code, based on ISBD

4. Who Is Responsible?

5. AACR2 Characteristics • Created for a card catalog environment • Provides rules for both description and display • Is limited when describing digital materials • Does not demonstrate how works are related to one another

6. 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.)

7. RDA will be … • A consistent, flexible, and extensible framework • Compatible with internationally established principles, models, and standards • Primarily for use in libraries, but also adaptable across many information communities worldwide

8. Collaborations with other Communities • International Meeting of Experts International Cataloguing Committee (IME ICC) • IFLA Section on Cataloguing and its working groups on FRBR and FRAD • RDA/MARC/MARBI • ONIX (Publishers) • RDA, Dublin Core, IEEE/LOM, Semantic Web • “Data Modeling Meeting” - London 2007

9. RDA’s Foundation • Functional Requirements for Bibliographic Records (FRBR) • Functional Requirements for Authority Data (FRAD) • Functional Requirements for Subject Authority Data (FRSAD – in progress)

10. Entities (categories) Attributes (characteristics) Relationships (between and among entities) FRBR Terminology

11. Work Expression Manifestation Item FRBR Group 1 Entities

12. FRBR Group 2 Entities • Those responsible for intellectual or artistic content, physical production and dissemination, or custodianship of Group 1 entities • Persons • Families • Corporate bodies

13. Subjects Can include any Group 1 or Group 2 entity plus Concepts Objects Events Place FRBR Group 3 Entities

14. Work is realized through Expression is embodied in Manifestation is exemplified by Item Group 1 Entities

15. Work • A distinct intellectual or artistic creation • Very abstract! – does not correspond with any tangible thing • (At right : Shakespeare thinks about creating Romeo and Juliet)

16. Expression • The intellectual or artistic realization of a work • Specific sequence of words in a textual work, translations, notes in a musical work, interpretations, etc. • Still abstract!

17. Manifestation • The physical embodiment of an expression of a work • An expression can be embodied in multiple manifestations (e.g. print, microform, digital)

18. Item • A single exemplar of a manifestation

19. Related or Derivative Works

20. User Tasks • Associated with bibliographic data (FRBR)

21. User Tasks • Associated with authority data (FRAD) *tasks carried out by those who create authority data

22. A Look at RDA • Compared to AACR2: IT SURE SOUNDS DIFFERENT! IT SURE LOOKS DIFFERENT!

23. Organization of RDA • Three concepts: • Resource Description • Access Point Control • Relationships

24. Outline of RDA chapters

25. Outline of RDA chapters

26. Outline of RDA chapters

27. Outline of RDA chapters

28. RDA’s Foundation • Structure of RDA itself relies heavily on FRBR and FRAD • Terminology used has its basis in these two conceptual models • “Entities”, “Attributes”, “Relationships” • Also user tasks “Find”, “Identify”, “Select”, “Obtain”, “Conceptualize”, “Justify”

29. RDA’s Structure -- Attributes • General guidelines (chapter 1) • Attributes • Of FRBR Group 1 entities (chapters 2-7) • Of FRBR Group 2 entities (chapters 8-11) which also includes access point control • Of FRBR Group 3 entities (chapters 12-16) – which are “place holder” chapters for now

30. RDA’s Structure -- Relationships • Relationship of FRBR Group 1entities to Group 2 entities (who wrote it, created it, illustrated it, edited it, acted in it, etc. – chapters 18-22) • Relationship of FRBR Group 1 entities to Group 3 entities (chapter 23 – place holder chapter for now)

31. RDA’s Structure -- Relationships • Recording relationships between Group 1 Entities (all those contents notes, title changes, derivative works – chapters 24-28) • Recording relationships between Group 2 Entities (the connection between Shakespeare and Leonard Bernstein – chapters 29-32)

32. RDA Appendices • Many more than were in AACR2 • Some (Abbreviations and Capitalization) are the same as in AACR2) • Some notable differences • Instructions on using ISBD • Mapping from ISBD and MARC to RDA • Titles of nobility (previously in chapter 22) • Relationship designators (who did what?)

33. Terminology in AACR2 and RDA • AACR2 • ISBD dictates content and display • Chief source of information • Heading • Author, composer, etc. • RDA • Instructions only for content • Preferred source of information • Authorized access point • Creator

34. Terminology in AACR2 and RDA • AACR2 • See reference • See also reference • Physical description • RDA • Variant access point • Authorized access point for related entity • Carrier description

35. Terminology in AACR2 and RDA • AACR2 • Main entry • Uniform Title • RDA • Preferred title + authorized access point for creator if appropriate • (1) Preferred title (+ other information to differentiate); • (2) Conventional collective title

36. Terminology in AACR2 and RDA • AACR2 • GMD • RDA • Media type + • Carrier type + • Content type +

37. Some Specific Rules – WEMI Attributes • Notice that RDA begins its instructions with the Group 1 entities of manifestations and items • Core elements have been identified for recording bibliographic attributes • Need to identify what you’re cataloging and the source of information • “Take what you see…”

38. Spell it Out! • Terms we previously abbreviated are now spelled out • Pages • Volumes • Geographic abbreviations • “Third revised edition” (if that’s how it appears on the preferred source of information (previously the chief source) • All in the name of internationalization

39. Compare and Contrast – Description/Attributes • AACR2 • Rule of 3 • Omit titles of nobility, address, honor, etc. • Use formatted field for serials enumeration and chronology • RDA • No longer limited to 3 • Include titles of nobility, address, honor, etc. • Option of using unformatted note for serials enumeration and chronology

40. Compare and Contrast – Description/Attributes • AACR2 • GMD found in two lists • One for the UK • One for Australia, Canada, and the U.S. • Broadly describes various formats • Found in MARC 245 $h • RDA • GDM now a single list for all • Has been split into three discrete elements • Content (MARC 336) • Media (MARC 337) • Carrier (MARC 338)

41. Compare and Contrast – Description/Attributes • AACR2 • Include “home country” if not first place of publication named • Use “s.l.”, “s.n.” • Include multiple publishers RDA Record only the first place of publication – no “home country” provision • Now “Place of publication not identified”, “Publisher not identified” • Only first publisher’s name is required

42. Compare and Contrast – Description/Attributes • AACR2 • Permitted to shorten publisher’s name • International identifiers focus on ISBN and ISSN • RDA • Spell out publisher’s name in full • Includes numbers assigned by publishers, distributors, music publisher numbers in addition to ISBN and ISSN

43. Personal Names • Chapter 9 includes establishing “authorized form of the name” • Many rules identical to AACR2 • Spell out abbreviations like “fl.” (flourished), approximately, born, died • Include individual’s role and/or relationship to the work

44. Family Names – New to RDA • Alignment with archival community • Found in chapter 10 – again includes instructions for authorized forms of names • Type of family • Dates associated with the family • Places associated with the family • Prominent members of the family

45. Corporate Bodies • Chapter 11 of RDA • Very similar to AACR2, including restricting instances for corporate body as a main entry • Will see more corporate bodies included in statements of responsibility, however – but this is not the same as the definition of a creator

46. AACR2 25.17A RDA 6.23.2.5 Works Accepted as Sacred Scripture Use as the uniform title for a sacred scripture (see 21.37) the title by which it is most commonly identified in English-language reference sources dealing with the religious group(s) to which the scripture belongs. If no such source is available, use general reference sources. Avesta Bible Koran Talmud Tripiṭaka Choose as the preferred title for a sacred scripture the title by which it is most commonly identified in reference sources in the language preferred by the agency creating the data that deal with the religious group or groups to which the scripture belongs. If no such source is available, use general reference sources. Avesta Bible Holy Piby Kitāb al-aqdas Qur’an Talmud Tripiṭaka

47. RDA Relationships • Works to works: • Romeo and Juliet to West Side Story • Serial title changes • Expressions to expressions: one translation to another; one interpretation to another • Manifestation: content remains the same, the carrier or media changes

48. Examples – Handout • 100 field: inclusion of $e to indicate creator’s role • 300: no abbreviations for pages, illustrations, etc. • 300: “cm” is abbreviated because it is considered as a scientific term • 336, 337, 338 fields: take the place of GMD (245 $h)

49. Examples – Handout • Example 3: Since RDA does not concern itself with display, a library could decide to capitalize all letters of the title proper • Also note the inclusion of the creators’ titles – something that isn’t done in AACR2 • However the cataloger has the option of omitting information in the statement of responsibility

50. Examples – Handout • Example 5: Relationship of one expression to another -- a translation to its original • Cataloger’s option to use a relationship designator from RDA Appendix I in the 100 and 700 fields • RDA allows you to create a 7xx field without mention as an attribute