Transcript What Do You Need to Know?

LC Training for RDA:
Resource Description & Access
Module 1:
Introduction to RDA;
Identifying Manifestations and Items
Cooperative and Instructional Programs Division
Library of Congress
2012
Acknowledgements



This course has been adapted from
training delivered by Barbara Tillett and
Judith Kuhagen, Library of Congress
Policy and Standards Division, to the
Georgia Public Library Cataloging Summit,
August 2011.
It incorporates the “Refresher Training”
conducted for LC’s RDA Testers in October
2011.
COIN gratefully acknowledges PSD’s
permission to adapt the material for the
present purpose
2
About This Material


This training material has been created
for a primary audience of Library of
Congress staff. Other audiences are
welcome to utilize it as they see fit.
However, it should be understood that it
reflects policies for LC staff, and should
not necessarily be interpreted to either
prohibit or require specific practices for
persons external to LC.
3
Learning Objectives for Module 1 -- Introduction
to RDA; Identifying Manifestations and Items
o
o
o
o
Introduction and Background
Overview of RDA
Supplemental Resources
Identifying Manifestations and Items
4
Unit 1: Introduction and Background



Why RDA?
How Did RDA Come to Be?
FRBR as a Foundation of RDA
5
“Why RDA?”
‘Why don’t we just revise AACR2?’


Evolving cataloging environment
RDA an improvement over AACR2
6
The Cataloging Environment -- Internet

Catalogs are no longer in isolation



Global access to data
‘linked data systems’
Integrate bibliographic data with
wider Internet environment


Share data beyond institutions
Any user – any place – any time
7
The Cataloging Environment
Databases,
Repositories
Services
VIAF
LCSH
Web front
end
8
The Cataloging Environment -- Current
Web-based
Wide
range of information carriers
More types of content and 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.
9
The Problems with AACR2

Increasingly complex

Lack of logical structure

Mix of content and carrier data

Hierarchical relationships are missing

Anglo-American centric

Pre-dates FRBR

Not enough support for ‘collocation’

Did not foresee Internet and well-formed
metadata or vocabularies
10
How Did RDA Come To Be?
‘AACR3?’
11
Resource Description & Access
AACR
3
12
Collaborations with Other
Communities

IFLA


ONIX (Publishers)



Principles, Conceptual models, ISBD/ISSN
Types of content, media,and carriers
Dublin Core, IEEE/LOM, Semantic Web,
W3C
RDA/MARC Working Group (MARBI)
13
Other Collaborations

Law Library community


Hebraica and Religion Teams at LC


AMIM2 and Ch.6 proposals for music
Prints & Photographs Division


DACS
Music Division, MBRS, Music Library
Association


Bible proposals
Mss/Archives staff at LC (MSS, NUCMC,
American Folklife Center, Rare Books)


Treaties
CCO
Geography and Map Division
14
15
A Tool for the Digital World

Optimized for use as an online product


Description and access of all resources



RDA Toolkit
All types of content and media
Resulting records usable in the digital
environment (Internet, Web OPACs,
etc.)
Resulting records readily adaptable to
newly emerging database structures
16
RDA Specific Goals








Easy to use and interpret
Applicable to an online, networked
environment
Provide effective bibliographic control for all
types of media
Encourage use beyond library community
Compatible with other similar standards
Have a logical structure based on
internationally agreed-upon principles
Separate content and carrier data, and
separate content from display
Examples – numerous and appropriate
17
FRBR as a Foundation of RDA



Functional Requirements for
Bibliographic Records (FRBR; 1998)
Functional Requirements for Authority
Data (FRAD; 2009)
Statement of International
Cataloguing Principles (ICP; 2009)
18
International Cataloguing Principles
(ICP)
o
o
o
o
o
o
o
o
o
o
Convenience of the user
Representation
Common usage
Accuracy
Sufficiency and necessity
Significance
Economy
Consistency and standardization
Integration
Defensible, not arbitrary
• If you contradict, take a defensible, practical solution.
19
Family of Works
Equivalent
Descriptive
Derivative
Free
Translation
Edition
Microform
Reproduction
Simultaneous
“Publication”
Abridged
Edition
Copy
Revision
Exact
Reproduction
Translation
Facsimile
Reprint
Original
Work - Same
Expression
Variations
or Versions
Illustrated
Edition
Summary
Abstract Dramatization
Digest
Novelization
Screenplay
Libretto
Casebook
Criticism
Evaluation
Change of Genre
Parody Annotated
Imitation Edition
Expurgated
Edition
Arrangement
Review
Same Style or
Thematic Content
Commentary
Slight
Modification
Adaptation
Same Work –
Cataloging Rules New Work
New Expression
Cut-Off Point
FRBR/FRAD Refresher –
Relationships
Work
Inherent Group 1
Relationships
is realized through
Expression
is embodied in
Manifestation
is exemplified by
Item
21
FRBR/FRAD Refresher –
Relationships
Work
Expression
Relationships
Between Groups 1 and 2
Manifestation
Item
is owned by
is produced by
is realized by
is created by
Person
Family
Corporate Body
22
FRBR and RDA




