The framework:structure principles basic concepts Chris Oliver for RDA Workshop June 2010 June 2010

the framework: structure principlesbasic concepts

Chris Oliverfor RDA Workshop

June 2010

AACR2 to RDA

AACR2 deconstructed new concepts

new structure

new vocabulary

some new instructions

some changed instructions

Reconstruction into RDA

• every word has changed

• many instructions show visible continuity with AACR2

What you need to know to understand the changes?

RDA’s framework

3 important acronyms

FRBR Functional Requirements modelfor Bibliographic Records

FRAD Functional Requirements modelfor Authority Data

ICP Statement of International Cataloguing Principles

all 3 created under the auspices of IFLA

What you need to know to understand the changes

• organization and structure of RDA• alignment with FRBR and FRAD models

• principles• international cataloguing principles

• basic concepts• user tasks• entities, attributes and relationships• elements and core elements• extensible framework


• user tasks• entities, attributes, relationships FRBR/FRAD• organization and structure of RDA

• principles ICP

• data elements• core elements practical

design• extensible framework

Focus on the user

0.0

• RDA provides a set of guidelines and instructions on formulating data to support resource discovery.

• The data created using RDA to describe a resource are designed to assist users performing the following tasks:

User tasks

Bibliographic data

• Find• Identify• Select• Obtain

Authority data

• Find • Identify• Clarify• Understand

Consistent focus on the user

Throughout RDA:

data why include this data?

to support the user in completing one of the user tasks

Functional objectives

• RDA divided into 10 sections

• Each section begins with general guidelines

• Functional objectives and principles specific to the section

• Functional objectives =

the data (recorded or formulated according to the instructions in that section)

the user tasks

Example from Section 1

Section 1= Recording attributes of manifestations & items

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 …

RDA never lets you forget

• introduction begins with focus on user and user tasks

• functional objectives in each section

• instructions open to cataloguer judgment within the parameters of enabling the successful completion of user tasks

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, attributes, relationships

• entity = the object of a user’s interest

• entities that are of interest to someone who uses bibliographic and authority data

bibliographic entitiesentities specific to authority control

Bibliographic entitiesworkexpressionmanifestationitem

personfamilycorporate body

conceptobjecteventplace

FRBR Group 1products of intellectual or artistic endeavor

FRBR Group 2responsible for group 1 entities

FRBR Group 3 subjects (includes group 1 & 2)

Group 1 entities

workis realized through

expression is embodied in

manifestation is exemplified by

item

FRBR 3.1.1

Example of Group 1 entities

w = idea for Hamlet story (in Shakespeare’s head)

is realized through

e = original English text as he wrote it

is embodied in

m = published in Oxford by Oxford University Press in 1998

is exemplified by

i = copy owned by McGill with barcode no.

3102930136A

4 entities – 1 resource

• an item

• an exemplar of the Oxford 1998 manifestation

• an embodiment of the original English expression

• a realization of the work, Hamlet

Group 2 & 3 entitiesGroup 2 = entities responsible for group 1 entities

• person e.g. creating

• family e.g. owning

• corporate body e.g. producing

Group 3 = subjects of works • concept

• object• event • place+ all group 1 and 2 entities

Authority entities

bibliographic entities

nameidentifiercontrolled access point

rulesagency

entities on which authority data is focused

entities for authority control

entities that determine the content and form of access points

Authority entities


are known by

names and/or identifiers

which are the basis for

controlled access points

FRBR/FRAD entities in RDAbibliographic entities

workexpressionmanifestationitem


conceptobjecteventplace

concepts in RDA

name

identifier

controlled access point

Attributes

• characteristics of the entity• data to be recorded about the entity

examples of attributes:work: form of the work (or genre), medium of performance,

coordinates (map), intended audience …

expression: content type (form of expression), language of the expression, type of score …

manifestation: publisher, date of publication, form of carrier, extent of the carrier …

item: identifier (e.g. barcode), provenance, condition …

Attributes

examples of attributes:person: dates, titles of rank, office, etc., gender, …

family: type, dates, history, …

corporate body: place, dates, address, …

conceptobject term (pending release of FRSAD)eventplace

Relationships• link between one entity and another

• basis for navigation and support collocation

• 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

Primary Relationships

17.4 Recording Primary RelationshipsPrimary relationships are the relationships between a

