Cambridge University Library
RDA Training – Module 1
Introduction to RDA
Identifying Manifestations & Items - Part 1
Adapted for Cambridge use by Janet Davis
Acknowledgements
This module, and the following four, are based on the training
given at the British Library, which is in turn developed from
that used at the Library of Congress.
We would like to express our thanks to both institutions for
making their training materials available to us.
2
Introduction to RDA
The first section of this module looks at:
 How the move to RDA will affect us here in Cambridge
 Foundations and scope of RDA
 Changes in terminology
3
RDA – Impact in Cambridge (1)
RDA - new cataloguing standard that is replacing AACR2
Libraries cataloguing into cambridgedb will use RDA for all
original cataloguing of print books, integrating resources
& serials from 31st March, 2013
BL, LC, and many other major libraries will convert over to
RDA from the same date, so our copy-catalogued records will
then increasingly arrive as RDA records
libraries@cambridge libraries (including all the other Affiliated
Libraries) to receive training over the summer and go live
from 1st October, 2013
Other formats to follow...
4
RDA – Impact in Cambridge (2)
RDA is specifically designed so that RDA records are
compatible with AACR2 records, and can co-exist in the same
database (see RDA 0.4.2.4)
No plans for manual conversion to RDA of:
 our existing AACR2 records
 full-level AACR2 records downloaded in copy-cataloguing
workflows, even after Mar. 2013
Check with your supervisor in case there are local policies on
converting to RDA under certain circumstances
Many global updates will be made using batch processes,
e.g. amendments to the authority forms of names
5
RDA - Basis
RDA is based on a combination of:
FRBR (Functional Requirements for Bibliographic Records) &
FRAD (Functional Requirements for Authority Data)
 These give us the entities, the attributes for each entity,
the relationships, and the user tasks
ICP (IFLA’s Statement of International Cataloguing Principles)
 This provides the basic principles, such as the principle of
representation and the principle of convenience of the
user
6
RDA – Content v. Display/Encoding
RDA is primarily a content standard
It is not a display standard (as AACR2 is). However, it does
contain:
 Appendix D for ISBD presentation
 Appendix E for AACR2 style for access points
It is not an encoding standard. It is ‘schema-neutral’, which
means you can use:
 MARC 21
 Dublin Core
 etc.
7
RDA – MARC
For the present, still using MARC21 to encode our records
Some new fields / subfields required, e.g.
 264 (replacing 260)
 336-338 (completely new)
RDA MARC records can recognised by:
 040 ... $e rda
Additional clues:
 Leader “Cataloging form” = i
 33X ... $2 rda...
8
9
What am I cataloguing?
Starting point is the book in hand
Using MARC 21 we create a composite record:
 Identify and describe the manifestation
 Identify and describe the content (work and expression)
 Identify and describe a specific copy (item)
 Relate to other resources, persons, families, corporate
bodies, etc.
 Assign subject indexing and classification as usual
10
MARC bibliographic record & FRBR
1XX = person, family, corporate body, work, expression
130/240 = work, expression
245-264, 490 = manifestation
300 = expression, manifestation
other 3XX = work, expression, manifestation
5XX = work, expression, manifestation, item
700-730 = person, family, corporate body, work, expression
760-787 = related work, expression, manifestation
8XX = work, expression, manifestation
11
RDA - Terminology (1)
AACR2
RDA
heading
authorised access point
author, composer, artist,
etc.
creator
main entry
preferred title and, if appropriate, the
authorised 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”
12
RDA - Terminology (2)
AACR2
RDA
see reference
variant access point
see also reference
authorised 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
13
Identifying Manifestations & Items - Part 1
The second section of this module looks at:
 Sources of information
 Transcription
 Language & script






Title
Statement of responsibility
Edition statement
Copyright date
Publication, Distribution & Manufacture statements
Production statement
14
Sources of information
Preferred source: source of title proper
More sources for information
 Whole resource, with priority order
 Then any other source