FRBR offers a structure to address user
tasks
FRBR entities and elements translate into
RDA data elements
RDA combines FRBR conceptual model
with cataloging principles
Foundations for:



cataloger judgment
better systems for the future
FRBR not a cataloging code -- but shows
how users can benefit from a system
based on FRBR entities and relationships
23
How FRBR/RDA is
Already Evident in LC ILS
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No.
LCCN Permalink
Type of Material
Personal Name
Main Title
Published/Created
Description
:
:
:
:
:
:
:
47023612
http://lccn.loc.gov/47023612
Book (Print, Microform, Electronic, etc.)
Shakespeare, William, 1564-1616.
... Hamlet, traduit par André Gide.
[Paris] Gallimard [1946]
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
Person
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No.
LCCN Permalink
Type of Material
Personal Name
Main Title
Published/Created
Description
:
:
:
:
:
:
:
47023612
Work
http://lccn.loc.gov/47023612
Book (Print, Microform, Electronic, etc.)
Shakespeare, William, 1564-1616.
... Hamlet, traduit par André Gide.
[Paris] Gallimard [1946]
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
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No.
LCCN Permalink
Type of Material
Personal Name
Main Title
Published/Created
Description
:
:
:
:
:
:
:
47023612
Expression
http://lccn.loc.gov/47023612
Book (Print, Microform, Electronic, etc.)
Shakespeare, William, 1564-1616.
... Hamlet, traduit par André Gide.
[Paris] Gallimard [1946]
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
26
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No.
LCCN Permalink
Type of Material
Personal Name
Main Title
Published/Created
Description
:
:
:
:
:
:
:
47023612
Manifestation
http://lccn.loc.gov/47023612
Book (Print, Microform, Electronic, etc.)
Shakespeare, William, 1564-1616.
... Hamlet, traduit par André Gide.
[Paris] Gallimard [1946]
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
27
Shakespeare, William, 1564-1616. Hamlet. French.
LC Control No.
LCCN Permalink
Type of Material
Personal Name
Main Title
Published/Created
Description
:
:
:
:
:
:
:
47023612
http://lccn.loc.gov/47023612
Book (Print, Microform, Electronic, etc.)
Shakespeare, William, 1564-1616.
... Hamlet, traduit par André Gide.
[Paris] Gallimard [1946]
Item
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
28
You see, FRBR is not so very
different from what we do now!
29
Collocation

Objectives of a
catalog, to display:




All works
associated with a
person, etc.
All expressions of
the same work
All manifestations
of the same
expression
All items/copies
of the same
manifestation
Don Quixote
English
French
Cervantes
Exemplary
novels
German
Spanish
Madrid, 1979
Library of Congress
Copy 1
Green leather binding
30
Unit 2: Overview of RDA



RDA Terminology
RDA: What it is
The Structure of RDA
31
RDA Terminology
AACR2
RDA
heading
authorized access point
author, composer,
artist, etc.
creator
main entry
preferred title and, if
appropriate, the authorized
access point for the creator
uniform title
Two RDA counterparts:
1. the preferred title and any
differentiating information;
2. a conventional collective
title such as “Works”
32
RDA Terminology
AACR2
RDA
see reference
variant access point
see also
reference
authorized access point for
related entity
physical
description
carrier description
general material
designator
three elements:
1. content type
2. media type
3. carrier type
chief source
preferred sources
33
RDA: What it is -A Content Standard

Not a display standard (as is AACR2)

But it does contain …



Appendix D for ISBD
Appendix E for AACR2 style for access points
Not an encoding standard

‘Schema-neutral’

Can use:



MARC 21
Dublin Core
etc.
34
RDA: What it is -More International


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
35
RDA: What it is –
Wider Scope of Resources


What’s being acquired in libraries
More elements for




non-printed text resources
non-text resources
unpublished resources
Defers to specialist manuals of
some collaborative communities
36
RDA: What it is -Authority Data


Based on attributes and
relationships in FRAD
Authorized/variant access points
and elements will for now continue
to be documented in authority
records
37
RDA: What it is -Controlled Vocabularies

Only a few are closed lists





Most are open lists


Content type
Media type
Carrier type
Mode of issuance
Cataloger can supply term if not in list
Vocabularies registered on the Web
(http://metadataregistry.org/rdabrowse.htm)
38
The Structure of RDA:
General Structure



Table of Contents
General introduction
Specific instructions

Entities and their attributes
Group 1 (Chapters 1-7)
 Group 2 (Chapters 8-16)





Relationships: ch. 17-22, 24-32
Appendices
Glossary
Index
39
The Structure of RDA:
Not Organized Like AACR2

Not by class of materials




No separate chapters for books, maps,
printed music, etc.
Overarching principles applicable to all
identify and relate user tasks
Elements addressed separately

To assemble elements when needed
(e.g., in authorized access points), see
the instructions at the end of chapters
6, 9-11)
40
The Structure of RDA:
Not a Linear Resource

