2-Background and Structure RDA Rev

 Screen images and RDA instructions from the
RDA Toolkit (www.rdatoolkit.org) used by

permission of the Co-Publishers for RDA
(American Library Association, Canadian Library
Association, and CILIP: Chartered Institute of
Library and Information Professionals)
2
 Increasingly complex library resources
 Lack of logical structure
 Mixing content and carrier data
 Hierarchical relationships missing
 Anglo-American centric viewpoint
 Written before FRBR
 Not enough support for collocation
 Before Internet and well-formed metadata
Ann Chapman, UKOLN

3
 Principles
 Content vs. carrier
 Logical structure
 Seriality
 Internationalization
4
 American Library Association
 Australian Committee on Cataloguing
 British Library
 Canadian Cataloguing Committee
 CILIP: Chartered Institute of Library and
Information Professionals
 Library of Congress
 and in 2012: Deutsche Nationalbibliothek
 future: expand governance
5
 Catalogs are no longer in isolation
 Global access to data
 Integrate bibliographic data with

wider Internet environment
 Share data beyond institutions
6
Databases,
Repositories Services
VIAF
LCSH
Web front
end
Power of “Linked data”

7
 Web-based
 Wide range of information carriers with

complexity of content
 Metadata (bibliographic information)
 Created by a wider range of personnel in
and outside libraries
 Element-based metadata schemas
▪ Dublin Core, ONIX, etc.
Ann Chapman, UKOLN

8
AACR3
9
IFLA - Principles, Conceptual models, ISBD/ISSN
 ONIX (Publishers) – types of content, media, carriers
Dublin Core, IEEE/LOM, Semantic Web, W3C
“Data Modeling Meeting” - London 2007
RDA/MARC Working Group (MARBI)
10
 Cataloging specialists: law, religion, music, etc.
 Archives and museums
11
 A new standard for resource description
and access
 Designed for the digital world
• Optimized for use as an online product
• Description and access of all resources
▪ All types of content and media
• Resulting records usable in the digital
environment (Internet, Web OPACs, etc.)
12
 Rules should be easy to use and interpret
 Be applicable to an online, networked environment
 Provide effective bibliographic control for all types of
media
 Encourage use beyond the library community
 Be compatible with other similar standards
 Have a logical structure based on internationally- agreed
principles
 Separate content and carrier data
 Examples – more of them, more appropriate
13
 Functional Requirements for
Bibliographic Records (FRBR; 1998)
 Functional Requirements for Authority
Data (FRAD; 2009)
 Statement of International Cataloguing
Principles (ICP; 2009)
14
• Convenience of user • Consistency and
• Representation Standardization
• Common usage • Integration
• Accuracy • Defensible, not
• Sufficiency and arbitrary
necessity
• Significance
• Economy • If contradict, take a
defensible, practical
solution.
15
FRBR: FRAD:
 Find  Find
 Identify  Identify
 Select  Contextualize
 Obtain  Justify
• ICP’s highest principle = “convenience of

the user”
16
 Entities
 Relationships
 Attributes (data “elements” in RDA)
relationship
One Entity Another Entity

 National level required elements
17
Person
Work
created
was created by
Shakespeare Hamlet
18
Group 1: Products of intellectual &
artistic endeavor = bibliographic
resources
 Work
 Expression
 Manifestation
 Item
19
“Inherent Group 1
Work
relationships”
is realized through
Expression
is embodied in
----------------------------------------------------------
Manifestation
recursive
one is exemplified by
many Item
20
Work
Expression  Inherent among the Group

Manifestation
1 entities
 Content relationships
Item
among works/expressions
 Structural relationships
Whole-Part
Derivative Sequential
Accompanying
21
Family of Works
Equivalent Derivative Descriptive
Free
Review
Translation
Microform Edition Casebook
Summary
Reproduction Abstract Dramatization
Simultaneous Abridged Digest Criticism
“Publication” Edition Novelization
Screenplay
Copy Libretto
Illustrated Evaluation
Revision
Edition Change of Genre
Exact
Parody Annotated
Reproduction Translation Expurgated
Imitation Edition
Edition
Variations Same Style or

Facsimile Arrangement Thematic Content
or Versions Commentary
Slight
Reprint Adaptation
Modification
Original Work - Same Work –

Cataloging Rules Cut- New Work
Same New Expression
Off Point
Expression
 Manifestation
 Work  ID
 ID  Title
 Title  Statement of responsibility
 Edition
 Date  Imprint (place, publisher,
 etc. date)
 Form/extent of carrier
 Terms of availability
 Mode of access
 Expression  etc.
 ID
 Form  Item
 Date  ID
 Language  Provenance
 Location
 etc.  etc.
23
Group 2: Those responsible for Group 1
entities – or are the subject of works:
 Persons
 Families
 Corporate bodies
24
 Intellectual or artistic creation (for
Work)
 Realization of work (for Expression)
 Production, publication, distribution, or
manufacture (for Manifestation)
 Custodian (for Item)
25
Group 3:Subjects of works
 Groups 1 & 2 plus
 Concept
 Object
 Event
 Place
Subject relationship
26
 But the concepts of the three groups are in
our catalogs
 The concepts have not been clear in past
cataloging rules
 More clarity for catalogers, for designers of

