1 Jennifer Bowen University of Rochester SUNY Library Association Geneseo, New York June 15, 2006 FRBR: Coming Soon to YOUR Library?

2 A Visual FRBR Example Results Display of a Keyword Search for Susan B. Anthony

3

4 Susan B. Anthony keyword search – Top relevance hits 1. Biography 2. Biography 3. Biography 4. Susan B. Anthony Preservation District 5. Her Writings 6. Biography 7. Biography 8. Biography 9. Correspondence 10. Virgil Thomson opera recording 11. Biography 12 Proceedings of her Trial 13 Virgil Thomson opera recording 14 Music from the Ken Burns film 15 The Ken Burns film 16 Biography 17 Biography 18 Analysis of her writings 19 Women’s Studies Newsletter 20 Her papers 21 Biography

5

6

7

8

9

10

11

12 Why is this better? Collocation: materials with the same or related content are grouped together Easier navigation through search results Precise results with simple search queries. What could help us to achieve this?

13 FRBR: What is it?

14 FRBR: Functional Requirements for Bibliographic Records IFLA publication, 1998 Published by K.G. Saur Also available on the Web Conceptual model How do users use bibliographic information? Relates bibliographic data to user tasks

15 But wait, there’s more… FRAR (or FRAD???) FRAR (Functional Requirements for Authority Records) May be renamed FRAD (Functional Requirements for Authority Data) Another model, similar to FRBR Review of draft ended October 2005

16 Significance of FRBR Sheds new light on current practices, standards AACR, MARC, etc. Inform development of new standards (RDA) A clearer way to communicate about how catalogs should function Based on needs of catalog users

17 Entity-Relationship Model Entities Relationships Attributes relationship Entity 1Entity 2

18 FRBR Entities Group 1: Work, Expression, Manifestation, Item Products of intellectual or artistic endeavor: Group 2: Person, Corporate Body Those responsible for intellectual or artistic content Group 3: Concept, Object, Event, Place Serve as subjects of works

19 FRBR Group 1 Entities Work Expression Manifestation Item Goethe’s “Faust” L. Filmore’s English translation of Faust As published by W. Smith, 1847 The copy owned by my library

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

FRBR Entity Levels Work: Expression: Manifestation: The Novel Orig. Text Transl. Critical Edition The Movie Orig. Version PaperPDFHTML Item: Copy 1 Autographed Copy 2

FRBR Entity Levels Work: Expression: Manifestation: The Novel Orig. Text Transl. Critical Edition The Movie Orig. Version PaperPDFHTML Item: Copy 1 Autographed Copy 2 Family of works

Attributes of Group 1 Entities Work ID Title Date etc. Expression ID Title Form/mode of expression Date Language etc. Manifestation ID Title Statement of responsibility Edition Imprint (place, publisher, date) Form/extent of carrier Terms of availability Mode of access etc. Item ID Provenance Location etc.

24 FRBR User Tasks Find Search for a resource Identify “What is this resource?” Select “Will this suit my needs?” Obtain “How do I get it?”

25 What does FRBR mean for catalogs? Collocation: Bring like things together in the catalog: Expressions of the same work Manifestations of the same expression Show relationships between records in the catalog Help users navigate search results

26 Where is FRBR most useful? Classics of literature vs. scientific studies Examples in the OCLC database Stephen King 102 works, 231 manifestations Shakespeare’s Hamlet 1 work, 2696 manifestations Rowling, J.K. (Harry Potter stories) 28 works, 300 manifestations

27 FRBR and Cataloging (Part 1 - Overview)

28 Group 1 Entities vs. MARC Or, What are we cataloging? CAVEAT: This is vastly oversimplified! WorkAuthority record Expression???? ManifestationBibliographic Record ItemHolding Record Current bibliographic records may contain attributes of all four entities! See Library of Congress (Tom Delsey) mapping of FRBR and MARC Bibliographic and Holding Formats

29 Expression vs. edition: Same thing? No! Some editions are the same expression, but different manifestations Reprint editions, simultaneous publications Some editions are different expressions: If content has been revised (Rev. ed., 1 st ed., 2 nd ed.) Some editions are different works altogether (but publisher calls them “editions”)

30 FRBR and cataloging Works : We already use uniform titles for collocation Expressions: Not currently creating headings for expressions Attributes of expressions now buried within bibliographic records

31 Incorporating FRBR into a new cataloging standard, RDA RDA: Resource Description and Access First release in 2008 Incorporating FRBR terminology Structure based on FRBR User Tasks Collocation of expressions using citations From To

32 Expressions: From cataloging to collocation Cataloger-created collocation Proposed new catalog rules for RDA for constructing citations for expressions System-created collocation Explore what systems can do with expression-level data already in MARC records (e.g. VTLS, OCLC, RLG)

33 Alternative: System-based collocation of expressions System can identify expression- level data already in the records Use this data to collocate (sort) displays More flexible than assigning citations Some system vendors are already working on this

34 FRBR and Systems Vendors What can library systems do now to implement FRBR?

35 Possibilities of system- based FRBR collocation Works Can do now, if good uniform titles, clean data Expressions Possible, but needs work! Can collocate by format, language Can improve collocation without explicitly identifying every expression

Collocation by family of works and expressions Shakespeare, William, Hamlet. + Texts + Motion Pictures + Sound Recordings

Collocation of expressions Shakespeare, William, Hamlet. + Texts – Danish + Texts – Dutch + Texts – English + Texts – French + Texts – Spanish + Motion Pictures – English + Sound Recordings - English

Collocation of manifestations Shakespeare, William, Hamlet. - Motion pictures – English Director, Bill Collegan Director, Kevin Kline, Kirk Browning Director, Franco Zeffirelli Director, Maria Muat Director, Kenneth Branagh Director, Campbell Scott, Eric Simonson