Read purposefully





Keyword searches
Follow links
Jump directly from Table of Contents
Some duplication of content (context)
ALA also publishes:


Printed text version of RDA is available
Printed version of the RDA element set (a
subset of the RDA content)
41
The Structure of RDA:
Core-ness


Based on attributes mandatory for a
national level record (FRBR/FRAD)
Defined at the element level



Core elements listed:



CORE ELEMENT
Always
“Core if” – situation described
as a group in RDA 0.6
separately in appropriate chapters
LC has identified additional elements
as “LC Core”
42
National Library of New Zealand




Reviewing LC list of core elements
Establishing our policy for these
elements
Not yet completed
2 documents


List of core elements for NLNZ
Cataloguing policy decisions for those
elements. NLNZ RDA policy-options and
alternatives 2012

G/Fileplan/Bib Services/Non-Clio formats/RDA
training/RDA core elements
43
The Structure of RDA:
Alternatives, Options, and Exceptions



Clearly labeled in the RDA Toolkit by
green vertical bars and legends
Alternatives to an instruction
Options



Additional data
Omission of data
“agency preparing …” instructions
44
The Structure of RDA:
Library of Congress Policy Statements



To facilitate a standard interpretation
and application of alternatives,
options, and exceptions
If LC Cataloger, follow LCPS in all
cases
Follow green link in Toolkit
45
National Library of New Zealand
policy statements
Mirror and often endorse LC policy
statements, with 2 exceptions
1. Elements where data is recorded in
both Māori and English
2. Policy/criteria are being developed
to address instructions which use
the words “if it is considered useful
…” or “if it is considered
necessary..”

46
The Structure of RDA:
Examples




Illustrate the specific instruction
under which they appear
Normally given without showing
preceding or enclosing punctuation
Illustrate elements as they would be
recorded by an agency whose
preferred language is English
Appear in yellow shading
47
Unit 3: Supplemental Resources

ABA RDA Web Page

http://www.loc.gov/aba/rda/
Documentation
 Webcasts
 Training material
 Exercises and examples
Catalogers Learning Workshop
 http://www.loc.gov/catworkshop/RDA%20training
%20materials/LC%20RDA%20Training/LC%20RD
A%20course%20table.html
 LC’s training materials
Program for Cooperative Cataloging Web Page
 http://www.loc.gov/aba/pcc/
 PCC policies
 Task Group reports



48
Supplemental Resources –
“R-Documents”
R-1
LC RDA core elements
R-2
[no longer relevant; targeted at LC RDA Testers]
R-3
[no longer needed]
R-4
Importing records for textual monographs -- for
LC RDA catalogers and technicians – we will look
at this, but not just yet
R-5
MARC 21 encoding to accommodate RDA
elements: LC practice for November 2011+ - we
will also check this one for its relevance to NLNZ
R-6
Name authority record printouts
R-7
Some possible RDA implementation scenarios
R-8
Not applicable to NLNZ
49
Unit 4: Identifying
Manifestations and Items





Identifying RDA Records
Sources
Transcription
Where are the Instructions?
Detailed Discussion of Elements
50
Identifying RDA Records


Leader/18
contains the
value “i” (ISBD
punctuation
included)
040 $e
contains the
code “rda”
51
Sources

Preferred source: source of title proper

More sources for information


Whole resource, with priority order
Then any other source

Brackets if from outside the resource

Three categories (RDA 2.2.2.2 – 2.2.2.4)



Pages, leaves, etc., or images of pages …
Moving images
All other resources
52
Sources:
Resources with Pages, Leaves, etc.


(or images of pages, leaves, etc.)
RDA 2.2.2.2 priority order:








Title page, title sheet, etc.
Cover
Caption
Masthead
Colophon
If none of these, source containing title
If no title, source with formal presentation
Exception for microform or digital resource

Eye-readable label – also followed by NLNZ
53
Sources: Resources Issued in
More Than One Part


e.g., serials, multiparts, integrating
resources, kits
RDA 2.1.2.3



If sequentially numbered, use the lowestnumbered issue or part available
If unnumbered or not sequentially
numbered, use the issue or part with the
earliest date of issue
If the concept of sequential numbering is
not appropriate (e.g., for a kit), use the
resource as a whole; if this is not possible,
generally determine the main part
54
Sources:
Other Sources of Information if you
really can’t find a title

RDA 2.2.4 priority order




Accompanying materials
Container not issued as part of the
resource
Other published descriptions
Any other source (e.g., a reference
source that indicates how the resource
is commonly known)
55
Transcription: ‘Take What You See
and Accept What You Get’


ICP Principle of Representation
Generally, do not alter what is on
the resource


Accurate representation
Encourage re-use of found data
56
Transcription: ‘Take What You See
and Accept What You Get’