work, expression, manifestation, and item that are inherent in the FRBR definitions of those entities:

a) the relationship between a work and an expression through which that work is realized

b) the relationship between an expression of a work and a manifestation that embodies that expression

c) the relationship between a manifestation and an item that exemplifies that manifestation

Primary Relationships

work expression manifestation item

Hamlet original text • London, 1603 RBD

• New York, 1998 MCL BIRK

French trans. tr. by Gide • Paris, 1946 EDUC

• Neuchatel, 1949 MCL

tr. by Bonnefoy • Paris, 1978 MACD

German trans. • Hamburg, 1834 MUSIC

audio-book • Paris, 1983 REDP

Examples of relationshipsexpression translation of work

manifestation embodiment of expression

work created by person

expression performed by person

manifestation produced by corporate body

work based on work

manifestation electronic reprod. manifestation

person member of family

family founded corporate body

Organization and Structure of RDA

2 main partsRecording attributes sections 1-4

Recording relationships sections 5-10

Divided into 10 sectionssections are organized according to the bibliographic entities


Section 1-4 = Recording attributes

Section 1. Recording attributes of manifestation and item

Section 2. Recording attributes of work and expression

Section 3. Recording attributes of person, family, and corporate body

Section 4. Recording attributes of concept, object, event, and place

[placeholder]

Organization and Structure of RDASections 5-10 = Recording Relationships

Section 5. Recording primary relationships between work, expression, manifestation, and item

Section 6. Recording relationships to persons, families, and corporate bodies associated with a

resource

Section 7. Recording the subject of a work [placeholder]

Section 8. Recording relationships between works, expressions, manifestations, and items

Section 9. Recording relationships between persons, families, and corporate bodies

Section 10. Recording relationships between concepts, objects, events, and places

[placeholder]

Organization and Structure of RDA• each chapter associated with a user task

Chapter 1: General guidelines on recording attributes of manifestations and items

Chapter 2: Identifying manifestations and itemsFRBR task = Identify

Chapter 3: Describing carriersFRBR task = Select

Chapter 4: Providing acquisition and access informationFRBR task = Obtain


Chapter 5: General guidelines on recording attributes of works and expressions

Chapter 6: Identifying works and expressionsFRBR task = Identify

Chapter 7: Describing contentFRBR task = Select


scope of RDA:

bibliographic data authority data

RDA aligned with FRBR and also aligned with FRAD

influence of FRAD: person, family, corporate body, place role of identifiers relationship between name +

entity

Person in RDAdefinition of person influenced by FRAD:

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”

Name in RDA


work


place

name

known by title

known by nameknown by nameknown by name

known by name

Principles2009 Statement of International Cataloguing Principles2009 final text of RDA including objectives & principles

ICP and RDA developed in sync0. 4.1 ICP “informs” RDA principles

no. 1 for ICP and RDA = Responsiveness to User Needs(RDA)

Convenience of the User(ICP)

RDA Objectives & Principles

Objectives• responsiveness to user

needs

• cost efficiency

• flexibility

• continuity

Principles• differentiation

• sufficiency

• relationships

• representation

• accuracy

• attribution

• common usage or practice

• uniformity

Role of Objectives & Principles

• instructions must be defensible + not arbitrary• real impact on the content of RDAfor example

objective = flexibilityThe 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 as a Content Standard

“what data should I record?”

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 as a Content Standard

implement in our current library environment

use in different metadata communities

ready to be used in newly emerging database structures

ready to be used in the future web environment

Role of Objectives & Principles

for exampleprinciple = representation

The data describing a resource should reflect the resource’s representation of itself.

result = impact on instructions about transcription

2.5.1.4 Recording Edition StatementsTranscribe an edition statement as it appears on the source of information. no instruction to use abbreviations transcribe what is on the source of information

Role of Objectives & PrinciplesPrinciple = Representation

Appendix B AbbreviationsB.4 Transcribed elementsFor 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

Data Elements

element = A word, character, or group of words and/or characters representing a distinct unit of bibliographic information.

appears similar to AACR2 definition, minus the reference to “areas”

actually quite different from AACR2

element as a key part of “well-formed metadata”JSC documents: RDA Scope and Structure

RDA Element Analysis

Data Elements

elements in line with metadata conventionselements, element sub-types, sub-elements

element contains data either about:

