rda test at lc module 1: overview what rda is; structure

RDA Test at LC

Module 1: Overview

What RDA Is;

Structure

RDA Test at LC: June 2010 -- Module 1 2

RDA is successor to AACR2

but is not AACR3 -- RDA is different from AACR2


RDA based on IFLA’s international models and principles

Functional Requirements for Bibliographic Records (FRBR; 1998)

Functional Requirements for Authority Data (FRAD; 2009)

Statement of International Cataloguing Principles (ICP; 2009)


Addresses user tasks

FRBR: Find Identify Select Obtain

FRAD: Find Identify Contextualize Justify

• ICP’s highest principle = “convenience of the user”


Is a content standard

Not a display standard (as was AACR2) Does have appendix D for ISBD and

appendix E for AACR2 style for access points

LC will continue using ISBD punctuation and AACR2 style for access points (also see LCPS 1.7)

Not an encoding standard LC will use MARC 21


For wider scope of resources

Response to what’s being acquired in libraries More elements for non-printed text resources More elements for non-text resources More elements for unpublished resources

Compatible with specialist manuals (DACS, CCO, DCRM(B) etc.)


Includes authority data instructions

Based on attributes and relationships in FRAD

Authorized/variant access points and elements will for now be documented in authority records


Has controlled vocabularies

Only a few closed: content, media, and carrier types; mode of issuance; etc. If term missing, tell PSD

Most are open: cataloger can supply term if needed term not in list Tell PSD which term used

Some vocabularies being registered on the Web

Training document #1 has list


What’s changing?

Changes in technology Impact on descriptive/access data

book catalogs card catalogs OPACs next generation

Move from classes of materials to elements and values (more controlled vocabularies)

Move from individual library to international audience


Internet

Catalogs are no longer in isolation Global access to data

Virtual International Authority File (www.viaf.org)

Integrate bibliographic data with wider Internet environment Share data beyond institutions


RDA developed for the future

Full advantage of RDA-based data: When authority and bibliographic data reside

in separate “packages” and records assembled when needed

When access points (if needed) can be assembled “on the fly”

When data for works and expressions can be reused for multiple manifestations


RDA appendices for transition

Appendix D mappings: ISBD to RDA - few changes from current

practice MARC 21 bibliographic format to RDA

Appendix E: Presentation and punctuation of access

points - few changes from current practice MARC 21 authority format mapping to RDA


Structure of RDA


RDA Structure

General introduction Identifying elements (entities and their

attributes) Ch. 1-7: work, expression, manifestation, item Ch. 8-16: person, family, corporate body, place

Relationships: ch. 17-22, 24-32 Appendices Glossary


RDA structure Not by class of materials: no separate

chapters for books, printed music, etc. Overarching principles applicable to all

Basic goals: identify and relate (from FRBR/FRAD user tasks and ICP)

Chapters: separate elements for goals Assemble those elements when need

authorized access points (instructions at end of chapters 6, 9-11)


Not to be read linearly Using an online tool:

“Jumping in” via keyword searches Going directly to elements from Table of

Contents (ToC) pane Following links Seeing some duplication of content (needed

for context) Separate RDA Toolkit training/demos Can use Training documents #3 and #4

to go to specific instructions


What is where in RDA?

Supplemental Training documents:

#2 = Where is it in RDA? (general information)

#3 = RDA core elements (listing of elements by

chapter for a general overview of RDA)

#4 = LC RDA core elements for the RDA Test

#6 = Bibliographic record: MARC to RDA

#7 = Authority record: MARC to RDA


Terminology

FRBR and FRAD “attributes” are “elements” in RDA

FRBR and FRAD Group 1 entities: Work Expression Manifestation Item


Group 1 entities

“Book”

– Door prop(item)

– Publication at bookstore -- any copy(manifestation)


Group 1 entities

“Book”

– Who translated?(expression)

– Who wrote?

(work)


AACR2 to RDA vocabulary

heading author, composer, etc.

main entry

uniform title

authorized access pointcreator

preferred title + authorized access point for creator if appropriate

(1) preferred title (+ other information to differentiate);

(2) conventional collective title



see reference

see also reference

physical description

chief source

variant access point

authorized access point for related entity

carrier description

preferred sources



GMD media type +

carrier type +content type


Examples of addressing user tasks

Variant title “if considered to be important for identification or access”

Length of the film “if considered important for identification or selection”

Other persons associated with the work “if considered important for access”

Cataloger’s note “to justify the … form of the access point”


Quiz on terminology


Core elements

Based on attributes mandatory for a national level record in FRBR and FRAD

Core elements (RDA 0.6): Some: always if applicable and available Others: depends upon situation = Core if … Agency can add others

LC’s core elements: Training document #4


“Core-ness” identified at element in RDA Toolkit

If always a core element (if applicable and available), label “CORE ELEMENT” appears below element name

If use as a core element depends upon the situation, the label “CORE ELEMENT” is followed by an explanation of the situation

If additional element selected by LC as core, an LCPS will say “CORE ELEMENT FOR LC” with or without an explanation


Core elements’ reminder (RDA 0.6)

Include all the core elements that are applicable and readily ascertainable

Don’t do research just to give a core element unless RDA instruction or LCPS says to do so


Other choices in RDA

Alternatives and options

“or” instructions

“agency preparing …” instructions

LC’s decisions in tables posted on PSD site and in LCPSs available on PSD site and in Toolkit


Choices: alternatives

Instructions saying to do something different from what the previous instructions said, e.g.,

Giving a general note about numerous minor changes in title proper of a serial

Using the label on a direct access electronic resource as source for title proper instead of viewing the resource


Choices: optional omissions

Instructions saying to do less than what the previous instructions said, e.g.,

Omitting corporate hierarchy in the publisher’s name

Omitting words in a long title proper


Choices: optional additions

Instructions saying to do more than what the previous instructions said, e.g.,

Adding birth/death dates even if that information isn’t needed to differentiate

Adding fuller form of name even if that information isn’t needed to differentiate


Choices: “or” instructions

Not labeled as alternatives but do offer different approaches – agency policy decision An example: when giving the extent of a resource

consisting entirely of unnumbered pages, give the exact number, an estimated number with “approximately”, or “1 volume (unpaged)”

Not all instructions with “or” wording are choices: some apply only to specific situations


Choices: “agency preparing …”

Result of internationalization: no longer assuming an Anglo-American context

Choices relate to Language of additions to access points Language of supplied data Script and transliteration Calendar Numeric system

rda test at lc module 1: overview what rda is; structure

Documents

rda test

lc module

rda structure

structure of rda slide

rda appendices

advantage of rda

rda appendix e

aacr2 slide