What does this mean for you?
Alternatives at RDA 1.7.1 allow for inhouse guidelines for capitalization,
punctuation, numerals, symbols,
abbreviations, etc. (in lieu of RDA
instructions)
LCPS 1.7.1
•
•
General guidelines on transcription
LC policy generally adheres to “Take What
You See and Accept What You Get.”
57
Transcription:
Capitalization

RDA 1.7.2


LCPS 1.7.1 First Alternative



“Apply the instructions on capitalization
found in Appendix A.”
“For capitalization of transcribed
elements, either “take what you see” on
the resource or follow [Appendix] A.”
Your choice! For LC cataloguers.
At NLNZ we will follow Appendix A
for capitalisation.
58
Transcription:
Capitalization
Accepting found capitalization:
245 10 $a Cairo : $b THE CITY VICTORIOUS /
$c Max Rodenbeck.
250 ## $a FIRST VINTAGE DEPARTURES EDITION.
Changing found capitalization:
245 10 $a Cairo : $b the city victorious /
$c Max Rodenbeck.
250 ## $a First Vintage Departures edition.
These are equally acceptable! for
LC but at NLNZ the second option is
preferred
59
Transcription: Punctuation, Numerals,
Symbols, Abbreviations, etc.

LCPS 1.7.1 First Alternative


“follow the guidelines in 1.7.3– 1.7.9
and in the appendices”
Generally, follow what is on the
resource
60
Transcription: Transcribed Elements
vs. Recorded Elements

Distinction between transcribed
elements and recorded elements.


For transcribed elements, generally
accept the data as found on the
resource.
For recorded elements, the found
information is often adjusted (for
example, the hyphens in an ISBN are
omitted).
61
Transcription:
Language and Script

RDA 1.4



Non-transcribed elements




“Transcribe … in the language and script found in the
resource”
List of elements to be transcribed
When recording other elements (e.g., extent, notes),
record them in English)
When adding data within an element, record it in the
language and script of the element to which it is added
When supplying an element, generally supply in English
Regarding non-Latin scripts, LC policy is to
record a transliteration instead, or to give both
(using the MARC 880 fields) NLNZ will record a
transliteration but won’t add 880 fields because
we don’t have capability (people or IT)
62
RDA Chapters for the Remainder
of this Module


The remainder of this module covers the
identification of manifestations and items.
This will be covered over the next 2 weeks.
It does not cover the identification of works and expressions,
nor the recording of authorized access points or relationships.
Those topics will be covered in subsequent modules.

NLNZ cataloguers: look at 1.7 in RDA and
our policy document, read the first 40 slides
of this presentation. Q&A for the last 30
minutes of this morning’s session.
63
What am I Cataloging?
64
RDA Chapters for the Remainder
of this Module

Chapter 2: Identifying manifestations and items

Primary focus on: LC core elements as adopted
by NLNZ and recorded in our core elements short
list and core elements policy document
65
Core Elements from Chapter 2:
“Identifying Manifestations
and Items”
•Include all applicable core elements
•Add extra elements only if the core don’t distinguish the
resource from similar resources
•Extra elements can be from chapters 2,3 or 4
66
Title and Statement of Responsibility
(RDA 2.3 – 2.4)




Title proper
Parallel title proper
Other title information
Statement of responsibility
67
Title Proper



CORE ELEMENT
RDA 2.3.2
Scope = “the chief name of a resource
(i.e., the title normally used when citing
the resource)” = the title on what’s being
cataloged

Sources:



Preferred source of information: 2.2.2 - 2.2.3
If no title within the resource: 2.2.4
MARC 245 $a $n $p
68
Title Proper Transcription


General guidelines on titles (RDA 2.2.1)
Principle of representation (RDA 2.3.1.4)

Don’t correct errors for monographs




no more “[sic]” or “[i.e., ____ ]”
give note to explain
Do correct errors for serials and integrating
resources to have a stable title
Changes in title proper (RDA 2.3.2.12 2.3.2.13)

same as AACR2
69
Examples:
Error in Title Proper
AACR2 record for a monograph:
245 $a Teusday’s [i.e. Tuesday’s] tasks
RDA record for this monograph:
245 $a Teusday’s tasks
246 $i Corrected title: $a Tuesday’s tasks
70
Parallel Title Proper

LC CORE ELEMENT

RDA 2.3.3



Scope = title proper in another language or script
“that is presented as the equivalent of the title
proper” RDA 2.3.3.1
Sources expanded to any source -- not just same
source as title proper – there is a proposal before the
JSC next month to say that parallel titles can only be
sourced from within the resource.
MARC 245 $b
71
Other Title Information





LC CORE ELEMENT
RDA 2.3.4
Scope = information that appears
in conjunction with, and is
subordinate to, the title proper of a
resource.
From same source as title proper
MARC 245 $b
72
Variant Titles


“A title associated with a resource
that differs from a title recorded as
the title proper, a parallel title
proper, other title information,
parallel other title information,
earlier title proper, later title proper,
key title, or abbreviated title”
RDA 2.3.6
73
Recording Variant Titles in MARC