Usually square brackets if from outside the resource
Three categories (RDA 2.2.2.2 – 2.2.2.4)
 Pages, leaves, etc., or images of pages, leaves, etc.
 Moving images
 All other resources
15
Preferred source - Resources with pages,
leaves, etc.
Monographs (single- and multi-part)
Serials
Integrating resources (e.g. loose-leafs, websites)
RDA 2.2.2.2 priority order for preferred source:







Title page, title sheet, etc.
Cover
Caption
Masthead
Colophon
If none of these contain a title, use any source that does
If no title, use any source with formal presentation
16
Preferred source - Resources issued in
>1 part
RDA 2.1.2.3 – e.g. serials, multiparts, kits
 If sequentially numbered, use the lowest-numbered
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
RDA 2.1.2.4 – integrating resources
 Use a source of information identifying the current
iteration of the resource as a whole, if available
17
Other sources of information
RDA 2.2.4 priority order for other sources




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)
18
Transcribed & recorded elements
Distinction between transcribed elements and recorded
elements.
For recorded elements, the found information is often
adjusted (for example, the hyphens in an ISBN are omitted)
ICP Principle of Representation ↔ RDA 0.4.3.4
For transcribed elements, generally do not alter what is on the
resource
Encourages re-use of found data
Take what you see and Accept what you get
19
Transcription
Instructions on transcription are found in RDA 1.7, and the
accompanying LC-PCC PS
For the alternatives given in the general guidelines (RDA
1.7.1), Cambridge:
 Does not apply Alternative 1 (use alternative style
manual)
 Does permit Alternative 2 to be applied (accept, without
modification, data as created by another agency or as
automatically scanned / downloaded from a digital
source)
20
Capitalisation
RDA 1.7.2
Apply the instructions on capitalisation found in Appendix A
Generally yes, plus LC-PCC PSs for 1.7.1 and Appendix
A.31
But you may accept “found” capitalisation:
 If data are scanned or downloaded from a digital source
 When using description created by another agency
21
Capitalisation examples
Accepting found capitalisation:
245 10 $a Cairo : $b THE CITY VICTORIOUS /
$c Max Rodenbeck.
250 ## $a FIRST VINTAGE DEPARTURES EDITION.
Changing found capitalisation:
245 10 $a Cairo : $b the city victorious /
$c Max Rodenbeck.
250 ## $a First Vintage Departures edition.
22
Abbreviations
RDA 1.7.8 & Appendix B.4
Do not substitute abbreviations for words in transcribed
elements
Do transcribe found abbreviations as they appear on the
source
23
23
Inaccuracies
RDA 1.7.9
Generally, transcribe an inaccuracy or a misspelled word as
it appears on the resource
Make a note correcting the inaccuracy if considered
important for identification or access
For inaccuracies that appear in a title, record corrected
form as a variant title
24
24
Language & script
RDA 1.4 provides an extensive list of transcribed elements
Transcribe these in the language and script in which they
appear on the sources from which they are taken
For non-Roman scripts, follow the alternative, and record
them in a transliterated form
When adding data within a transcribed element, record it in
the language and script of the element to which it is added
When recording other elements (e.g., extent, notes), record
them in English
25
Title & Statement of responsibility
RDA 2.3 – 2.4
Title proper
Parallel title proper
Other title information
Earlier title proper
Later title proper
Statement of responsibility relating to title proper
26
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)”
Sources:
 Preferred source of information: RDA 2.2.2-2.2.3
 If no title within the resource: RDA 2.2.4