39 FRBR-ize MARC records OCLC’s FRBR Work Set algorithm: e/frbrhttp:// e/frbr/ LC’s FRBR display tool:

40 System-based collocation: Potential for improvement? Relator Information Identify roles of entries in a predictable place in the record Proposed new rules in RDA will expand use of relator info. (currently covered under AACR2 Rule 21.0D) Linking Entries Show relationship between records Pat Riva, article in April 2004 Library Resources & Technical Services

41 Assigned access points or System-based collocation? Both! Libraries will demand more of systems to show structure of catalog and collocate search results AND Catalogers will be able to assign citations for expressions when necessary.

42 FRBR interface questions for your system vendor What does the FRBR user interface look like? Will users see a FRBR-like structure? How do users navigate search results? Is vendor doing usability testing on a FRBR user interface?

43 More questions for your system vendor What record structure do you use: “FRBR-Like” (e.g. VTLS) or MARC? Can MARC records be extracted? How will FRBR affect cataloging interface? How are links made and maintained between records?

44 What if your system vendor isn’t implementing FRBR? Lobby them! Get other institutions interested! Make a list of problems that FRBR would help solve Restate old problems in terms of FRBR Look for other ways to incorporate FRBR or parts of it at your library

45 FRBR at the University of Rochester or, Why wait for your System Vendor to implement FRBR?

46 University of Rochester web projects User-centered web design Alternatives to cumbersome online catalog searches Use data already in our MARC records to create websites designed to meet specific UR users’ needs

47 Buried treasure in our MARC records Relator information ($e and $4) Shows relationships in a predictable place in the record Language Expression-level attribute Genre terms Work-level attribute

48 Example 1 UR Video/DVD Collection Circulating collection: for research AND casual viewing “What directors do you have represented in your collection?” Use relator info., etc. in MARC records to create browse lists dex.cfm?page=videos dex.cfm?page=videos

49

50

51 Example 2 UR Audio Recordings Relator Information Users choose performers or composers Problematic: $4 cmp not used for composers so… Absence of $4 = composers Some false drops, more data cleanup. dex.cfm?PAGE= dex.cfm?PAGE=1333

52

53

54 Other useful FRBR data Browse by primary language (videos and DVDs) expression-level attribute Browse by genre work-level attribute videos and DVDs: mostly LC genre list audio CDs: local list (“record store categories”: Jazz, Classical, etc.)

55

56

57 The Real Truth UR website project designers didn’t know about FRBR! Project concept based on user needs Demonstrates viability of FRBR model regarding user tasks/needs

58 FRBR: May already be at your library! Catalogs already contain some elements of FRBR There’s more to FRBR than entities and attributes: emphasis on the user User tasks: find, identify, select, obtain What are our users trying to achieve? User-centered design

59 Is FRBR Really Coming? It’s already here!

60 Questions?

61 FRBR and Cataloging Part 2: FRBR and RDA

62 Incorporating FRBR into a new cataloging standard, RDA RDA: Resource Description and Access First release in 2008 Incorporating FRBR terminology Structure based on FRBR User Tasks Collocation of expressions using citations From To

63 Group 1 entities vs. MARC Or, What are we cataloging? CAVEAT: This is vastly oversimplified! WorkAuthority record Expression???? ManifestationBibliographic Record ItemHolding Record Current bibliographic records may contain attributes of all four entities! See Library of Congress (Tom Delsey) mapping of FRBR and MARC Bibliographic and Holding Formats

64 Can We Catalog an Expression? Is it feasible to change the basis for a catalog record from a manifestation to an expression?

65 Working Group: Can we catalog an expression? Sound archivist: YES! The performance is the expression Link all recordings of that performance to it Most group members: NO! Not the way most libraries operate We start by purchasing, and then cataloging, a manifestation.

66 Problems with cataloging expressions Not enough info. at the time of cataloging title of the expression? date of the expression? If only one manifestation of an expression in the catalog, cataloger may not know: if other manifestations exist, and if so… how the first one relates to others May needlessly complicate the cataloging process

67 Do we always care about expressions? Only when… Bibliographic families: When a work exists in multiple expressions When an expression exists in multiple manifestations A small percentage of all catalog records (OCLC - 20%), but these represent the core of our cultural heritage

68 Cataloging an expression? Working Group recommendation: Libraries should keep cataloging manifestations (mostly) Expression–level access can be achieved instead through collocation of search results

69 Rules for constructing citations for expressions in RDA: How? Possible additions to work citations (uniform titles): Language Edition statement Mode of expression (e.g. Sound) Date of expression: date of performance, translation, etc. Name of editor, translator, performer (show relationship to Group 2 entity)

70 Specific uses of citations for expressions Useful for small, but important, subsets of library materials Large collections in a specific area Local research interest Many expressions of the same work Many manifestations of the same expression More specific related-work citations (related expression citations)

71 Rules for creating citations for expressions in RDA: Why? Show relationships between records Move toward rules for how a catalog should function Demonstrates that collocation at the expression level is an important function of the catalog Force an online system to collocate expressions if system won’t do it any other way

72 RDA Timeline May-Sept. 2006: Completion of draft of remainder of part A (formerly called part II) and constituency review Oct Apr. 2007: Completion of draft of Part B (formerly called part III), and constituency review May-Sept. 2007: Completion of General Introduction, Appendices, and Glossary 2008: First release

73 Commenting on RDA drafts RDA drafts available at: Informal discussion: subscribe to RDA-L (link on page above) Formal comments: within the U.S., use the CC:DA web form: orm.cfm

74 Thank you! …Questions?