LCPS 2.3.6.3



Record a variant title in MARC field 246 –
most variant titles are recorded in this field
Some variant titles are recorded in MARC
field 740. These are variant titles for works
that are parts of collections. RDA refers to
collections as aggregate works.
Omit any initial article from the variant
title unless the intention is to file on the
article
74
Statement of Responsibility
Relating to Title Proper - Scope




CORE ELEMENT if it relates to title proper
RDA 2.4.1
Scope = “a statement associated with the
title proper of a resource that relates to the
identification and/or function of any persons,
families, or corporate bodies responsible for
the creation of, or contributing to the
realization of, the intellectual or artistic
content of the resource”
MARC 245 $c
75
Statement of Responsibility
Relating to Title Proper - Sources

Take statements of responsibility relating to
title proper from the following sources (in
order of preference):




a) the same source as the title proper
b) another source within the resource itself
c) one of the other sources of information specified
under 2.2.4
Sources expanded: square brackets only if
from outside the resource
76
Statement of Responsibility Relating
to Title Proper - Transcription


Transcribe a statement of responsibility in the form in
which it appears on the source of information (follow
general guideline in RDA 1.7)
LCPS: “Generally do not abridge a statement of
responsibility.” See also our policy document under rule
2.4.1.4
Source:
Dr. Logan Carroll, Harvard Medical School
RDA/LCPS:
245 … / $c Dr. Logan Carroll, Harvard Medical
School.
RDA allows:
245 … / $c Dr. Logan Carroll.
77
Statement of Responsibility Relating
to Title Proper - Transcription

LCPS: “Generally do not omit names in a
statement of responsibility.”
“Rule of Three” -- Change from AACR2!
Source: by Susan Brown, Melanie Carlson, Stephen
Lindell, Kevin Ott, and Janet Wilson.
RDA allows: 245 $a … / $c by Susan Brown [and four
others].
RDA/LCPS: 245 $a … / $c by Susan Brown, Melanie
Carlson, Stephen Lindell, Kevin
Ott, and Janet Wilson.
AACR2: 245 $a … / $c by Susan Brown … [et al.].
78
If Multiple Statements ...



Only the first recorded is required
Record in the order indicated by the sequence, layout,
or typography of the source of information (RDA
2.4.1.6) Note references to special rules for
performers, narrators, presenters at 2.4.1
If not giving all statements of responsibility, give
preference to those identifying creators of intellectual
or artistic content (RDA 2.4.2.3)see NLNZ policy
document under rule 2.4.2. We would always
transcribe both statements below as both identify
creators of intellectual content
On source: “introduction by ______”
“written by _____”
If only transcribing one in 245 $c, give
“written by _____”
79
Designation of Edition and …
Named Revision of an Edition





LC CORE ELEMENT
RDA 2.5.2 and 2.5.6
Scope of Designation of edition = “a
word, character, or group of words
and/or characters, identifying the
edition to which a resource belongs”
Scope of Designation of a named
revision … = “... particular revision of a
named edition”
MARC 250 $a
80
What is a named revision of an edition?

Its an edition statement that is then
added to, indicating a further
Named revision of
change edition
th
4

edition
E.g. 4th edition, revised and
enlarged,
Designation of Edition and …
Named Revision of an Edition


Transcribe as found (under the general
guideline in RDA 1.7)
“For transcribed elements, use only those
abbreviations found in the sources of
information for the element” (Appendix B4)
Source:
AACR2:
RDA:
Third revised edition
250 $a 3rd rev. ed.
250 $a Third revised edition
Source: 2nd enlarged ed., revised
AACR2: 250 $a 2nd enl. ed., rev.
RDA:
250 $a 2nd enlarged ed., revised
82
Recording Changes of
Edition Statement


RDA 2.20.4.5
For multipart monographs, make a note
if considered important for identification
or access i.e. if the edition number
changes between volumes of a multipart
set
83
Many RDA Elements in MARC 264






Production statement - RDA 2.7
Publication statement - RDA 2.8
Distribution statement - RDA 2.9
Manufacture statement - RDA 2.10
Copyright date - RDA 2.11 -- separate
element from date of publication
Change in the MARC bibliographic
format: 264 field
84
Publication Statement




CORE ELEMENT for published
resources
RDA 2.8
Scope – “a statement identifying the
place or places of publication, publisher
or publishers, and date or dates of
publication of a resource”
MARC field 264, second indicator 1
85
Place of Publication





LC CORE ELEMENT: if more than one, only the first
recorded is required
RDA 2.8.2
Transcribe places of publication in the form in which they
appear on the source
Include both local place name and name of the larger
jurisdiction if present
Option to add a larger jurisdiction if not already on the
resource – 2.8.2.3 – see NLNZ RDA policy doc for our
guidelines. Note the change from our current practice.
LC takes no position on this.
86
More Than One Place of Publication