MARC 245 $a $n $p
27
Title proper - Transcription
RDA 2.3.1.4
Transcribe a title as it appears on the source of information,
following general transcription guidelines in RDA 1.7.
Don’t correct errors for monographs: no more “[sic]” or
“[i.e., ____]” – instead give note to explain
Do correct errors for serials and integrating resources
Changes in title proper: RDA 2.3.2.12-2.3.2.13 (same as
AACR2)
28
Examples of title proper errors
RDA record for a monograph:
245 10 $a Teusday’s tasks
246 1# $i Corrected title: $a Tuesday’s
tasks
AACR2 record for a monograph:
245 10 $a Teusday’s [i.e. Tuesday’s] tasks
246 1# $i Corrected title: $a Tuesday’s
tasks
RDA record for a serial:
245 10 $a Zoology studies
246 1# $i Misspelled title on number 1:
$a Zooology studies
29
Parallel title proper
CAM CORE ELEMENT
RDA 2.3.3
Scope: “The title proper in another language and/or script”
Sources: Expanded to any source - not just same source as
title proper
245 10 $a Italian short stories = $b Racconti
italiani / $c edited by Raleigh Trevelyan.
246 31 $a Racconti italiani
30
Other title information
CAM CORE ELEMENT
RDA 2.3.4
Scope: “Information that appears in conjunction with, and is
subordinate to, the title proper of a resource”
Source: From same source as title proper
245 10 $a Kerouac : $b the definitive biography
31
Variant titles
RDA 2.3.6
Scope: “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”
Includes:





Alternative title
Spine title
Running title
Corrected title
Part of title
32
Examples of variant titles
Alternative title
245 10 $a Listening to popular music, or,
How I learned to stop worrying and love Led
Zeppelin
246 30 $a Listening to popular music
246 30 $a How I learned to stop worrying and
love Led Zeppelin
Cover title – other title information
245 10 $a Bridget Fidget
246 14 $a Bridget Fidget : $b the girl in a
whirl who can’t stay still
33
Recording variant titles
Follow LC-PCC PS 2.3.6.3
 Record a variant title in MARC field 246
 Record a variant title for a component of an aggregate
work in a form other than would be recorded as the
authorised access point for that component work. This
form of variant title is recorded in MARC field 740
Omit any initial article from the variant title unless the
intention is to file on the article (MARC 21, not RDA)
34
Earlier title proper
CAM CORE ELEMENT
RDA 2.3.7
Scope: “A title proper appearing on an earlier iteration of an
integrating resource that differs from that on the current
iteration”
Source: source specified for title proper on earlier iteration
MARC 247
245 00 $a Older client service.
247 10 $a Tottel’s older client law service,
$f 2006-2010
35
Later title proper
CAM CORE ELEMENT
RDA 2.3.8
Scope: “A title proper appearing on a later issue or part of a multipart
monograph or serial that differs from that on the first or earliest issue or
part”
Source: source specified for the title proper on later issue / part
MARC 246
245 00 $a IEEE/OSA journal of optical communications
and networking.
246 1# $i Minor title change: $a Journal of optical
communications and networking, $f Vol. 1, no. 5
(October 2009)36
36
SoR relating to title proper – Scope
CORE ELEMENT (first if more than one)
RDA 2.4.2 (& 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
37
SoR 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
Square brackets only required if information taken from
outside the resource
245 10 $a UNIMARC manual authorities format
/ $c [Permanent UNIMARC Committee]
38
SoR relating to title proper –
Transcription (1)
Transcribe a statement of responsibility in the form in which it
appears on the source of information (follow general
guideline in 1.7)
Cambridge policy: “Generally do not abridge a statement of
responsibility” (LC-PCC PS 2.4.1.4)
Source: Dr. Logan Carroll, Harvard Medical School
RDA/LC-PCC PS:
245 … / $c Dr. Logan Carroll, Harvard
Medical School.
RDA allows:
245 … / $c Dr. Logan Carroll.
39
SoR relating to title proper –
Transcription (2)
RDA does not contain the “Rule of Three”
Cambridge policy: “Generally do not omit names in a statement
of responsibility” (LC-PCC PS 2.4.1.5)
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/LC-PCC PS:
245 $a … / $c by Susan Brown, Melanie Carlson,
Stephen Lindell, Kevin Ott, and Janet Wilson.
AACR2:
245 $a … / $c by Susan Brown … [et al.].
40
Multiple SoRs
Record in the order indicated by the sequence, layout, or
typography of the source of information (RDA 2.4.1.6)
Only first recorded is required but Cambridge policy is to
record all unless it would be unduly onerous
If not giving all statements of responsibility, give preference
to those identifying creators of intellectual or artistic
content (RDA 2.4.2.3)
On source: “introduction by ______”
“written by _____”
If only transcribing one in 245 $c, give “written by _____”
41
Designation of edition & Designation of
named revision of an edition - Scope
CORE ELEMENT
RDA 2.5.2 and 2.5.6
Scope: “A word, character, or group of words and/or
characters, identifying ...
 the edition to which a resource belongs”
 a particular revision of a named edition”
MARC 250 $a
42
Designation of edition & Designation of
named revision of an edition - Sources
Each element has a list of possible sources in descending
order of preference:
a) same source as the
 title proper
 designation of edition
