Why RDA? What’s the point? OCLC Cookbook finder: html html

In SWAN…

… and even more!

How is this made possible?

Functional Requirements for Bibliographic Records (FRBR) Conceptual model of bibliographic universe Theoretical foundation of RDA Developed from the perspective of the user rather than the cataloger Defines four user tasks: Find, Identify, Select, Obtain

FRBR User Tasks Find: to find entities that correspond to the user’s search criteria Identify: to confirm that an entity described corresponds to the one sought Select: to choose an entity that meets a user’s requirements with respect to content, physical format, etc. Obtain: to obtain access to an entity described

FRBR An entity relationship model Entity: Something that can be distinctly defined Relationship: An association among two or more entities

FRBR Entities Group 1 Products of intellectual or artistic endeavor Book Film Sound recording Group 2 Persons responsible for creating Group 1 entities Author Editor Producer Director Composer Instrumentalist

FRBR Relationships Associations between Group 1 and Group 2 entities Creator Relationships Relationship between an author and a book » Expressed “written by” Relationship between a director and a film » Expressed “directed by”

FRBR Group 1 entities (WEMI) Work – A distinct intellectual or artistic creation Expression – The realization of a work Manifestation – The physical embodiment of an expression Item – An individual copy of a manifestation

A WEMI Example WORK = ideas in a person’s head, the original story as in Romeo and Juliet EXPRESSION = a specific text and language, as in the Italian translation of Romeo and Juliet MANIFESTATION = a particular publication, as in Penguin Book’s 2011 publication of Romeo and Juliet ITEM = one copy of a manifestation, such as a physical book, DVD or CD

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

AACR2 and RDA Compared AACR2 Developed in a print environment Limited in scope Anglo American perspective RDA Designed for a digital world/web environment Extensible framework International perspective

Principles of RDA: Fundamental differences from the old rules AACR2 was structured so that data could fit on physical catalog cards Without catalog cards, why does everything need to be so abbreviated? (It doesn’t!) RDA is meant to be a more “plain language” way to record bibliographic information Transcribing information is the new rule – “take what you see and accept what you get” (even if it’s inaccurate) This encourages not just the readability of our catalog information for library patrons, but also makes it easier for librarians – they can often reuse machine- generated data. But we also have the option to change it and adhere to local practice!

Differences between RDA and AACR2 reflected in MARC records GMD replaced by multiple fields for format description Latin abbreviations eliminated and use of most English abbreviations prohibited Publication and copyright information shown in separate fields In general, presentation of information is less cryptic and more clearly differentiated

16 Capitalization Accepting found capitalization: $a Cairo : $b THE CITY VICTORIOUS / $c Max Rodenbeck. 250 ## $a FIRST VINTAGE DEPARTURES EDITION. Changing found capitalization: $a Cairo : $b the city victorious / $c Max Rodenbeck. 250 ## $a First Vintage Departures edition. These are equally acceptable!

Inaccuracies AACR $a Techincal [sic] services best practices : $b Oak Park Public Library / $c Fran Whiteside... [et al.]. OR $a Techincal [i.e. Technical] services best practices : Oak Park Public Library / $c Fran Whiteside... [et al.]. RDA $a Techincal services best practices : $b Oak Park Public Library / $c Fran Whiteside, Bonnie Jurkowski, Sonia Ramos, and Donna Bobco _ $i Title should read: $a Technical services best practices

Abbreviations Generally, you might notice some smaller changes within the record’s fields themselves; there are no more abbreviations and a lot less square brackets.

What MARC fields have changed with RDA? 040 & fixed fields:

Rule of Three AACR $a Technical services best practices : $b Oak Park Public Library / $c Fran Whiteside... [et al.] _ $a Whiteside, Fran. RDA $ Technical services best practices : $b Oak Park Public Library / $c Fran Whiteside, Bonnie Jurkowski, Sonia Ramos, and Donna Bobco _ $a Whiteside, Fran, $e author _ $a Jurkowski, Bonnie, $e author _ $a Ramos, Sonia, $e author _ $a Bobco, Donna, $e author.

Statement of Responsibility Optional Omission $ Technical services best practices : $b Oak Park Public Library / $c Fran Whiteside [and three others]

Relationship Designators in 1xx & 7xx Relationship between person and resource Terms added to entities in MARC records to specify the relationships among FRBR entities. They replace the infrequently used relator codes that were part of AACR2. A designator that describes the relationship between a person and a resource goes in subfield $e _ $a Madigan, Jim, $e author $ Fun at the Oak Park Public Library : $b the best years yet / $c by Jim Madigan, edited by Karen Bar, illustrated by Martyn Churchouse _ $a Bar, Karen, $e editor _ $a Churchouse, Martyn, $e illustrator.

264 Field Production, Publication, Distribution, Manufacture & Copyright 1st indicator Sequence of statements # - Not applicable/No information provided/Earliest 2 - Intervening 3 – Current/Latest 2 nd indicator - Function 0 – Production (for unpublished resources) 1 - Publication 2 - Distribution 3 - Manufacture 4 - Copyright notice date

264 Field Production, Publication, Distribution, Manufacture & Copyright Subfield Codes $a – Place of production, publication, distribution, manufacture (R) $b – Name of producer, publisher, distributor, manufacturer (R) $c – Date of production, publication, distribution, manufacture, or copyright (R)

264 Field Publication and Copyright Dates AACR2 260 _ _ Chicago : $b David J. Seleb Publishing, $c 2013, ©2012. RDA 264_ 1 Chicago : $b David J. Seleb Publishing, $c _ 4 $c ©2012

What MARC fields have changed with RDA? No more GMD: In RDA, the ǂh in the 245 title statement, referred to as the General Material Designation or GMD, is no longer in use. Thus it would be correct for you to encounter RDA records for CDs that did not say [sound recording] in the title, or ebook records without [electronic resource]. This has been replaced by the 33x fields.

336, 337, 338 fields (aka “33x” fields) Instead of a GMD, RDA records now use these 336, 337 and 338 fields to describe: 336: Content type (how the item’s information is expressed) 337: Media type (how the item’s information is accessed) 338: Carrier type (how the item’s information is stored)

General Material Designation AACR2 1.1C $a The third coast $h [electronic resource] : $b when Chicago built the American dream / $c Thomas Dyja. 300 $a 1 online resource (xxxiv, 508 p., [16] p. of plates) : $b ill., ports., maps. RDA 3.2, 3.3, $a The third coast : $b when Chicago built the American dream / $c Thomas Dyja. 300 $a 1 online resource (xxxiv, 508 pages, 16 unnumbered pages of plates) : $b illustrations, portraits, maps. 336 $a text $b txt $2 rdacontent 337 $a computer $b c $2 rdamedia 338 $a online resource $b cr $2 rdacarrier

Bibliographic Framework Initiative (BIBFRAME) An undertaking of the Library of Congress and Library Community To transition from the MARC 21 format to a more web-based linked-data model To realize the full potential of FRBR & RDA