If more than one, only the first
recorded is required
No “home country” provision


No need to look for a place in the U.S.
See also guidance in NLNZ policy doc.
87
Place of Publication in
More Than One Language


If the place of publication appears in
more than one language or script,
record the form that is in the
language or script of the title proper
Rule 2.8.2.5 – NLNZ policy – if languages
are English and Māori use the version of
the name that appears first, regardless of
the language of the title proper
88
Place of Publication Not Identified


Supply the place of publication or a
probable place of publication whenever
possible for benefit of users and
catalogers, if the place of publication is not
identified
LCPS 2.8.2.6 instructs catalogers to
supply a place of publication if possible,
rather than record “[Place of publication
not identified]” NLNZ will follow LC
89
Examples:
Supplying Place
Known local place:
[Toronto]
Probable local place:
[Munich?]
Known country, state, etc.:
[Canada]
Probable country, state, etc.: [Spain?]
90
Place of Publication: RDA Changes



Only first place of publication is core
[S.l.] is no longer permitted
Do not correct fictitious or incorrect
information; make a note to explain
91
Examples: Place of Publication
On resource: London -- New York – Boston
264 #1
$a London
or
264 #1
$a London ; $a New York ; $a Boston
264 #1 $a Red Oak [Iowa]
(addition OK, but not required)
264 #1 $a [Place of publication not identified]
(Generally, no! LCPS says to supply a place if
you can, even if just the country)this would be
an absolutely last resort.
92
Publisher’s Name




LC CORE ELEMENT - If more than one,
only the first is required NLNZ will
record all named publishers
RDA 2.8.4
Record the publisher's name in the
form in which it appears on the source
of information 2.8.2 says “transcribe”
LCPS: do not omit levels in corporate
hierarchy
93
More Than One Publisher

If you record more than one (which NLNZ
plans to do at this stage – at least for NZNB
resources):

Record the entities in the order indicated by the
sequence, layout, or typography of the names on
the source of information
94
Publisher’s Name in
More Than One Language
o If the name of a publisher appears in more than one
language or script, record the form that is in the
language or script of the title proper – we will use the
one that appears first if the languages involved are
English and Māori – see NLNZ RDA policy doc.
Otherwise we will follow the instruction here.
95
Publisher’s Name not Identified

If no publisher is identified within the
resource or from other sources, record
“[publisher not identified]”

Not “[s.n.]”
96
Examples:
Publisher’s Name
264 #1 $a New York : $b J.J. Wilson
Publishing Company
Not:
264 #1 $b Wilson Pub. Co.
Source: Humanities Association, Literature
Division, Renaissance Literature Section
264 #1 $a Chicago : $b Humanities Association,
Literature Division, Renaissance
Literature Section
264 #1
$b [publisher not identified]
97
Date of Publication




LC CORE ELEMENT
RDA 2.8.6
Record date as it appears on the
source
LCPS 1.8.2 (First Alternative),
transcribe roman numerals for
publication dates; do not convert to
Arabic. Also followed by NLNZ
98
Multipart Monographs, Serials,
and Integrating Resources


RDA 2.8.6.5
Record the date of publication of that issue, part,
or iteration, followed by a hyphen, if the first
issue, part, or iteration of a multipart
monograph, serial, or integrating resource is
available.
1988-
99
Multipart Monographs, Serials,
and Integrating Resources

Record the dates of publication of those issues,
parts, or iterations, separated by a hyphen, if
publication of the resource has ceased or is
complete and the first and last issues, parts, or
iterations are available.
1968-1973

Record the publication date of the last issue,
part, or iteration, preceded by a hyphen, if
publication of the resource has ceased or is
complete and the last issue, part, or iteration is
available, but not the first.
-1977
100
Date of Publication:
RDA Changes (Single Part Resource)


