RDA: A Quick Introduction: Chris Oliver
RDA: A Quick Introduction: Chris Oliver
Chris Oliver
February 2nd, 2011
What is RDA?
new metadata standard that replaces AACR2
a set of practical instructions based on a theoretical
framework
To understand RDA:
• not simply a set of updated instructions
• new way of thinking about cataloguing data
1. scope of RDA
2. underlying theoretical framework
3. objectives and principles
4. an aspect of RDA’s design:
• elements and core elements
• designed for current databases and for future
databases and web environments
every word has
changed
RDA instructions
show visible
continuity with
AACR2
1 film reel 1 film reel
RDA: a quick introduction / Chris Oliver
AACR2 to RDA: continuity & change
AACR2 deconstructed
new concepts
new structure
new vocabulary
some new instructions
some changed instructions
RDA: a quick introduction / Chris Oliver
AACR2
stones
plus
framework
without
the framework
stones
plus
new
framework
versus AACR2 0.1
These rules are designed for use in the construction of
catalogues and other lists in general libraries of all sizes.
more international
beyond “Anglo‐American”
instructions made consistent and easy to use by many cultural,
religious, national communities
for example, options for the use of other languages, scripts,
calendars, numeric systems
not just for libraries
connecting with other cultural heritage communities
beyond the library “silo”
for example, instructions for archival resources
b. role of user tasks
c. entity relationship models
d. evidence of the models in the way RDA is organized
e. influence of FRAD
aligned with the FRBR and FRAD conceptual models
FRBR Functional Requirements for Bibliographic Records
1998
FRAD Functional Requirements for Authority Data
2009
FRAD is an extension of the FRBR model
both models developed under the auspices of IFLA
widely used data modelling technique:
entity relationship model
• entities
• attributes
• relationships
“functional”
data is important because of how it is used
use is operationalized as “user tasks”
The data created using RDA to describe a resource are
designed to assist users performing the following tasks:
Bibliographic data Authority data
find find
identify identify
select clarify
obtain understand
why record this data?
to support the user in completing one
of the user tasks
user tasks come from FRBR/FRAD models
user tasks are an essential part of RDA
RDA: a quick introduction / Chris Oliver
Functional objectives
RDA divided into 10 sections
Each section begins with general guidelines
Functional objectives and principles specific to the section
Functional objectives =
relationship between the data and the user tasks
(recorded or formulated according
to the instructions in that section)
1.2 Functional Objectives and Principles
The data describing a manifestation or item should enable the user to:
a) find manifestations and items that correspond to the user’s stated search
criteria
b) identify the resource described …
c) select a resource that is appropriate to the user’s requirements with
respect to the physical characteristics of the carrier and the formatting
and encoding of information stored on the carrier
d) obtain a resource …
cataloguer judgment = cataloguer determines if the data is
important for the successful completion of a user task
for example, from 3.7 Applied material
Record the applied material used in the resource if it is
considered important for identification or selection …
entities that are of interest to someone who uses
bibliographic and authority data
bibliographic entities
entities specific to authority control
concept
object
event FRBR Group 3
place subjects (includes group 1 & 2)
RDA: a quick introduction / Chris Oliver
Authority entities
bibliographic entities entities on which authority
data is focused
name
entities for authority control
identifier
controlled access point
(in RDA = authorized access point)
rules entities that determine the
agency content and form of access
points
RDA: a quick introduction / Chris Oliver
Attributes
characteristics of the entity
data to be recorded about the entity
examples of attributes:
work: title, genre, coordinates (map)
manifestation: publisher, date of publication, extent of the carrier
item: identifier (e.g. barcode), provenance, condition
person: dates, gender, a title of rank or office
corporate body: place, dates, address
object: term
2 main parts
Recording attributes sections 1‐4
Recording relationships sections 5‐10
Divided into 10 sections
sections are organized according to the bibliographic entities
Section 1‐4 = Recording attributes
Chapter 1: General guidelines on recording attributes of
manifestations and items
Chapter 2: Identifying manifestations and items
User task = Identify
Chapter 3: Describing carriers
User task = Select
Chapter 4: Providing acquisition and access information
User task = Obtain
Chapter 6: Identifying works and expressions
User task = Identify
Chapter 7: Describing content
User task = Select
person = an individual or an identity established by an
individual (either alone or in collaboration with one
or more other individuals)
scope of 9.0 = persons include fictitious entities
for example
works created by fictitious characters: Miss Piggy, Snoopy
relationship of person (bibliographic identity) to person
(individual)
designate relationship as “real identity” or “alternate identity”
the objectives and principles
how the objectives and principle shape RDA instructions,
looking at two examples
Convenience of the User
(ICP)
RDA: a quick introduction / Chris Oliver
RDA Objectives & Principles
Objectives Principles
responsiveness to user differentiation
needs sufficiency
cost efficiency relationships
flexibility representation
continuity accuracy
attribution
common usage or practice
uniformity
for example
objective = 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.
result = RDA is a “content standard”
RDA can be encoded using different encoding schema
e.g. MARC 21, MODS, Dublin Core, etc.
RDA data can be displayed using different display
conventions
e.g. ISBD, label display, etc.
RDA data can be stored in current databases and in new types
of database structures
AACR2 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
MARC 21 manual
MARC 21 245 $c statement of responsibility, etc.
245 04$aThe plays of Oscar Wilde /$cAlan Bird.
245 10$aHow to play chess /$cKevin Wicker ; with a foreword by
David Pritchard ; illustrated by Karel Feuerstein.
RDA: a quick introduction / Chris Oliver
RDA as a Content Standard
implement in our current library environment
can be used by different metadata communities
ready to be used in newly emerging database structures
ready to be used in the future web environment
RDA 2.5.1.4 Recording Edition Statements
Transcribe an edition statement as it appears on the source of
information.
no instruction to use abbreviations
transcribe what is on the source of information
Appendix B Abbreviations
B.4 Transcribed elements
For transcribed elements, use only those abbreviations found in
the sources of information for the element.
t.p. data recorded
3rd ed. 3rd ed.
Second edition Second edition
core elements
AACR2 element = similar definition
plus
… and forming part of an area of the description.
AACR2 elements are organized and embedded into areas
net effect is quite different
RDA element contains data either about:
a single attribute of an entity
OR a single relationship between entities
AACR2: date of publication, distribution, etc.
MARC 21: 260 $c
RDA: 4 different elements:
date of production
date of publication
date of distribution
date of copyright
day 1 implementation in MARC 21 environment – data will still be
ambiguous
RDA: a quick introduction / Chris Oliver
RDA data elements
remove ambiguity
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
• information that can be used by human or machine
day 1 implementation in MARC 21 environment – subfields for 502 already
implemented
RDA: a quick introduction / Chris Oliver
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
illustrative content
encoding format
other physical production method
details sound content
applied material
MARC 300 $b base material
reduction ratio
content or carrier
illustrative content encoding format
sound content production method
applied material
base material …
controlled vocabulary recommended for many elements
aspect ratio: full screen, wide screen, mixed
base material: Bristol board, canvas, cardboard, ceramic, glass,
leather, paper, parchment, vellum …
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
RDA: a quick introduction / Chris Oliver
Designed to be flexible and extensible
elements to describe all known types of content and carriers
easily extensible to describe resources yet to be developed
• many data elements – each precisely defined
• data elements can be used in any combination
not a level of description
core elements are a minimum “a floor, not a ceiling”
must include any additional elements required to differentiate
the resource or entity from a similar one
may include additional elements – as required to complete
user tasks
summary of core elements in introduction: 0.6
general guidelines for each section: core elements
certain elements are flagged as “core if”
date of distribution if date of publication not identified
extent is core if resource is complete or if the total extent is
known
element is core but can omit some data
place of publication (if more than one, only the first)
scope of RDA
theoretical framework based on the FRBR and FRAD
conceptual models
role of objectives and principles
data elements: an aspect of RDA’s design
Understanding RDA
• theoretical framework
• a framework for today and tomorrow
RDA: a quick introduction / Chris Oliver
Understanding RDA
day 1 of implementation:
“shoe‐horn” RDA into MARC
21
day 1 of implementation is
only the point of transition
RDA: not simply RDA in
MARC 21
day 1 of implementation
allows us to begin travelling
along the new track
Images from Flickr
creative commons attribution license
Road‐Side History by Owls Flight Photography
http://www.flickr.com/photos/kevinhooa/2370449243/
Old stones of Bauda Byzantine ruins by Hovic
http://www.flickr.com/photos/200000/2304353314/
Falling water by spike55151
http://www.flickr.com/photos/spike55151/14471574/
Data Represented in an Interactive 3‐D Form by Idaho National Laboratory
http://www.flickr.com/photos/inl/5097547405/