b) another source within the resource itself
c) one of the other sources of information specified under
2.2.4
43
Designation of edition & Designation of
named revision of an edition - Transcription
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:
AACR2:
RDA:
2nd enlarged ed., revised
250 $a 2nd enl. ed., rev.
250 $a 2nd enlarged ed., revised
44
Recording changes in edition statement
RDA 2.20.4.5
For multipart monographs, make a note if considered
important for identification or access
For serials, make a note on changes in edition statements
that occur after the first/earliest issue or part of a serial if they
are considered to be important for identification or access
For integrating resources, change the edition statement to
reflect the current iteration if the change does not require a
new description. However, make a note if the earlier edition
statement is considered to be important
45
Examples of changes in edition statement
Multi-part set:
250 ## $a Second edition.
500 ## $a Volume 3: First edition.
Multi-part set (local variation):
250 ## $a Second edition.
599 ## $a Volume 3: First edition. $5 UkCU
Serial:
250 ## $a International ed. in English.
500 ## $a Edition statement varies:
International ed., 1998-
46
SoR relating to the edition
RDA 2.5.4
Scope: “A statement of responsibility relating to the edition is
a statement relating to the identification of any persons,
families, or corporate bodies responsible for the edition
being described but not to all editions”
Source: “same source as the designation of edition”
The SoR is “dropped down” to the 250 $b if necessary to
indicate responsibility for the edition being described
Responsibility for the work remains in the 245 $c
47
RDA elements in MARC 264
Production statement - RDA 2.7 (264 #0)
Publication statement - RDA 2.8 (264 #1)
Distribution statement - RDA 2.9 (264 #2)
Manufacture statement - RDA 2.10 (264 #3)
Copyright date - RDA 2.11 (264 #4)
 “A date associated with a claim of protection under
copyright or a similar regime”
 NB separate element from date of publication
[260 appears on legacy data]
48
264 field – First indicators
# - Not applicable / No information provided / Earliest
2 - Intervening
3 - Current / Latest
264 #1 $3 volumes 1-14: $a Amsterdam : $b
North Holland Publishing Company, $c 1970264 31 $3 volume 15- : $a Amsterdam : $b
Elsevier
49
49
Copyright date
CAM CORE ELEMENT*
RDA: Core element if publication and distribution dates not
identified
Cambridge policy: *core for single-part monographs if
present on resource
RDA 2.11
Precede by copyright symbol (©) or phonogram symbol ()
MARC field 264, second indicator 4
264 #4 $c ©2002
NB No full stop at end of field
264 #4 $c ℗1983
50
Publication statement
CORE ELEMENTS 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
Generally ends with a mark of punctuation (full stop, hyphen,
or closing bracket). Do not use a full stop at the end of a 264
field which ends with subfield $b
51
Place of publication – Scope & Sources
CORE ELEMENT: if more than one, only the first is required
RDA 2.8.2
Scope: “A place associated with the publication, release, or
issuing of a resource”
Sources: In descending order of preference:
a) the same source as the publisher's name
b) another source within the resource itself
c) one of the other sources of information specified under
2.2.4
52
Place of publication - Transcription
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, enclosed in square brackets, if
not already on the resource if useful for identification or to
distinguish between places with the same name
Do not correct fictitious or incorrect information; instead make
a note to explain (RDA 2.20.7.3)
264 #1 $a Minneapolis
500 $a Actually published in St. Paul.
53
>1 place of publication
“If more than one place of publication is named on the source
of information, record the place names in the order indicated
by the sequence, layout, or typography of the names on the
source of information”
[Remember, only the first is core]
No longer any requirement to include a place in the UK
Source:
Dublin New York Oxford
RDA core:
264 #1 $a Dublin
RDA allows: 264 #1 $a Dublin ; $a New York ; $a
Oxford
or even:
264 #1 $a Dublin [Ireland] ; $a New
York [New York] ; $a Oxford [England]
54
Place of publication in >1 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
If this criterion does not apply, record the place name in the
language or script that appears first
55
Place of publication not identified
RDA: “If neither a known nor a probable local place or
country, state, province, etc., of publication can be
determined, record Place of publication not identified”
Cambridge policy: For the benefit of users and cataloguers,
follow LC-PCC PS 2.8.2.6 and supply a place of publication if
at all possible, rather than recording “[Place of publication not
identified]”
NB “[S.l.]” is no longer permitted
264 #1 $a [Place of publication not
identified]
Generally no! Supply a place if you can, even if just country
56
Supplying place of publication
RDA 2.8.2.6
Known local place:
[Toronto]
Probable local place:
[Munich?]
[Göteborg?, Sweden]
[Sofia, Bulgaria?]
Known country, state, etc.:
[Canada]
Probable country, state, etc.:
[Spain?]
57
Publisher’s name
CORE ELEMENT: if more than one, only the first is required
RDA 2.8.4
Scope: “The name of a person, family, or corporate body
responsible for publishing, releasing, or issuing a resource”
Sources: In descending 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
Transcription: Record the publisher's name in the form in which it
appears on the source of information (2.8.1.4)
Follow LC-PCC PS 2.8.1.4: don’t omit levels in corporate hierarchy
58
>1 publisher & >1 language
If more than one person, family, or corporate body is named
as a publisher of the resource, record the publishers' names
in the order indicated by the sequence, layout, or typography
of the names on the source of information
[Remember, only the first is core]
If the name of a publisher appears on the source of
information in more than one language or script, record the
form that is in the language or script of the title proper
If this criterion does not apply, record the name in the
language or script that appears first
59
Publisher’s name not identified
If no publisher identified within the resource or from other
sources, give “[publisher not identified]”
NB “[s.n.]” is no longer permitted
You may supply a publisher’s name
But never supply an only “probable” publisher’s name
264 #1 $a Oxford : $b [publisher not
identified]
NOT: 264 #1 $a Oxford : $b [Varsity Press?]
60
Publisher’s name - Examples
Source:
RDA:
NOT:
Source:
RDA:
New York -- J.J. Wilson Publishing Company
264 #1 $a New York : $b J.J. Wilson
Publishing Company
264 #1 $b Wilson Pub. Co.
Humanities Association, Literature Division,
Renaissance Literature Section
264 #1 $a Chicago : $b Humanities
Association, Literature Division,
Renaissance Literature Section
Source:
Toronto -- Pilkington Pub. Co.
Houston -- Davidson Publishers
RDA core: 264 #1 $a Toronto : $b Pilkington Pub.
Co.
61
Date of publication - Scope & Sources
CORE ELEMENT
RDA 2.8.6
Scope: “A date associated with the publication, release, or
issuing of a resource”
Sources: In descending 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
62
Date of publication – Transcription
Record date as it appears on the source
Follow LC-PCC PS 1.8.2 (First Alternative): Transcribe
Roman numerals for publication dates; do not convert to
Arabic
Follow LC-PCC PS 2.8.6.3: Add dates in the Gregorian or
Julian calendar if not already on the source
Follow LC-PCC PS 2.8.6.4: Record supplied date in
numerals if it appears on the source in the form of
chronogram; indicate that the information was taken from a
source outside the resource itself
63
Multipart monographs, serials &
integrating resources (1)
RDA 2.8.6.5
If the first issue, part, or iteration of a multipart monograph,
serial, or integrating resource is available, record the date of
publication of that issue, part, or iteration, followed by a
hyphen
Information taken from the resource itself is presented as
follows:
264 #1 $a … $b … $c 1988-
64
Multipart monographs, serials &
integrating resources (2)
If publication of the resource has ceased or is complete and
the dates of the first and last issues, parts, or iterations are
available, record them, separated by a hyphen
264 #1 $a … $b … $c 1968-1973.
If publication of the resource has ceased or is complete and
the last issue, part, or iteration is available, but not the first,
record the publication date of the last issue, part, or iteration,
preceded by a hyphen
264 #1 $a … $b … $c -1997.
65
Multipart monographs, serials &
integrating resources (3)
For an integrating resource, supply the date of the last
update if it is considered to be important
264 #1 $a … $b … $c 1995–1998 [updated 1999]
If the date of publication is the same for all issues, parts, or
iterations, record only that date as the single date
264 #1 $a … $b … $c 1997.
If the publication date of the first and/or last issue, part, or
iteration is available but is not present on the resource,
then supply it in square brackets
264 #1 $a … $b … $c [1988-1991]
66
Multipart monographs, serials &
integrating resources (4)
If the first and/or last issue, part, or iteration is not available,
supply an approximate date or dates in square brackets,
applying the instructions given under 2.8.6.6
264 #1 $a … $b … [1988?-1991]
If the date or dates cannot be approximated, do not record a
date of publication
67
Single-part resources
RDA: If the date of publication is not identified in the singlepart resource, supply the date or approximate date of
publication. Apply the instructions on supplied dates given
under 1.9.2. If an approximate date of publication for a
single-part resource cannot reasonably be determined,
record date of publication not identified.
Cambridge policy: Follow LC-PCC PS 2.8.6.6 on supplying
a probable date of publication if at all possible, rather than
giving “[date of publication not identified]”
68
Supplying dates
RDA 1.9.2
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]
69
Single-part resources – Supplying publication
date from Copyright date
Copyright date only: Supply a date of publication that
corresponds to the copyright date, in square brackets, if it
seems reasonable to assume that date is a likely publication
date
Title page verso:
Prefaced signed:
Date of publication:
Copyright ©2009
June 2009
not given
Transcription:
264 #1 $a … $b … $c [2009]
264 #4 $c ©2009
t
2009
2009
008/06:
008/07-10:
008/11-14:
70
Single-part resources – Supplying publication
date from Copyright & Manufacture dates (1)
Copyright date & Date of manufacture: Supply a date of
publication that corresponds to the copyright date, in square
brackets, if it seems reasonable to assume that date is a
likely publication date
If the date of manufacture differs from the copyright date, it
may optionally also be recorded:
 as part of a manufacture statement
 or as part of a “Note on issue, part, or iteration used as