If no publication date on resource,
supply a probable date whenever
possible
Follow LCPS 2.8.6.6 on supplying a
probable date of publication, rather
than giving “[date of publication not
identified]”
101
Examples:
Supplying Dates
Title page verso:
Prefaced signed:
Date of publication:
Transcription:
008/06:
008/07-10:
008/11-14:
Title page verso:
Item received in:
Date of publication:
Transcription:
optionally:
008/06:
008/07-10:
008/11-14:
Copyright ©2009
June 2009
not given
264 #1 $a … $b … $c [2009]
s
2009
####
©2009
2008
not given
264 #1 $a … $b … $c [2009]
264 #4
$c ©2009
t
2009
2009
102
Examples:
Supplying Dates
Title page verso:
Date of publication:
Transcription:
008/06:
008/07-10:
008/11-14:
©1980//1980 printing
not given
264 #1 $a … $b … $c [1980]
s
1980
####
Title page verso:
©1978//Sixth Printing 1980
Prefaced signed:
June 1978
Date of publication:not given
Transcription:
264 #1 $a … $b … $c [1978]
optionally:
264 #3 $a … $b … $c 1980.
588 ## $a Description based on sixth
printing, 1980.
008/06:
s
008/07-10:
1978
008/11-14:
####
103
Examples:
Supplying Dates
Title page verso:
Distributed 2008
Bibliography includes citations to 2007 publications
Date of publication:
not given
Transcription: 264 #1 $a London :$b Gay Mens Press, $c
[2008]
optionally: also give 264 #2 $a Chicago, IL : Distributed
in North America by InBook/LPC Group, $c 2008
008/06:
s
008/07-10:
2008
008/11-14:
####
Title page verso:
Distributed in the USA in 1999
Prefaced signed:
London, January 1993
Date of publication:not given
Transcription: 264 #1 $a … :$b … $c [between 1993 and 1999]
008/06:
q
008/07-10:
1993
008/11-14:
1999
104
Examples:
Supplying Dates
Title page verso:
Date of publication:
Transcription:
008/06:
008/07-10:
008/11-14:
First Printing 1980
not given
264 #1 $a … :$b … $c [1980]
s
1980
####
Title page verso:
15th Impression 1980
Date of publication: not given
Transcription:
264 #1 $a … :$b … $c [not
after 1980]
optionally:
588 ## $a Description based
on 15th impression,
1980.
008/06:
q
008/07-10:
uuuu
008/11-14:
1980
105
Supplying Dates –
5 Categories in RDA 1.9
Actual year known
264 $ … c [2010]
Either one of two consecutive years
264 $ … c [2009 or 2010]
Probable year
264 $ … c [2010?]
Probable range of years (“between ___ and ___?”)
264 $ … c [between 2008 and 2010?]
Earliest and/or latest possible date known (“not
before,” “not after,” or “between ___ and ___”)
264 $ … c [not before January 15, 2010]
106
Importance of Supplying Probable Place
and Date of Publication




LC Policy strongly encourages you to supply a
probable place of publication and a probable
date of publication when this information is not
on the resource
Use distribution or manufacture information to
help supply place and date of publication.
Distribution elements are core elements ONLY if
Publication data can not be identified.
Give a complete distribution statement if
distribution data elements are being given in lieu
of missing publication data elements
107
Examples:
Supplying Publication Data
On source: ABC Publishers, 2009
Distributed by Iverson Company,
Seattle
RDA: 264 #1 $a [Place of publication not
identified] : $b ABC Publishers, $c 2009.
264 #2 $a Seattle : $b distributed by
Iverson Company, $c [2009]
LC-Recommended:
264 #1 $a [Seattle?] : $b
ABC Publishers, $c 2009.
108
Examples:
Supplying Publication Data
On source: On title page:
On title page verso:
Means Pub. Co.,
Omaha, Nebraska
2009 distribution
RDA: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co.,
$c [date of publication not identified]
264 #2 $a [Place of distribution not
identified]: $b [distributor not
identified], $c 2009.
LC-Recommended: 264 #1 $a Omaha, Nebraska : $b Means
Pub. Co, $c [2009?]
109
Examples:
Supplying Publication Data
Sometimes, distribution
information must be provided
On jewel box:
Published in 2010 in
Providence; distributed in
Boston and Ottawa by KL,
Inc.
RDA and LC:
264 #1 $a Providence :$b [publisher not
identified], $c 2010.
264 #2 $a Boston ; $a Ottawa : $b KL,
Inc., $c [2010]
110
Recording Distribution Information
• CORE ELEMENT only when publication
information is not identified for a resource
in a published form
• RDA 2.9
• LCPS: When given in lieu of missing
publication data, give a complete
distribution statement
• Generally do not omit levels in corporate
hierarchy
111
Manufacture Information (RDA 2.10)
o Manufacture elements are core elements for
a resource in a published form only when
neither publication nor distribution
information can be identified
o Give a complete manufacture statement, if
manufacture data elements are being given
in lieu of missing publication and missing
distribution elements
o Generally do not omit levels in corporate
hierarchy
112
Copyright Date





CORE ELEMENT if publication and distribution
dates not identified for a single-part monograph
Copyright dates are not required for multipart
monographs, serials, and integrating resources
RDA 2.11
Precede by copyright symbol (©) or phonogram
symbol ()
MARC field 264, second indicator 4; $c is the only
subfield used; no ending period.
Examples: 264 #4 $c ©2002
264 #4 $c ℗1983
NLNZ: End of Week 2. Now practice following the rules covered
in this session.
113
Series, Mode of Issuance,
and Frequency

Series Statement - RDA 2.12

Mode of Issuance – RDA 2.13
114
Series Statement




CORE ELEMENT : Title proper of
series, numbering within series, title
proper of subseries, and numbering
within subseries are core elements
RDA 2.12
MARC field 490
Authorised access points for series
and the MARC 8XX fields are covered
in the module on recording
relationships.
115
Recording Series Statement


Transcribe the series statement as
they appear on the source of
information
Record each series statement
separately, if the resource belongs
to more than one series and/or …
subseries
116
Title Proper of Series and
… of Subseries

