RDA

Designed for current

and
future environments

Chris Oliver
McGill University
chris.oliver@mcgill.ca
May 11, 2011
Y
Y   





˜ new metadata standard replaces AACR2
˜ designed for the web environment
˜ better metadata to support better resource
discovery
Designed for now and the future
×
˜ designed to work in the
current environment
˜ compatible with AACR2
  

˜ designed to work in
future environments
˜ à
 
records ˜ à 

˜ can encode in MARC 21 ˜
à à 
and store in current  à


databases àà à
˜

à 


à  
  
{lan for the webinar
1. What is RDA?
2. What makes RDA different?
3 RDA as a content standard
3 RDA·s underlying framework
- data model
- data elements
Questions, comments
3. Bibliographic and authority data in new environments
3 RDA data beyond MARC records
3 RDA data beyond the current catalog
3 RDA data on the web

Questions, comments
What is RDA?

‡ relationship to AACR2

‡ a content standard
AACR2 RDA
˜ continue to record title
˜ continue to record edition
˜ continue to record date of publication

¦


˜ new vocabulary
˜ new way of thinking about how we do these
steps
Relationship to AACR2
Y
0.2
´instructions derived from AACR have been reworkedµ

Ô many instructions originate from AACR2

Ô instructions are reworded and organized differently
Ô within a new theoretical framework

every word
has changed many instructions
show visible
continuity with
AACR2
AACR2 RDA
AACR2 deconstructed

new concepts

new structure

new vocabulary

some new instructions

some changed instructions

What makes RDA different?
some continuity with AACR2

¦


˜ RDA as a content standard

Πflexibility
Πadaptability
˜ theoretical framework
˜ bibliographic and authority information as
´dataµ
RDA = content standard
RDA not an encoding standard
not a presentation standard

RDA what data do I record?

RDA 0.4.2 Objectives

0.4.2.3 Flexibility

The data should function independently of the format,

medium, or system used to store or communicate the
data.They should be amenable to use in a variety of
environments.
RDA = content standard
RDA data can be encoded using:
‡ MARC 21
‡ encoding schema such as Dublin Core,
MODS, and others
‡ web friendly encoding schema based on
XML

RDA data can be presented using :

‡ ISBD conventions
‡ labelled display
‡ newly developed display conventions
‡ display conventions used in other metadata
communities
xamples in RDA
examples show what the data should be:
Y
2.4.1.4 Recording Statements of Responsibility
Transcribe a statement of responsibility in the form in
which it appears on the source of information.
EXAMPLE
by Walter de la Mare
Fats Waller
by Dr. Johnson
by Sir Richard Acland
by Alfred, Lord Tennyson
by a Lady of Quality
par Charles M. Schultz
directed and produced by the Beatles
xamples in RDA


Y 2.1F1. Transcribe statements of responsibility
relating to persons or bodies as instructed in 1.1F

Shut up in Paris / by Nathan Sheppard

Great Britain : handbook for travellers / by Karl
Baedecker
Vas-y, Charlie Brown / par Charles M. Schulz

!
Ymanual 245 $c statement of responsibility «

=
 The plays of Oscar Wilde /Alan Bird.

=
How to play chess /Kevin Wicker ; with
a foreword by David Pritchard ; illustrated by Karel
Feuerstein.
 RDA as a content standard
˜ record reliable data
˜ how to encode data ² not part of the standard

RDA says: record person·s date of birth

1978

Many possibilities for encoding:

$d 1978- MARC 21
<subfield code="d">1978- .</subfield> MARCXML
<mods:name{art type="date">1978- </mods:name{art>
<dob>1978</dob>
å   à à  1978</   à
RDA as a content standard
˜ record reliable data
˜ how to display data ² not part of the standard

RDA says: record person·s date of birth

1978

Many possibilities for display:

born 1978
b. 1978
1978-
date of birth: 1978
RDA as a content standard
˜ designed for use by libraries
˜ designed to be flexible and adaptable to many
environments
´not tied to library-specific encoding
´not tied to library-specific display of data
´data that can interact and co-exist with metadata of
other cultural heritage communities
´data that can be used in the web environment
Day 1 of implementation
˜ most ² in MARC 21 environment
˜ most ² in conventional library databases
² bibliographic records, authority records
+ holdings records

RDA records in MARC 21

Library of Congress catalog
US RDA Test documentation
OCLC WorldCat
Libraries that participated in the US Test
xample: RDA in MARC 21
020 $a 9780521440080
100 1 $a Adrian, R. J. $q (Ronald J.), $e author
245 10 $a {article image velocimetry / $c Ronald J. Adrian, Jerry
Westerweel.
260 $a New York : $b Cambridge University {ress, $c 2011,
©2011.
300 $a xxvi, 558 pages : $b illustrations ; $c 26 cm.
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
490 1 $a Cambridge Aerospace series ; $v 30
700 1 $a Westerweel, J., $e author
830 0 $a Cambridge Aerospace series ; $v 30
xample: RDA in MARC 21
020 $a 9780521440080
100 1 $a Adrian, R. J. $q (Ronald J.), $e author
245 10 $a {article image velocimetry / $c Ronald J. Adrian, Jerry
Westerweel.
260 $a New York : $b Cambridge University {ress, $c 2011,
©2011.
300 $a xxvi, 558 pages : $b illustrations ; $c 26 cm.
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
490 1 $a Cambridge Aerospace series ; $v 30
700 1 $a Westerweel, J., $e author
830 0 $a Cambridge Aerospace series ; $v 30
xample: RDA in MARC 21
110 2 $a Indian Map Service.
245 00 $a Assam tourist road atlas & state distance guide / $c
designed, cartographed, printed & published by Indian Map
Service ; editors, R.{. Arya [and three others].
246 3 $a Assam tourist road atlas and state distance guide
255 $a Scales differ.
260 $a Jodhpur, India : $b Indian Map Service, $c 2010, ©2010.
300 $a 1 atlas (40 pages) : $b color illustrations, color maps ; $c 25
cm.
336 $a cartographic image $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
700 1 $a Arya, R. {.
xample: RDA in MARC 21
110 2 $a Indian Map Service.
245 00 $a Assam tourist road atlas & state distance guide / $c
designed, cartographed, printed & published by Indian Map
Service ; editors, R.{. Arya [and three others].
246 3 $a Assam tourist road atlas and state distance guide
255 $a Scales differ.
260 $a Jodhpur, India : $b Indian Map Service, $c 2010, ©2010.
300 $a 1 atlas (40 pages) : $b color illustrations, color maps ; $c 25
cm.
336 $a cartographic image $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier
700 1 $a Arya, R. {.
Look beyond day 1
day 1 implementation  task is completed

day 1 beginning on a new track

making the point of transition
as smooth as possible
emphasizing continuity
Us and our legacy data
RDA «
˜ takes us from where
we are

˜ moves us to a new
track

˜ allows us to change
direction

˜ start travelling along a

new track
RDA·s framework
the data model
the data elements
RDA·s framework
the data model
xplicit RDA data model
˜ RD = entity relationship diagram
in RDA Toolkit

available athttp://www.rdatoolkit.org/background
Aligned with IFLA conceptual models
YY Functional Requirements for Bibliographic
Records
1998

Y
Functional Requirements for Authority Data

2009

†
  à
à     à !
" 

 #$%$

˜ FRAD and FRSAD are extensions of the FRBR model

FRBR + FRAD

˜ based on the analysis of

bibliographic and authority
records
˜ entity-relationship models
˜ IFLA task forces
˜ world-wide consultation
˜ international consensus
Why are the models important?
˜ internationally shared conceptual model
´ broad international support for the explanatory
power of the models
´ common international language and conceptual
understanding of the bibliographic universe

˜ entity-relationship model
´ widely used data modeling technique
´ understood by other metadata and data modeling
communities
e.g. software engineers, information systems and database designers
Why are the models important?
as the foundation for a standard:
Ô provides a logically consistent underlying framework
Ô makes it easier for other metadata communities to
understand the structure of our data
Ô makes it easier to apply in an international context
Ô makes it easier for our data to interoperate with
data modeled similarly
‡ other data that aligns with a FRBR/FRAD model
‡ other data that conforms to a similar entity-
relationship model
ntities - attributes - relationships
˜ new vocabulary

˜ entity = the object of a user·s interest

˜ entities that are of interest to someone who

uses bibliographic and authority data

RDA focuses on:

bibliographic entities

entities specific to authority control

Bibliographic entities (FRBR/FRAD)
work FRBR Group 1
expression products of intellectual or
manifestation artistic endeavor
item

person FRBR Group 2

family responsible for group 1 entities
corporate body

concept
FRBR Group 3
object
subjects
event
(includes group 1 & 2)
place
Authority entities (FRAD)
bibliographic entities entities on which authority
data is focused
name
identifier entities for authority
control
controlled access point

  à   à  

 à

à àà


à
Authority entities (FRAD)
bibliographic entities entities on which authority
data is focused
name
identifier entities for authority
control
controlled access point

  à   à  

 à

à àà


à
Attributes
˜ characteristics of the entity
data to be recorded about the entity

   
work: title, genre

manifestation: publisher, date of publication, extent

item: identifier (e.g. barcode), provenance
person: name, dates, gender
corporate body: place, dates, address
object: term
Relationships: links between entities
˜ link between one entity and another
˜ basis for navigation and support collocation
˜ explicitly defined

primary relationships:
between work, expression, manifestation and item
3 other major types of relationships:
1. between a person, family or corporate body and a resource
2. between one resource and another resource
3. between a person, family or corporate body and another person,
family or corporate body
Relationships: links between entities

work
    person
item 
à   family
manifestation 
  corporate body

work   à work

manifestation
à
 & manifestation

person     family
family  à  corporate body
Organization and Structure of RDA

È2 main parts
Recording attributes 
à%'(
Recording relationships 
à)'%$

È Divided into 10 sections

sections are organized according to the bibliographic
entities
Organization and Structure of RDA

à%'(
à  

à%& Recording attributes of manifestation and item

à#. Recording attributes of work and expression

à*. Recording attributes of person, family, and corporate body

à(& Recording attributes of concept, object, event, and place
[placeholder]
Organization and Structure of RDA

à)'%$
à à

à). Recording primary relationships between
work, expression, manifestation, and item

à+. Recording relationships to persons, families,
and corporate bodies associated with a resource

à,& Recording the subject of a work [placeholder]

à-& Recording relationships between works,
expressions, manifestations, and items

à.. Recording relationships between persons, families,
and corporate bodies

à%$. Recording relationships between concepts, objects,
events, and places [placeholder]
ntities - attributes - relationships
˜ new vocabulary
˜ new way of thinking about bibliographic and authority
information
˜ careful separation of content and carrier

 that a human can read and interpret

that is machine actionable

RDA·s framework
the data elements
lements in RDA and AACR2
Y
 A word, character, or group of words
and/or characters representing a
distinct unit of bibliographic
information.

Y similar definition


« and forming part of an area of the
description.

˜ AACR2 elements are organized and embedded into areas

RDA data elements
˜ move :
‡ paragraph style (ISBD areas)
‡ data embedded in long character strings
‡ data stored in ambiguous elements

˜ move :
‡ independent, separate units of data
‡ precisely defined or ´parsedµ
‡ each element contains data about
a single attribute
 a single relationship
‡ increased use of controlled vocabulary
RDA data elements
˜ distinct and defined elements for each kind of data

illustrative content
encoding format
different element production method
for each type of sound content
data applied material
base material
reduction ratio
lements in AACR2


Y information embedded in ´other physical
detailsµ (or a non-specific note)

illustrative content
encoding format
other physical production method
details sound content
applied material
MARC 300 $b base material
reduction ratio
Controlled vocabulary
˜ controlled vocabulary recommended for many elements

encoding format DAISY, M{3, Access, XML,

J{G, TIFF, CAD, {DF,
Blu-Ray, VCD

production method blueline, blueprint, engraving,

etching, lithograph, photocopy,
photoengraving, woodcut

base material Bristol board, canvas, cardboard,

ceramic, glass, leather, paper,
parchment, vellum
RDA data elements
˜ distinct and defined elements for each kind of data
= groundwork for the future

illustrative content
encoding format
currently map to production method
MARC 300 $b sound content
applied material
base material
reduction ratio

%  ààà/"0#% àà à1 
  

   
RDA data elements
˜ only   kind of data in an element

Y date of publication, distribution, etc.

!
Y 260 $c

Y
 4 different elements:

date of production
date of publication
date of distribution
date of copyright
Dates of publication and copyright
AACR2: RDA:
{   New York : {   New York :
{algrave Macmillan, 2011. {algrave Macmillan, 2011,
©2011.

{   Cambridge, Mass. {   Cambridge,

: Candlewick {ress, Massachusetts :
c2006. Candlewick {ress,
[2006], ©2006.

÷


     
  
 


RDA data elements
˜ remove ambiguity
AACR2:
AACR2 1.7B13. Dissertations
‡ information embedded in a note
‡ note about academic degree, granting institution or
faculty and year degree granted

RDA: 7.9.1 Recording Dissertation or Thesis

Information
‡ separate elements for: academic degree
granting institution or faculty
year degree granted

÷


     
 ÷
 ÷

÷
Thesis information
RDA elements:
Academic degree {h.D.
Granting institution or faculty McGill University
Year degree granted 2009

Already have 2 options in MARC 21:

502 $a Thesis ({h.D.)³McGill University, 2009.

502 $b {h.D. $c McGill University $d 2009

Thinking ´dataµ
˜ even within the MARC environment, we·re thinking about
parsing information strings into data elements
more granularity for:
thesis information
place and date of capture
dates of pub., dist., man., prod. in progress
date of copyright in progress
form of work
medium of performance

˜ even for display:

260 $a [San Francisco?] : $b [publisher not identified],
$c [2009?].
 Identifiers
from FRAD: entities are known by their names
and/or are assigned identifiers

Y
has an element defined for recording the identifier of

each bibliographic entity: item
manifestation
expression
work
person
family
corporate body

Y
has option to use identifiers to reference relationships

 Identifiers
˜ name = more suitable for humans to read and interpret

eye-readable data: name, date «

 20 2%.)*'#$$*

˜ identifier = more suitable for machines to make links

= scope to use a URI as an identifier
= machine actionable data

$%$%"++*)
33&33(.(()*,34  250
Relationship designators
˜ specify nature of relationships

specify roles
&&
 
  

 
 
à 

specify relationship between resources

&& à
 
  à
 
Access points for automated env.
env.
AACR2 Aesop·s fables. {olyglot.

RDA Aesop·s fables. Greek

Aesop·s fables. Latin
Aesop·s fables. nglish
Aesop·s fables. German

AACR2 Aesop·s fables. nglish & German

RDA Aesop·s fables. nglish

Aesop·s fables. German
RDA data elements
˜ still recording the same kind of information
  à   
à

˜ record in distinct data elements

˜ record with more precision
˜ data that a human can use
˜ data that is machine actionable
˜ each element has the potential to be used:
- to search
- to navigate
- to retrieve
- to build meaningful displays of data
Questions, comments


Bibliographic and authority data
in new environments
‡ RDA data beyond MARC records
‡ RDA beyond the current catalog
‡ RDA data on the web
RDA = ´well-
´well-formedµ metadata
˜ instructions on how to record data for each element
˜ controlled vocabulary is used as the value recorded in
many elements
˜ underlying model for the data

¥ elements defined in the way that other metadata

communities expect
¥ RDA data can interoperate with data modeled similarly
¥ preparation for use of RDA data on the web, in linked
data environment of the future ²  à 
 à
RDA in XML
˜ not an abstract goal for the future
˜ US test included testing RDA for descriptions encoded
using Dublin Core and MODS
˜ RDA Toolkit includes a section on schemas
˜ download RDA element sets as XML schema
core
enhanced
specialized
universal
{art of MODS record - US test data
U


<titleInfo displayLabel="
">
<title>
 </title>
</titleInfo>
<note displayLabel="! 
">  
"#</note>
U


</relatedItem>
<relatedItem type="$" displayLabel="">
<titleInfo>
<title>%
#

 $
#$&$ 
 </title>
</titleInfo>
</relatedItem>
U


<form authority="
" type="
"> </form>
<form authority=" 
" type=" 
"> 
 </form>
<form authority="   " type="   ">

&</form>
{art of MODS record - US test data
U


<mods:title>' 
! ()</mods:title>
</mods:titleInfo>
<mods:name type=" " authority=" " ID=" *+,-./+-,">
<mods:name{art> 0$</mods:name{art>
<mods:name{art type="">/12</mods:name{art>
<mods:affiliation> !%
#
</mods:affiliation>
<mods:role>
<mods:roleTerm authority=" ">$</mods:roleTerm>
</mods:role>
</mods:name>
U


<mods:issuance> &$
</mods:issuance>
U


<mods:form type="
" authority="">3
</mods:form>
<mods:form type="
" authority="">
&
</mods:form>
<mods:form type="
" authority="">#

</mods:form>
<mods:form authority="" type=" 
&">4!0</mods:form>
U

Beyond the traditional catalog
˜ online catalog = closed database
Πabundance of metadata
Œ invisible to web search engines ´(µ

˜ MARC 21 = library specific record format

Πdeveloped before concept of relational databases
Πused in closed databases of the library world
Πweb cannot access and use MARC data
Πmany ILS cannot fully use MARC data
Πnot used in other cultural heritage communities
Squeezing into MARC 21

« it can be done «
but more comfortable fit elsewhere?
 RDA data in current databases
bibliographic records = description Ë access points
Ëauthority records ² linked to access points
Ëholdings records ² linked to bib records

6     àà  

 7à   2
à 28 à29 à #à2#$$.33


&'!
&3
3#$$.$+$#&

Authority

Bibliographic
Authority

Holdings
RDA data is flexible
‡ in new types of database structures
&&object oriented database
database mirroring FRBR/FRAD model

cluster of data pertaining to each entity

manifestation record
Ëitem record
Ëwork record
Ëexpression record
Ërecord for person, family, corporate body
Ërelationships = links between the above entities
illustration: from Tom Delsey·s presentation to the Deutsche Nationalbibliothek, Frankfurt,
Germany, June 2nd, 2009: http://www.rda-jsc.org/docs/td20090602.pdf
AACR2 + MARC 21
  
name of a person ------- title of a resource

AACR2 + MARC 21
˜ type of relationship embedded in text of bibliographic
description
˜ bibliographic record contains name of person and title
˜ may have an authority record that also ties together
name of person and title of work
AACR2 + MARC 21
bibliographic record  à  

245 00 $a Alice in Wonderland, or, What's a nice kid like you

doing in a place like this? /$cHanna-Barbera {roductions.
700 1# $a Carroll, Lewis, $d 1832-1898. $t Alice's
adventures in Wonderland.

˜ record may or may not include text in a note that explains

the relationship between Lewis Carroll and the film
 RDA + MARC 21
  
name of a person ------- title of book

RDA + MARC 21
˜ type of relationship embedded in text of bibliographic
description
˜ bibliographic record contains name of person and title
˜ may have an authority record that also ties together name of
person and title of work
˜ relationship designators in bibliographic records
($e, 4, i)
RDA + MARC 21
bibliographic record

=
00 $a Alice in Wonderland, or, What's a nice kid like you

doing in a place like this? /$cHanna-Barbera Productions.
700 1# $i parody of (work) $a Carroll, Lewis, $d 183=-1898. $t
Alice's adventures in Wonderland.

    

:/"0#% 
;

Alice in Wonderland, or, What's a nice kid like you doing in a

place like this? / Hanna-Barbera {roductions.
{arody of Carroll, Lewis, 1832-1898. Alice's adventures in
Wonderland.
RDA + MARC 21
bibliographic record

100 1# $a Verdi, Giuseppe, $d1813-1901.

=
10 $a Otello :$b in full score / $c Giuseppe Verdi.
700 1# $i libretto based on (work) $a Shakespeare, William,
$d 1
 -11. $t Othello.
787 08 $i reproduction of (manifestation) $a Verdi, Giuseppe,
$d 1813-1901. $t Otello. $d Milan: Ricordi, c1913

%  ààà/"0#% àà à1

à

 à  à
RDA + MARC 21
authority record for a work:
100 1# $a Stoppard, Tom. $t Rosencrantz and Guildenstern
are dead

00 1# $w r $i based on (work) $a Shakespeare, William, $d
1
 -11. $t Hamlet

authority record for a person:

100 1# $a Clemens, Samuel, $d 183
-1910

00 ## $w r $i alternate identity $a Twain, Mark, $d 183
-
1910
RDA + post MARC 21
  
name of a person ------- title of a resource

RDA + post MARC 21 record environment

˜ data about entities:
´recordµ or cluster of data for person, work, expression
(as needed), manifestation, item «
˜ explicitly defined relationships between entities
˜ explicitly defined relationships means that MARC record
structure is no longer required
 RDA data
data inside MARC record wrapper

bibliographic
data

data outside MARC record wrapper

work person
data data
data of
another manifestation
work data
manifestation data data of
data about another
item work
Where is the future?
˜ data that supports resource discovery
˜ data that is visible on the web
˜ data that enables machine-actionable processing of data
˜ data that can be stored and used in new database
structures
˜ data that can connect us with other communities
RDA moves us forward

Y
5
takes us from where
we are

moves us to a new
track

opens up possibilities
for the future
Images from Flickr
Creative Commons attribution license

Dinner train by Slideshow Bruce

http://www.flickr.com/photos/springfieldhomer/95614622/

Cross track ² i{hone wall paper by CJ Schmit

http://www.flickr.com/photos/cjschmit/4623783487/

Behind the big red ball by Christopher Woo

http://www.flickr.com/photos/deks/3618803169/

Tracks by eirikref
http://www.flickr.com/photos/eirikref/432088535/
Thank you
Questions, comments


contact info: chris.oliver@mcgill.ca