the basis for identification of a resource” (RDA 2.20.13)
71
Single-part resources – Supplying publication
date from Copyright & Manufacture dates (2)
Title page verso:
©1978 // Sixth Printing 1980
Preface signed:
June 1978
Date of publication: not given
Transcription:
008/06:
008/07-10:
008/11-14:
264 #1 $a … $b … $c [1978]
264 #3 $a … $b … $c 1980.
264 #4 $c ©1978
588 $a Description based on
sixth printing, 1980.
t
1978
1978
72
Single-part resources – Supplying publication
date from Distribution date (1)
Date of distribution only: Supply a date of publication that
corresponds to the distribution date, in square brackets, if it
seems reasonable to assume that date is a likely publication
date
If it does not seem reasonable to assume that the distribution
date is a likely publication date, supply a date of publication,
in square brackets, based on the information provided
In either case, a date of distribution may optionally be
recorded as part of a distribution statement if determined
useful by the cataloguer
73
Single-part resources – Supplying publication
date from Distribution date (2)
Title page verso:
Distributed 2008
Bibliography includes citations to 2007 publications
Date of publication: not given
Transcription:
008/06:
008/07-10:
008/11-14:
264 #1 London :$b Gay Mens
Press, $c [2008]
264 #2 Chicago, IL : $b
Distributed in North America
by InBook/LPC Group, $c 2008.
s
2008
####
74
Single-part resources – Supplying publication
date from Distribution date (3)
Title page verso:
Distributed in the USA in 1999
Preface signed:
London, January 1993
Date of publication: not given
Transcription:
008/06:
008/07-10:
008/11-14:
264 #1 $a … $b … $c [between
1993 and 1999]
q
1993
1999
75
Single-part resources – Supplying publication
date from Manufacture date (1)
Date of manufacture only: Supply a date of publication that
corresponds to the manufacture date, in square brackets, if it
seems reasonable to assume that date is a likely publication
date. For books, this means that the item is assumed to be
the first printing of the edition
If the date of manufacture given implies that it is not likely the
same as the date of publication, supply a date of publication,
in square brackets, using the information provided
In either case, a date of manufacture may optionally be
recorded as part of a manufacture statement if determined
useful by the cataloguer
76
Single-part resources – Supplying publication
date from Manufacture date (2)
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:
Date of publication:
Transcription:
15th Impression 1980
not given
264 #1 $a … $b … $c [not after
1980]
588 $a Description based on 15th
impression, 1980.
q
uuuu
1980
008/06:
008/07-10:
008/11-14:
77
Supplying publication data
On source
Title page:
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.
Cambridge (LC, BL)
264 #1 $a Omaha, Nebraska : $b Means Pub.
Co., $c [2009?]
78
Distribution statement
CORE ELEMENTS only when publication information is not
identified for a resource in a published form
RDA 2.9
Cambridge policy:
 Follow LC-PCC PS 2.9: When given in lieu of missing