an attribute of an entity OR a relationship between entities

each element is discrete and precisely defined

Data Elements

each element is discrete and precisely defined

data is not embedded in long character strings

Data Elementsfor exampleAACR2: information embedded in a non-specific note

physical video format characteristics

description note fontMARC 500 base and applied

materials sound characteristics

requires that a human interpret information in record cannot be used reliably to search or to limit a search cannot be used for automated processing cannot generate a meaningful display

Data ElementsRDA: distinct and precise elements for each kind of data

video format characteristicsdifferent element fontfor each type of base materialdata applied material

sound characteristics

RDA: recommended controlled vocabulary for content of many elements

video format characteristics: beta, betacam, betacam SP, CED, D-2 … font: large print, giant printbase material: bristol board, canvas, cardboard, ceramic, glass …

Data Elements

RDA: precise elements – only one kind of data in an element

AACR2: date of publication, distribution, etc.MARC 21: 260 $cRDA: 4 different elements:

date of productiondate of publicationdate of distributiondate of copyright

Day 1 of Implementation

implementation in MARC 21 environment

continue with ambiguity

many RDA elements will map to one MARC subfield

potential for the future

designed to be in line with metadata that can be used in the online networked environment

More elements - e.g. for digital resources

new data elements: record carrier type for online resource; record extent:

1 online resource (1 image file)1 online resource (75 pages)

file typedata filestreaming video file

encoding formatDAISY GIF HTML

audio DVD audio image JPEG text PDFMP3 TIFF MS

Worduniform resource locator

Data Elements each element has the potential to be usable:

to indexto searchto build meaningful displays of data

data in element can be used by humans and machines can be used reliably to search or to limit a search can be used for automated processing can be used to generate a meaningful display

Core Elements

many new elements but don’t have to use them all

core elements

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

inclusion of other elements is discretionary

Core Elements core elements support a subset of user tasks

• identify and select a manifestation• identify works and expressions embodied in a

manifestation• identify the creator or creators of a work• find a person, family, or corporate body associated with

a resource• identify a person, family, or corporate body

summary of core elements in introduction: 0.6

general guidelines for each section: core elements

Core Elements certain elements are flagged as “core”

title properdesignation of editionpreferred name for the person

certain elements are flagged as “core if” date of distribution if date of publication not identifiedextent 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)

Extensible Framework framework to describe all known resources framework that can be extended to describe

resources yet to be developed

Extensible Framework

many data elements – each precisely defined

data elements can be used in any combination

clear distinction between content and carrier

work contentexpression content

manifestation carrieritem carrier

Extensible Framework

room for growth with framework of attributes and relationships

RDA framework can describe

any content any carrier

in addition, framework for categorizing resources

Categorization of Content & Carrier

RDA/ONIX frameworksupport needs of libraries and publishing industryhelp user to select appropriate resource

What is the categorization framework? consists of 3 elements that can be used in

multiple combinationseach element has controlled vocabulary replaces the GMD

Categorization of Content & Carrier

consists of three elements: content typemedia type

carrier type can use as many of each type as needed media is not core because it can be inferred from

carrier type to record content, media and carrier types not a display standard code all three to support better automated

processing (absence of data = ambiguous data)

Categorization of Content & Carriercontent type expression notated music

performed musicstill imagespoken wordtext

media type manifestation audiomicroformunmediated

carrier type manifestation audio cartridgeaudio discaudiocassette

Categorization of Content & Carrierbook Content type = textMedia type = unmediatedCarrier type = volume

music CD Content type = performed musicMedia type = audio Media type = computerCarrier type = audio discCarrier type = computer disc

Categorization of Content & Carrierweb page Content type = textMedia type = computerCarrier type = online resource

online videoContent type = two dimensional moving image Media type = computerCarrier type = online resource

Categorization of Content & Carrier controlled vocabulary three elements that can be used in multiple

combinations can immediately record content and carrier

information consistent values in the elements that can be

mapped in various waysmap to iconsmap to terms preferred by the user groupmap to terms in different languagesmap to newly developed terms


• user tasks• entities, attributes, relationships FRBR/FRAD• organization and structure of RDA

• principles ICP

• data elements• core elements practical

design• extensible framework

Documents

The framework:structure principles basic concepts Chris Oliver for RDA Workshop June 2010 June 2010