databases/catalogs, and for users
27
ACOSTA (CHRISTOVAL).
Tractado de las drogas, y medicinas de las Indias
Orientales, con sus plantas. Burgos, 1578. 4o
Another copy.
The same. Ital. Venetia, 1585. 4o
Another copy.
Tractado en loor de las mugeres. Venetia, 1592. 4o
28
ACOSTA (CHRISTOVAL).
Tractado de las drogas, y medicinas de las Indias
Orientales, con sus plantas. Burgos, 1578. 4o
Another copy.
The same. Ital. Venetia, 1585. 4o
Another copy.
Tractado en loor de las mugeres. Venetia, 1592. 4o
Person Work Expression Manifestation Item
29
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No. : 47023612
LCCN Permalink : http://lccn.loc.gov/47023612
Type of Material : Book (Print, Microform, Electronic, etc.)
Personal Name : Shakespeare, William, 1564-1616.
Main Title : ... Hamlet, traduit par André Gide.
Published/Created : [Paris] Gallimard [1946]
Description : 2 p. l., 7-237, [2] p. 17 cm.
CALL NUMBER : PR2779.H3 G5Copy 1

-- Request in : Jefferson or Adams Bldg General or
Area Studies Reading Rms
30
Person
LC Control No. : 47023612 Work

31
LC Control No. : 47023612 Expression

32
LC Control No. : 47023612 Manifestation

33
LC Control No. : 47023612
Description : 2 p. l., 7-237, [2] p. 17 cm. Item
34
35
 Based on principles
 Based on conceptual models
 Content, not encoding, standard
 More international
 Wider scope of resources
 Includes authority data
 Has controlled vocabularies
 Changes in instruction vocabulary
 Core elements
36
 Not a display standard (as is AACR2)
 Does have appendix D for ISBD and appendix
E for AACR2 style for access points
 Not an encoding standard
 Use whatever schema you prefer (MARC 21,
Dublin Core, etc.)
 Bibliographic Framework Transition Initiative
37
 Focus on local user needs
 Choice of agency preparing the description:

 Language of additions to access points
 Language of supplied data
 Script and transliteration
 Calendar
 Numeric system
38
 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
39
 Based on attributes and relationships in
FRAD
 Authorized/variant access points and

elements will for now continue to be
documented in authority records
40
 Only a few closed: content, media, and carrier
types; mode of issuance; etc.
 Most are open: cataloger can supply term if
needed term not in list
 Vocabularies being registered on the Web
(http://metadataregistry.org/rdabrowse.htm)
-- goal of multiple languages and/or scripts
41
 heading authorized access point
 author, composer,
etc. creator
 main entry
preferred title + authorized
access point for creator if
appropriate
 uniform title
(1) preferred title (+ other
information to differentiate);
(2) conventional collective title
42
 see reference variant access point
 see also reference authorized access point

for related entity
 physical description carrier description
43
 GMD media type +
carrier type +
content type
 chief source preferred sources
44
 General introduction
 Identifying characteristics (entities and their
elements)
 Ch. 1-7: work, expression, manifestation, item
 Ch. 8-16: person, family, corporate body, place
 Relationships: ch. 17-37
 Appendices
 Glossary
 Index
45
 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)
46
 Using the online RDA Toolkit:
 “Jumping in” via keyword searches
 To elements from Table of Contents pane
 Following links
 Seeing some duplication of content (needed for context)
 Can print chapters from Toolkit

 Printed text version of RDA is available
 Publishers considering Essential RDA
47
 Based on attributes mandatory for a
national level record in FRBR and FRAD
 Core elements listed as a group in RDA
0.6 and separately in appropriate
chapters
 Agency, consortium, etc., can add others
48
 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
49
 Alternatives and options – marked in
the RDA Toolkit with a green vertical
line to left of text
 “or” instructions
 “agency preparing …” instructions
50
 Policy statements by the Library of
Congress and the participants in the
Program for Cooperative Cataloging
 Identified in the RDA Toolkit by the icon
 Free access to these policy statements in

the RDA Toolkit
 Some decisions still pending
51
Examples: option and LC-PCC PS icons
52
 Phase 1: Mark records (with 667) that need evaluation or
revision before use under RDA (summer 2012;
completed)
 Phase 1.5: Deal with 700 fields for RDA added to AACR2
records
 Phase 2: Make mechanical changes where possible to
recode to RDA (March 2013)
 Phase 3: No plan (yet) to change remaining ‘acceptable’
AACR2 records (7.6 million – 95%)
 http://www.loc.gov/catworkshop/RDA
%20training%20materials/LC%20RDA
%20Training/Authorities
%20Presentations/RDA%20special
%20topic_changes%20to%20lc-naco
%20file.ppt
 RDA Appendix D mappings:
 ISBD to RDA
 MARC 21 bibliographic format to RDA
 RDA Appendix E:
 Presentation and punctuation of access points
 MARC 21 authority format mapping to RDA
 Mappings (MARC/RDA) in the RDA Toolkit

 Free – on the Tools tab
55

2-Background and Structure RDA Rev

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2-Background and Structure RDA Rev

Uploaded by

Copyright:

Available Formats

 Screen images and RDA instructions from the

RDA Toolkit (www.rdatoolkit.org) used by

Ann Chapman, UKOLN

 Integrate bibliographic data with

Power of “Linked data”

 Wide range of information carriers with

Ann Chapman, UKOLN

RDA/MARC Working Group (MARBI)

• ICP’s highest principle = “convenience of

One Entity Another Entity

Expression  Inherent among the Group

Variations Same Style or

Original Work - Same Work –

 More clarity for catalogers, for designers of

Person Work Expression Manifestation Item

CALL NUMBER : PR2779.H3 G5Copy 1

CALL NUMBER : PR2779.H3 G5Copy 1

CALL NUMBER : PR2779.H3 G5Copy 1

CALL NUMBER : PR2779.H3 G5Copy 1

 Choice of agency preparing the description:

 Authorized/variant access points and

 see also reference authorized access point

 chief source preferred sources

 Chapters: separate elements for goals

 Can print chapters from Toolkit

 If use as a core element depends upon the

 “agency preparing …” instructions

 Free access to these policy statements in

 Mappings (MARC/RDA) in the RDA Toolkit

You might also like