publication data, give a complete distribution statement
 Follow LC-PCC PS 2.9.1.4: Generally do not omit levels
in corporate hierarchy
MARC field 264, second indicator 2
Ending punctuation is same as that for publication statement
79
Distribution statement - Example
On jewel case:
Published in 2010, and distributed by
KL, Inc. in Boston and Ottawa
Transcription:
264 #1 $a [Place of publication not
identified] : $b [publisher not
identified], $c 2010.
264 #2 $a Boston ; $a Ottawa : $b
Distributed by KL, Inc., $c [2010]
80
Manufacture statement
CORE ELEMENTS only when neither publication nor
distribution information available for a published resource
RDA 2.10
Cambridge policy:
 Follow LC-PCC PS 2.10: When given in lieu of missing
publication data, give a complete manufacture
statement
 Follow LC-PCC PS 2.10.1.4: Generally do not omit
levels in corporate hierarchy
MARC field 264, second indicator 3
Ending punctuation is same as that for publication statement
81
Production statement
Date of production is a CORE ELEMENT for resources issued in
an unpublished form. Other sub-elements of production
statements are optional
RDA 2.7
MARC field 264, second indicator 0
Scope: “A statement identifying the place or places of production,
producer or producers, and date or dates of production of a
resource in an unpublished form”
E-resources where publication status unclear:
Assume: online = published; handheld = unpublished
Resource:
An unpublished thesis, dated 2010
Transcription: 264 #0 $c 2010.
82
More information
The slides for this presentation, along with lots of other RDA
resources and documentation, are available from:
http://www.lib.cam.ac.uk/libraries/login/RDA/docs.html
83