Upload
damon-simpson
View
222
Download
1
Tags:
Embed Size (px)
Citation preview
Descriptive CatalogingUsing RDA
RDA Introduction and Background;Identifying Manifestations
Cooperative and Instructional Programs DivisionLibrary of Congress
2014
Module 4
2
Acknowledgements
This course is the result of collaboration between Tim Carlton, Cooperative and Instructional
Programs Division, Library of Congress Ingrid Hsieh-Yee, Ph. D., Dept. of Library &
Information Science, Catholic University of America
It has been adapted from training developed by Barbara Tillett and Judith Kuhagen, Library of Congress Policy and Standards Division, and other Library of Congress staff
COIN gratefully acknowledges PSD’s permission to adapt the material for the present purpose
3
About This Material
This training material has been created for a primary audience of Library of Congress staff.
Other audiences are welcome to adapt and utilize it as they see fit. However, it should be understood that it reflects LC policies, and should not be interpreted to either prohibit or require specific practices for other libraries or organizations.
4
Learning Objectives
o RDA Introduction and Backgroundo Overview of RDAo Introduction to Identifying
Manifestationso Identifying Manifestations – The Detailso For Further Assistance
5
Unit 1:RDA Introduction and Background What does RDA Stand For? Why RDA? How Did RDA Come to Be? RDA as a Tool FRBR as a Foundation of RDA International Cataloguing Principles
Many students are not very interested in this ‘background’ -- and some of it is already familiar to you. So we will not cover most of it in class.It is provided here for you to peruse on your own.
6
What does RDA Stand For?
Resource Description & Access
First … a little history of its origins and development
7
“Why RDA?”
Evolving cataloging environment RDA an improvement over AACR2
‘Why don’t we just revise AACR2?’
8
Why RDA? –The Cataloging Environment
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
9
Web frontend
Services
VIAF
Databases, Repositories
LCSH
Why RDA? –The Cataloging Environment
10
Why RDA? –The Cataloging Environment
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.
11
Why RDA? –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
12
AACR3
AACR3
How Did RDA Come to be?
13
How Did RDA Come to be? –Collaborations with Other Communities
International Federation of Library Associations and Institutions (IFLA)
Principles, Conceptual models, ISBD/ISSN ONIX (Publishers)
Types of content, media,and carriers
Dublin Core, IEEE/LOM, Semantic Web, W3C
RDA/MARC Working Group (MARBI)
14
How Did RDA Come to be? –Collaborations with Other Communities
Law Library community Treaties
Hebraica and Religion Teams at LC Bible proposals
MSS/Archives staff at LC (MSS, NUCMC, American Folklife Center, Rare Books) DACS
Music Division, MBRS, Music Library Association AMIM2 and Ch.6 proposals for music
Prints & Photographs Division CCO
Geography and Map Division
15
16
RDA as a Tool –a Tool for the Digital World
Optimized for use as an online product RDA Toolkit
Description and access of all resources All types of content and media
Result in records that are usable in the digital environment (Internet, Web OPACs, etc.)
Result in records that are readily adaptable to newly-emerging database structures
17
RDA as a Tool –Specific Goals
Easy to use and interpret Online, networked environment Bibliographic control for all types of
media Useful beyond library community Compatible with other standards Logical structure based on
internationally agreed-upon principles Separate content and carrier data Numerous appropriate examples
18
FRBR as a Foundation for RDA
Functional Requirements for Bibliographic Records (FRBR; 1998)
Functional Requirements for Authority Data (FRAD; 2009)
Entities, attributes, relationships User tasks
19
Work
Expression
Manifestation
Item
is realized through
is embodied in
is exemplified by
FRBR as a Foundation for RDA --FRBR/FRAD Relationships (Refresher)
Inherent Group 1 Relationships
20
Work
Expression
Manifestation
Item
is owned by
is produced by
is realized by
is created by
Person
Corporate Body
Family
FRBR as a Foundation for RDA –FRBR/FRAD Relationships (Refresher)
RelationshipsBetween Groups 1 and 2
21
FRBR as a Foundation for RDA --Relationship of FRBR to RDA
FRBR conceptual model offers a structure to address user tasks attributes translate into RDA data elements offers a way to conceive relationships
RDA standard Builds on FRBR model (and ICP) to provide
a structure for detailed instructions
FRBR is not a cataloging code -- but it shows the benefit of a well-structured code based on the FRBR conceptual model
22
International Cataloguing Principles (ICP)
Convenience of the user Representation Common usage Accuracy Sufficiency and necessity Significance Economy Consistency and standardization Integration Defensible, not arbitrary
Statement of International Cataloguing Principles (ICP; 2009)
23
Unit 2: Overview of RDA
What RDA is The Structure of RDA Supplemental Resources
24
What RDA Is
Content standard Not …
A display standard An encoding standard
‘Schema-neutral’MARC 21Dublin Coreetc.
25
What RDA Is
More international than AACR2 Focus on local user needs
Agencies can make decisions regarding Language of additions to access points Language of supplied data Script and transliteration Calendar Numeric system
26
What RDA Is
Applies to wider scope of resources Reflects what’s being acquired in
libraries more non-printed text resources more non-text resources more unpublished resources
Defers to specialist manuals of some collaborative communities
27
What RDA Is
Includes authority data Based on attributes and relationships in
FRAD Authority elements, for now, are
documented in authority records
28
What RDA Is
Uses controlled vocabularies Only a few lists are ‘closed’
Content type Media type Carrier type Mode of issuance
Cataloger can supply term if not in list
29
The Structure of RDA
Table of Contents General introduction Entities (and their attributes)
Group 1 (Chapters 1-7) Group 2 (Chapters 8-16)
Relationships: chapters 17-22, 24-32 Appendices Glossary Index
30
The Structure of RDA
Principles applicable to all resources Not separate chapters for formats (e.g.,
books, maps, printed music, etc.) FRBR structure
attributes relationships
For access points individual elements addressed separately instructions to assemble elements are at
the end of chapters 6, 9-11
31
The Structure of RDA –Coreness
Based on attributes mandatory for a national level record (FRBR/FRAD)
Defined at the element level Always “Core if” – situation described
‘element must be recorded if known’ LC has identified additional elements
as “LC Core” Indicated in LC-PCC Policy Statements
(LC-PCC PS)
CORE ELEMENT
32
The Structure of RDA –LC-PCC Policy Statements
Library of Congress and Program for Cooperative Cataloging
To facilitate standard interpretation and application
If you are an LC Cataloger, always follow LC-PCC Policy Statements
If there is no LC-PCC PS, apply cataloger judgment
Follow the green link
33
The Structure of RDA –Alternatives, Options, and Exceptions
Clearly labeled in the Toolkit by green legends and vertical bars
Alternatives to an instruction Options Additional data Omission of data “agency preparing …” instructions
34
The Structure of RDA –Examples (0.10)
Illustrate only the specific instruction at which they appear
If data in another element is directly relevant, the related element is explained in a note. For example, at an instruction on recording
other title information:
Normally do not show preceding or enclosing ISBD punctuation
Illustrate elements as they would be recorded by an agency whose preferred language is English
35
Supplemental Resources –Web Sites
LC ABA RDA web page www.loc.gov/aba/rda/
“Descriptive Cataloging Using RDA” web page http://staff.loc.gov/sites/lstraining/take-a-cla
ss/course-materials/dcat-use-rda/
Program for Cooperative Cataloging (PCC) web page www.loc.gov/aba/pcc/
36
Unit 3: Introduction toIdentifying Manifestations
Coding Records as “RDA” Records Sources Transcription Where in RDA are the Instructions?
But first … Watch this, then we'll talk about why
37
Coding Records as “RDA” Records
Leader/18 contains the value “i” (ISBD punctuation included)
040 $e contains the code “rda”
38
Sources –General Principles
Important for standardization Preferred sources for each element
First: source with the title proper Next: the whole resource, in priority order
Record data in brackets if taken from outside the resource Exception: not needed for resources that
typically don’t have bibliographic data on the resource (photograph, sculpture, etc.)
We will concentrate on resources with pages, leaves, etc. (or images of these, i.e., PDFs)
39
Sources – Preferred1. Resources with Pages, Leaves, etc.
2.2.2.2 Priority order:
Title page, title sheet, etc. Cover Caption Masthead Colophon (if none of these, the source containing title)
For resources issued in more than one part (e.g., serials, multipart items, integrating resources), see 2.1.2.3
40
Sources – Preferred2. Moving-Image Resources
2.2.2.3 Film, DVD, etc. Priority order
41
Sources – Preferred3. Other Resources
2.2.2.4 Resources not covered by 2.2.2.2. or
2.2.2.3
42
Sources –Other Sources of Information
2.2.4 Sources external to the resource Priority order
Accompanying materials Other published descriptions of the
resource Container not issued as part of the
resource Any other source (e.g., a reference source
which indicates how the resource is commonly known)
43
Transcription –Transcribed 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 (e.g., the hyphens in an ISBN are not recorded)
44
Transcription –What Does it Mean?
‘Take What You See and Accept What You Get’
ICP Principle of Representation Generally, record what is on the
resource Accurate representation Encourage re-use of found data
45
Transcription –Language and Script
1.4“in the language and script in which they appear”
Non-transcribed elementsAdding data within an element: language and
script of element to which it is addedSupplying an element: generally, EnglishRecording other elements (e.g., notes): English
For non-Latin scripts, LC policy is to record a transliteration instead, or to give both (using MARC 880 fields)
46
Transcription –LC Policy
Alternatives at 1.7.1 allow for in-house guidelines (in lieu of RDA instructions) for capitalization, punctuation, numerals, symbols, abbreviations, etc.
LC-PCC PS 1.7.1 General guidelines on transcription LC policy generally adheres to “Take What
You See and Accept What You Get”
Following slides emphasize LC policy
47
Transcription –Capitalization (LC Policy)
LC-PCC PS 1.7.1 First Alternative “For capitalization of transcribed elements,
catalogers are encouraged (but not required) to follow Appendix A; it is permitted to "take what you see" on the resource.”
Your choice! – but don’t do a ‘mix’
48
Transcription –Capitalization (LC Policy)
Acceptable:
245 10 $a Cairo : $b THE CITY VICTORIOUS / $c Max Rodenbeck.250 ## $a FIRST VINTAGE DEPARTURES EDITION.
Encouraged:
245 10 $a Cairo : $b the city victorious / $c Max Rodenbeck.250 ## $a First Vintage Departures edition.
49
Transcription –Punctuation, Numerals, Symbols,
Abbreviations (LC Policy)
LC-PCC PS 1.7.1 First Alternative “follow the guidelines in 1.7.3 – 1.7.9 and
in the appendices” Generally, transcribe what is on the
resource
Where in RDA are the Instructions?
Quiz: Which WEMI entity are you generally cataloging?
50
51
Where in RDA are the Instructions?
Chapter 2: Identifying Manifestations and Items Information used by producers of
resources to identify their products — title, statement of responsibility, edition statement, publication data, etc.
Information users rely on to: determine if the resource is the one sought distinguish between similar resources
Find, Identify
Primary focus on: LC core elements
52
Unit 4: Identifying Manifestations – the Details
Title and Statement of Responsibility Edition Numbering of Serials Production, Publication, Distribution,
Manufacture, Copyright Series, Mode of Issuance, Frequency Notes
‘Ground Rules’
53
Title and Statement of Responsibility
Title Elements Statement of Responsibility Elements
54
Title(2.3)
Title proper Parallel title proper Other title information Variant titles Earlier Title Proper Later Title Proper
55
Title Proper(2.3.2)
CORE ELEMENT Scope = “the chief name of a
resource (i.e., the title normally used when citing the resource)”
Sources Preferred sources within the resource
Title page; then priority order (2.2.2) If none on the resource, priority order of
other sources Title of Manifestation – not Work MARC 245 $a $n $p
56
Title Proper –Choosing the Title Proper
Occasionally, a resource includes several strings of title-like data Which string is the title proper? Which string(s) might be recorded as
other elements? 2.3.2.5 indicates that you should
consider sequence, layout, and typography in making this decision Also, common sense
The next few slides show examples of such situations …
Title Proper –Choosing the Title Proper
57
Title Proper –Choosing the Title Proper
But sometimes, even the typography can be misleading Based on typography, one
might think that this title proper is “Washington, D.C.”
But that ignores common sense and grammar – which require you to record as title proper the entire string, “MapEasy’s guidemap to Washington, D.C.”
58
Title Proper –Choosing the Title Proper
Here, typography might suggest the title proper is “52”, or “52 day walks …”
But “Tim Anderson’s” is an ‘integral’ part of the title, and thus must be included in the title proper Tim Anderson’s 52 day-walks in and around Cape Town
59
Title Proper –Choosing the Title Proper
The typography on this title page only confuses us – it uses four different fonts for the ‘title’ strings
You can look at other sources within the resource to inform your decision. In this case, other sources
(cover, back cover, last printed page) indicate the publisher’s intent that the title is “Through the Walls.”
60
Title Proper –Choosing the Title Proper
Sometimes, you just use common sense: The title is neither “The Book of”, nor “London” The facing pages constitute a ‘collective’ title
page 61
62
Title Proper –What it May and May Not Include (2.3.2.1)
An alternative title is treated as part of the title proper
The title proper does not include: parallel title (2.3.3) other title information (2.3.4) parallel other title information (2.3.5)
63
Title Proper –What is an ‘Alternative Title’?
“The second part of a title proper that consists of two parts (each of which has the form of an independent title), joined by a word such as “or” or its equivalent in another language.” Listening to popular music, or, How I learned to stop worrying and love Led Zeppelin
Note: This is not the same as a ‘variant title’
64
Title Proper –Transcription
“Transcribe a title as it appears on the source of information” (2.3.1.4)
Examples (many in 2.3.1.4 and 2.3.2.7) The most of P.G. Wodehouse IV informe de gobierno Supplement to The conquest of Peru and Mexico
λ-calculus and computer theory L'éducation 25 ans plus tard! Et après?
Changes in title proper 2.3.2.12 - 2.3.2.13
65
Title Proper –Errors
245 $a Teusday’s tasks246$ i Corrected title:$a Tuesday’s tasks
245 $a Zoology studies246 $i Misspelled title on number 1: $a
Zooology studies
Don’t correct errors for monographs provide a note to explain
Do correct errors for serials and integrating resources
66
Title Proper –Collective Titles
With a collective title Record the collective title as the title proper
Three notable stories(Table of contents lists three short stories) *
Without a collective title Record the titles as they appear on the
source, separated by <space>;<space> En famille ; Deux amis ; et La ficelle
* This preference to use the collective title applies, even if the title page also lists the individual titles
67
Parallel Title Proper(2.3.3)
CORE ELEMENT for LC/PCC Scope = “Title proper in another
language and/or script” Source: any source within the resource Follow instructions for transcription of
titles Punctuation: <space>=<space> MARC 245 $b
For serials, recorded in the 246 field Examples …
68
Parallel Title Proper –Examples
Single parallel title 245 10 $a Einführung in die Blutmorphologie = $b Introduction to the morphology of blood
More than one parallel title Record in the order on the resource 245 10 $a Strassenkarte der Schweiz = $b Carte routière de la Suisse = Road map of Switzerland
69
Other Title Information(2.3.4)
CORE ELEMENT for LC Scope = “information that appears in
conjunction with, and is subordinate to, the title proper of a resource”
Explicit instruction regarding sources ‘on the same source as the title proper’
MARC 245 $b Examples (many more in 2.3.4.3)
Kerouac : $b the definitive biography Linguistics and language behavior abstracts : $b LLBA
70
Other Title Information(cont.)
Can include any phrase appearing with a title proper that is indicative of: the character, contents, etc., of the resource,
or the motives for, or occasion of, its production,
publication, etc. Includes subtitles, etc. Does not include variations on the title
proper (e.g., spine titles, cover titles, etc.) or designations of parts, sections, or supplements
71
Variant Titles(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” NOT ‘alternative title’
Examples in 2.3.6.3 MARC 246 Examples …
72
Variant Titles –Examples
245 $a NFL rocks246 $a National Football League rocks
245 $a Listening to popular music, or, How I learned to stop worrying and love Led Zeppelin246 $a How I learned to stop worrying and love Led Zeppelin
245 $a Sechs kleine Stücke für Anfänger = $b Six easy pieces for beginners246 $a Six easy pieces for beginners
245 $a Four the moment246 $a We're still standing
73
Earlier Title Proper(2.3.7)
“a title proper appearing on an earlier iteration of an integrating resource that differs from that on the current iteration”
Take from “sources in earlier iterations of an integrating resource, using the source specified for the title proper”
Record “if considered important for identification or access”
MARC 247
74
Later Title Proper(2.3.8)
“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”
Take from “sources in later issues or parts of a multipart monograph or serial, using the source specified for the title proper”
Record “if considered important for identification or access”
MARC 246
75
Statement of Responsibility (2.4)
CORE ELEMENT if it relates to title proper
Scope = “a statement relating 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
76
Statement of Responsibility –Sources (2.4.2.2)
Take from the following sources(in this 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 at 2.2.4 Per LC-PCC PS 2.2.4, record in brackets
only if taken from outside the resource
77
Statement of Responsibility -- Transcription
“as it appears on the source of information (see 1.7)”
LC-PCC PS 2.4.1.4 (Option): “Generally do not abridge a statement of responsibility.”
Source: Dr. Logan Carroll, Harvard Medical School
RDA allows: 245 … / $c Logan Carroll.LC/PCC: 245 … / $c Dr. Logan Carroll, Harvard
Medical School.
78
Statement of Responsibility --Multiple Entities in a Statement (2.4.1.5)
LC-PCC PS 2.4.1.5: “Generally do not omit names in a statement of responsibility.”
Source: by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson.
RDA allows: 245 $a … / $c by Susan Brown [and four others].
LC/PCC: 245 $a … / $c by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson.
79
Statement of Responsibility –Multiple Statements (2.4.1.6)
Only the first is required See Core statement at 2.4 Other statements of responsibility are
optional
If you record more than the first … Record them in the order indicated by the
sequence, layout, or typography of the source of information
Separated by <space>;<space>
80
Statement of Responsibility –Examples
par Charles M. Schultz
edited and introduced by Mrs. C.F. Leyel
L.H. Booth, P. Fisher, V. Heppelthwaite,
and C.T. Eason
by F. Scott and Zelda Fitzgerald ;
selected by Scottie Fitzgerald Smith and
Matthew J. Bruccoli ; with a foreword by
Scottie Fitzgerald Smith (only the first is required)
[collected by] Chet Williams
Statement of Responsibility –Noun Phrases
81
Discuss, then we’ll see the ‘answers’…
Statement of Responsibility –Noun Phrases
245 14 $a The coming of the night / $c a novel by John Rechy.
82
245 10 $a Marilyn’s daughter : $b a novel / $c by John Rechy.
83
Edition Statement(2.5)
CORE ELEMENTS Designation of edition Designation of named revision of an
edition Scope = “a statement identifying the
edition to which a resource belongs” may include a designation of a named
revision of an edition may include a statement or statements
of responsibility relating to the edition and/or to a named revision of an edition
84
Edition Statement –Sources and Transcription
Sources: Priority order the same source as the title proper another source within the resource itself one of the other sources specified at 2.2
Transcription: “as it appears on the source” (1.7) “use only those abbreviations found in the
sources” (Appendix B4) “record numerals in the form in which they
appear on the source” (1.8.2 (alternative)) MARC 250 $a
85
Edition Statement –Examples
250 $a Second edition
250 $a 2nd enlarged ed., revised
250 $a Third revised edition
250 $a 52nd edition
250 $a Nouvelle édition
But … because they appear this way on the source
86
Numbering of Serials(2.6)
CORE ELEMENTS Numeric and/or alphabetic designation of
first issue or part of sequence Chronological designation of first issue or
part of sequence These designations for the last issue or
part of sequence Scope = “the identification of each of
the issues or part of a serial” Generally, transcribe as on the
resource
87
Numbering of Serials –Examples
Vol. 1, no. 1
July/August 2005
88
Production, Publication, Distribution, Manufacture, Copyright
89
Production Statement (2.7)
CORE ELEMENT for resources issued in unpublished form
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”
We will not cover this element in detail. Consult 2.7 as necessary.
90
Publication Statement(2.8)
CORE ELEMENTS for published resources Place Publisher Date
Scope = “a statement identifying the place or places of publication, publisher or publishers, and date or dates of publication of a resource”
Sources for each sub-element in 2.8 LC-PCC PS instructions for CIP materials
MARC field 264, second indicator 1
91
Place of Publication(2.8.2)
CORE ELEMENT: if more than one, only the first is required
Sources: priority order same source as the publisher’s name another source within the resource other sources specified in 2.2.4
Transcribe as it appears on the source Include both the local place name and
the larger jurisdiction if present May add larger jurisdiction if not already on
the resource – cataloger judgment
92
Place of Publication Not Identified
If place of publication is not identified: Supply the place or a probable place of
publication whenever possible for the benefit of users and catalogers
LC-PCC PS 2.8.2.6 reinforces this preference for supplying a place
If no place can be determined: [Place of publication not identified] But then you must also record distributor
information (2.9.2) “Core if” requirement to be removed April 2015 May still record, additionally, per judgment
93
Place of Publication -- Instruction Change Pending
In April 2015, the CORE IF statements for Distributor/Manufacturer information will be removed
Distributor/Manufacturer elements will not be required, even if the place of publication is not identified
Catalogers will be permitted to record the data in additional 264 fields if, in their judgment, it is considered useful
94
Place of Publication –Examples
On resource: London -- New York – Boston264 #1 $a London or264 #1 $a London ; $a Boston or264 #1 $a London ; $a New York or 264 #1 $a London ; $a New York ; $a Boston
264 #1 $a Red Oak [Iowa] (addition OK, but not required)
Known local place: [Toronto]Probable local place: [Munich?]
Known country, state, etc.: [Canada]
Probable country, state, etc.:[Spain?]
Supplying a place:
95
Publisher’s Name(2.8.4)
CORE ELEMENT: if more than one, only the first is required
Sources: priority order same source as the publisher’s name another source within the resource other sources specified in 2.2.4
Transcribe as it appears on the source LC-PCC PS 2.8.4.3: “Generally do not
omit levels in corporate hierarchy.” Record terms indicating the function of
the entity as they appear on the source
96
Publisher’s Name Not Identified
Record [publisher not identified] if: no publisher is named within the resource
and the publisher cannot be identified from
other sources Recorded in brackets because the
statement is not from the resource Probable publisher not allowed (2.4.2.7)
OK: [ABC Books] Not OK: [ABC Books?]
97
Publisher’s Name –Examples
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
Source: Toronto -- Pilkington Pub. Co. Houston -- Davidson Publishers 264 #1 $a Toronto : $b Pilkington Pub. Co.
264 #1 … $b [publisher not identified]
98
Date of Publication(2.8.6)
CORE ELEMENT Sources: priority order
same source as the publisher’s name another source within the resource other sources specified in 2.2.4
“Record dates … as they appear on the source of information” (2.8.1.4) Do not convert roman numerals to Arabic
(LC-PCC PS 1.8.2, First Alternative) If the date on the source is not of the
Gregorian or Julian calendar, add dates of Gregorian or Julian calendar
99
Dates for Multipart Monographs,Serials, and Integrating Resources
2.8.6.5 if the first issue is available:
1988- if publication has ceased or is complete and
the first and last issues are available:1968-1973
if publication has ceased or is complete and the last issue is available, but not the first:-1977
if the date is the same for all issues:1997
For an integrating resource, supply the date of the last update if considered to be important:1995–1998 [updated 1999]
100
Dates for Multipart Monographs,Serials, and Integrating Resources
If the first and/or last issue, part, or iteration is not available, supply an approximate date or dates.
If the date or dates cannot be approximated, do not record a date of publication.
[1998]- [Earliest issue available: v. 1, no. 3, July 1998]
1997-[2000] [Last part not available; information about ending date known]
[1988-1991] [First and last issues not available but information about beginning and ending dates known]
101
Date of Publication Not Identified
If date of publication is not identified: supply the date or approximate date of
publication whenever possible LC-PCC PS 2.8.6.6 reinforces this preference
for supplying a date If no date can be determined:
[date of publication not identified] But then you must also record distributor
information “Core if” requirement to be removed April 2015 May still record, additionally, per judgment
102
Date of Publication --Instruction Change Pending
In April 2015, the CORE IF statements for Distributor/Manufacturer information will be removed
Distributor/Manufacturer elements will not be required, even if the date of publication is not identified
Catalogers will be permitted to record the data in additional 264 fields if, in their judgment, it is considered useful
103
Supplying Dates --Five Types in 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 264 $ … c [between 2008 and 2010?]
Earliest and/or latest possible date known 264 $ … c [not before January 15, 2010] 264 $ … c [not after August 21, 2013]
104
Guidance on Supplying Dates –LC-PCC PS 2.8.6.6
o How do you determine a date when there is no clear publication date? Copyright, Distribution, or Manufacture data
often, you can infer from a copyright date, if this seems reasonable
you may be able to reasonably infer from distribution or manufacture dates
hints from Forward, Preface, Bibliography remember these possibilities:
‘not before … ’ ‘not after … ’ ‘between … and … ’
105
Supply Probable Publication Data!!!
LC Policy strongly encourages you to supply a probable place and date when this information is not on the resource
Pending instruction change, April 2015 ‘Core if’ status for Distribution and
Manufacture statements will be removed Not required to be recorded, even if
publication data not identified But permitted to be added, per judgment
106
Supplying Publication Data –Which of These do you Prefer?
On source: ABC Publishers, 2009Distributed 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-Preferred: 264 #1 $a [Seattle?] : $b ABC Publishers, $c 2009.
107
Supplying Publication Data –Which of These do you Prefer?
On title page: Means Pub. Co., Omaha, NebraskaOn title page verso: 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-Preferred: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co, $c [2009?]
108
But …
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]
o Sometimes, Distribution data must be recorded to provide useful information
109
And in other cases, Distribution or Manufacturing information can be extremely useful in identifying the manifestation, even if not ‘required’
For example … Manifestations without ISBNs Small press publications, for which the
user may be interested in the book as a product of the printer
Other situations in which the information is considered useful
And …
110
CORE ELEMENT only when publication information is not identified
Transcribed as are publication elements only the first is required as it appears on the source include larger jurisdiction if present; can add do not omit hierarchy
LC-PCC PS 2.9: “give a complete distribution statement”
MARC field 264, second indicator 2
Distribution Statement(2.9)
111
Distribution Statement --Instruction Change Pending
In April 2015, the CORE IF statement for this element will be removed
Distribution data will not be required, even if publication data is not identified
Catalogers will be permitted to record it in addition if, in their judgment, it is considered useful
112
CORE ELEMENT only when neither publication nor distribution is identified
Transcribed as are publication elements• only the first is required• as it appears on the source• include larger jurisdiction if present; can add• do not omit hierarchy
LC-PCC PS 2.9: “give a complete distribution statement”
MARC field 264, second indicator 3
Manufacture Statement(2.10)
113
Manufacture Statement --Instruction Change Pending
In April 2015, the CORE IF statement for this element will be removed
Manufacture data will not be required, even if neither publication nor distribution data is identified
Catalogers will be permitted to record it in addition if, in their judgment, it is considered useful
114
Copyright Date(2.11)
CORE ELEMENT if neither publication nor distribution date is identified
LC-PCC PS 2.11: Not required for multipart monographs, serials, and integrating resources
Precede by copyright symbol (©) or phonogram symbol ()
$c only; no ending period MARC field 264, second indicator 4
Example: 264 #4 $c ©2002
115
Copyright Date --Instruction Change Pending
In April 2015, the CORE IF statement for this element will be removed
Copyright data will not be required, even if neither publication date nor distribution date is identified
Catalogers will be permitted to record it in addition if, in their judgment, it is considered useful
MARC field 264, second indicator 4
116
Series, Mode of Issuance,and Frequency
117
Series (2.12) –LC Policy
LC policy is to not “trace” series This means that no authorized access
points are made for series However, some elements in the series
statement are CORE and must be recorded in the MARC 490 field title proper of series numbering within series title proper of subseries numbering within subseries
MARC field 490, first indicator 0
118
Recording Series Statements
Specific sources for each element Transcribe the elements as they
appear on the source of information If the resource belongs to more than
one series/subseries, record each series statement separately (2.12.1.5)
Record changes in series statements as instructed in 2.12.1.6
119
Title Proper of Series …and of Subseries
CORE ELEMENTS Sources: priority order
Series title page Another source within the resource Other sources as indicated in 2.2.4
Record the series title proper as you do other titles (2.3.1) “take what you see” capitalization
120
Other Title Information of Series …and of Subseries
Record other title information only if it is considered necessary for the identification of the series
May only be recorded if from the same source as the title proper of the series
Example:
490 0# $a English linguistics, 1500-1750
Other title information of series:a collection of facsimile reprints
121
ISSN of Series …and of Subseries
CORE ELEMENT for LC/PCC Sources: priority order
series title page another source within the resource other sources specified at 2.2.4
MARC 490 $x
122
Numbering Within Series …and Within Subseries
CORE ELEMENT Record the numbering of the resource
within the series as it appears on the source of information
Guidelines are generally the same as those for numbering of serials Special situations discussed in 2.12.9
MARC 490 $v
Examples: 490 $a … $v volume 32490 $a … $v Band LXXXVIII
123
Mode of Issuance(2.13)
CORE ELEMENT for LC/PCC Scope = “a categorization reflecting
whether a resource is issued in one or more parts, the way it is updated, and its intended termination”
Sources: Use evidence presented by the resource itself (or on any accompanying material or container)
‘Closed vocabulary’ terms in 2.13.1.3
124
Mode of Issuance –LC Practice
MARC Leader: Bibliographic Level
m - single unit- multipart monograph
s - serial i - integrating resource
125
Frequency(2.14)
CORE ELEMENT for LC/PCC Scope = “intervals at which the issues
or parts of a serial or the updates to an integrating resource are issued”
Sources: take from any source ‘Closed vocabulary’ terms in 2.14.1.3 MARC 310/321: current/former Examples:
weekly
monthly
126
Identifier for the Manifestation(2.15)
CORE ELEMENT If more than one, prefer an internationally
recognizable identifier; others are optional Scope = “a character string associated
with a manifestation that serves to differentiate that manifestation from other manifestations” What is this???
Sources: take from any source
127
Identifier for the Manifestation –Categories
ISBN, ISSN, and others based on internationally recognized schemes
those assigned by publishers, etc., following their internal schemes
“fingerprints” (i.e., constructed by combining groups of characters from specified pages of a printed resource)
music publisher numbers and plate numbers
not URLs (RDA 4.6)
128
Identifier for the Manifestation –Recording
Record in accordance with prescribed display format (e.g., ISBN, ISSN, URN)
For a resource consisting of two or more parts if there is an identifier for the resource as a
whole, and identifiers for the individual parts, record the identifier for the resource as a whole
If known to be incorrect in the resource, record it as it appears and indicate that it is incorrect, cancelled, or invalid, as appropriate
If the resource bears more than one identifier of the same type, add a brief qualification
129
Identifiers for the Manifestation –Examples
020 ## $a 9789070002343
020 ## $a 0435916610 (pbk.)
020 ## $a 0387082662 (U.S.)
020 ## $z 0870684302 (invalid)
022 ## $a 0046-225X
Notes
Bibliographic data that provides further detail about the resource Helpful to the user
Might not appear in a ‘preferred source’ Thus, not recorded in another element
Sometimes called ‘details on’ in RDA Often recorded in a 5XX field
130
131
Note on Manifestation(2.17)
Scope = “a note providing information on attributes of the manifestation”
Sources: take from any source CORE ELEMENTS for LC/PCC
Note on Title Note on Issue, Part or Iteration Used as the
Basis for Identification of the Resource
132
Note on Title (2.17.2)
Scope = note providing information on: the source from which a title was taken the date the title was viewed variations in titles inaccuracies, deletions, etc. other information relating to a title
LC-PCC Core: source of title always record source of title information in a
CONSER standard record
Examples: Title from containerTitle from caption
133
Note on Issue, Part, or Iteration Used as Basis for Identification (2.17.13)
Scope = “a note identifying what was used to identify the resource” the issue or part of a multipart monograph
or serial the iteration of an integrating resource the date an online resource is viewed
LC-PCC Core: always give in CONSER records multipart monographs: if the description is
not based on the first issue or part MARC 588 field
134
Note on Issue, Part, or Iteration Used as Basis for Identification -- Examples
588 ## $a Description based on: part 2, published 1998.
588 ## $a Description based on: Volume 1,issue 1 (2012); title from home page publisher's Web site, viewed May 16, 2012).
588 ## $a Description based on version consulted: Oct. 26, 2000.
135
Other Notes
Not LC CORE Note on Statement of Responsibility 2.17.3 Note on Edition Statement
2.17.4 Note on Numbering of Serials 2.17.5 Note on Production Statement 2.17.6 Note on Publication Statement 2.17.7 Note on Distribution Statement 2.17.8 Note on Manufacture Statement 2.17.9 Note on Copyright Date 2.17.10 Note on Series Statement 2.17.11 Note on Frequency 2.17.12
136
Unit 5: For Further Assistance
OCLC Support RDA Bibliographic Record Practice
Workform
137
OCLC Support
“Bibliographic Formats and Standards” “a guide to machine-readable
cataloging records in WorldCat” Provides tagging conventions, input
standards and guidelines for entering information into WorldCat
Currently under revision
http://oclc.org/bibformats/en.html
138
RDA Bibliographic RecordPractice Workform
Another Way to Practice aid in learning RDA Structure record RDA or LC-PCC PS # for every
element electronic version at:
http://staff.loc.gov/sites/lstraining/take-a-class/course-materials/dcat-use-rda/
139
Exercises:Identifying Manifestations
Exercise #1 Identifying
Manifestations
Complete as homework for next module