LC CORE ELEMENT

RDA 2.12.2 and 2.12.10

Basic instructions on transcribing titles in
RDA 2.3.1 apply to these titles


Including “take what you see” and the agency’s
policy on capitalization
MARC 490 $a
117
Recording Title Proper of Series



300 ##
490 1#
Record the title proper of the series as it appears on
the source of information, including the numbering
as part of the title proper of the series
RDA/LCPS 2.12.2
Generally give each series statement in a MARC 490
rather than in a note, if some issues or parts of a
serial or a multipart monograph or iterations of an
integrating resource are in different series
$a 350 pages ;$c 14 cm.
$a Music bibliographies ;$v 12
118
ISSN of Series and Subseries




LC CORE ELEMENT
RDA 2.12.8 and 2.12.16
MARC 490 $x now repeatable
If the ISSN of a series appears within the
resource, record it as it appears
119
Numbering Within Series and …
Within Subseries

LC CORE ELEMENT

RDA 2.12.9 and 2.12.17

MARC 490 $v

Guidelines are generally the same as those for
Numbering of serials (see rule 1.8 & NLNZ
policy decisions)
490 $a … $v volume 32
490 $a … $v Band LXXXVIII
120
Mode of Issuance (not yet addressed formally
by NLNZ – but we think we will follow LC)



LC CORE ELEMENT
LCPS 2.13.1.3
MARC Leader: Bibliographic Level



“m”
“s”
“i”
for both “single unit” and “multipart
monograph”
for “serial”
for “integrating resource”
121
Identifier for the Manifestation





LC CORE ELEMENT
RDA 2.15
Scope = “a character string associated with
a manifestation that serves to differentiate
that manifestation from other
manifestations”
If there is more than one identifier for the
manifestation, prefer an internationally
recognized identifier, if applicable.
An ILS bib id is “sort of” an identifier for a
manifestation, but it is not recognized
internationally and only works within one
system
122
What is an identifier?


“A character string associated with
… [FRBR entity] that serves to
differentiate that [entity] from other
[entities]” RDA glossary. The
character string doesn’t have to tell
you anything about the entity itself.
An authorized access point is: “A
standardized access point
representing an entity
Identifier for the Manifestation

Categories of identifiers:
 ISBN, ISSN, and others registered based
on internationally recognized schemes
 those assigned by publishers, distributors,
clearing houses, etc., based on internal
schemes
 “fingerprints” (i.e., identifiers constructed
by combining groups of characters from
specified pages of a printed resource)
 music publisher numbers and plate
numbers
 not URLs (RDA 4.6)
124
Recording Identifier for the
Manifestation




Record in accordance with any prescribed display
format (e.g., ISBN, ISSN, URN)
If an identifier is known to be incorrectly
represented in the resource, record the number
as it appears and indicate that the number is
incorrect, cancelled, or invalid, as appropriate
If the resource bears more than one identifier of
the same type, add a brief qualification
LCPS 2.15.1.7: Record ISBNs in 020 $z if they
represent a different manifestation from the
resource being cataloged and would require a
separate record. If separate records would not be
made, or in cases of doubt, record the ISBNs in
020 $a
125
Examples:
Identifier for the Manifestation
020 ## $a 9789070002343
022 ## $a 0046-225X
020 ## $a 0435916610 (pbk.)
020 ## $a 0387082662 (U.S.)
020 ## $z 0870684302 (invalid)
See also NLNZ policy document for
use of qualifiers – not used if
there is only 1 ISBN
126
Note on Issue, Part Used as
Basis for Identification



LC CORE ELEMENT
Always give in a CONSER Standard Record
RDA 2.20.13

Multipart monographs and serials: if not based
on first issue or part (LCPS 2.20.13.3)
Integrating resources: latest iteration
consulted
Any online resource: date resource viewed

MARC 588 field


127
Other Notes

Not LC CORE ELEMENTS











Note
Note
Note
Note
Note
Note
Note
Note
Note
Note
Note
on
on
on
on
on
on
on
on
on
on
on
Title (core for serials)
Statement of Responsibility
Edition Statement
Numbering of Serials
Production Statement
Publication Statement
Distribution Statement
Manufacture Statement
Copyright Date
Series Statement
Frequency
2.20.2
2.20.3
2.20.4
2.20.5
2.20.6
2.20.7
2.20.8
2.20.9
2.20.10
2.20.11
2.20.12
128
Unit 5: Exercises on Manifestations
and Further Practice

Exercise #1-2
Identifying
Manifestations
129
Another Way to Practice

Bibliographic Record Practice Workform




Aid in learning RDA Structure
Record RDA or LCPS # for every element
Can copy-and-paste into Voyager
 Roman, non-diacritic data only
Electronic version at:

http://www.loc.gov/catworkshop/RDA%20trainin
g%20materials/LC%20RDA%20Training/LC%20
RDA%20course%20table.html
130