LC Training for RDA: Resource Description & Access Module 1: Introduction to RDA; Identifying Manifestations and Items Cooperative and Instructional Programs

LC Training for RDA:Resource Description & Access

Module 1: Introduction to RDA;Identifying Manifestations and Items

Cooperative and Instructional Programs DivisionLibrary of Congress

Revised November 26, 2012

2

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

3

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.

4

Learning Objectives for Module 1 -- Introduction

to RDA; Identifying Manifestations and Items

o Introduction and Backgroundo Overview of RDAo Supplemental Resourceso Identifying Manifestations and Items

5

Unit 1: Introduction and Background

Why RDA? How Did RDA Come to Be? FRBR as a Foundation of RDA

6

“Why RDA?”

Evolving cataloging environment RDA an improvement over AACR2

‘Why don’t we just revise AACR2?’

7

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

8

Web frontend

Services

VIAF

Databases, Repositories

LCSH

The Cataloging Environment

9

The Cataloging Environment -- Current

Web-basedWide 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.

10

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

11

How Did RDA Come To Be?

‘AACR3?’

12

AACR3

AACR3

Resource Description & Access

13

Collaborations with Other Communities

IFLAPrinciples, 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

Other Collaborations

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

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

Resulting records usable in the digital environment (Internet, Web OPACs, etc.)

Resulting records readily adaptable to newly emerging database structures

17

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

18

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)

19

International Cataloguing Principles (ICP)

o Convenience of the usero Representationo Common usageo Accuracyo Sufficiency and necessityo Significanceo Economyo Consistency and standardizationo Integrationo Defensible, not arbitrary

• If you contradict, take a defensible, practical solution.

Original Work - Same

Expression

Same Work – New Expression

New WorkCataloging Rules Cut-Off Point

DerivativeEquivalent Descriptive

Facsimile

Reprint

ExactReproduction

Copy

MicroformReproduction

Variations or Versions

Translation

Simultaneous“Publication”

Edition

Revision

SlightModification

ExpurgatedEdition

IllustratedEdition

AbridgedEdition

Arrangement

SummaryAbstractDigest

Change of Genre

Adaptation

DramatizationNovelizationScreenplay

Libretto

FreeTranslation

Same Style orThematic Content

Parody

Imitation

Review

Criticism

AnnotatedEdition

Casebook

Evaluation

Commentary

Family of Works

21

Work

Expression

Manifestation

Item

is realized through

is embodied in

is exemplified by

FRBR/FRAD Refresher – Relationships

InherentInherent Group 1 Group 1 RelationshipsRelationships

22

Work

Expression

Manifestation

Item

is owned by

is produced by

is realized by

is created by

Person

Corporate Body

Family

FRBR/FRAD Refresher – Relationships

RelationshipsRelationshipsBetweenBetween Groups 1 and 2 Groups 1 and 2

23

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

LC Control No. : 47023612 LCCN Permalink : http://lccn.loc.gov/47023612 Type of Material : Book (Print, Microform, Electronic, etc.) Personal Name : Shakespeare, William, 1564-1616. Main Title : ... Hamlet, traduit par Andre Gide.Published/Created : [Paris] Gallimard [1946] Description : 2 p. l., 7-237, [2] p. 17 cm.

CALL NUMBER : PR2779.H3 G5Copy 1 -- Request in : Jefferson or Adams Bldg General or

Area Studies Reading Rms

Shakespeare, William, 1564-1616. Hamlet. French.

How FRBR/RDA isAlready Evident in LC ILS

http://lccn.loc.gov/47023612

http://catalog.loc.gov/cgi-bin/Pwebrecon.cgi?SC=Author&SEQ=20080513101540&PID=29879&SA=Shakespeare,+William,+1564-1616.





Work

Person

26





Expression

27





Manifestation

28





Item

29

You see, FRBR is not so very different from what we do now!

30

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

Exemplary novels

Don QuixoteCervantes

English

French

German

Spanish Madrid, 1979

Library of CongressCopy 1Green leather binding

31

Unit 2: Overview of RDA

RDA Terminology RDA: What it is The Structure of RDA

32

RDA Terminology

AACR2 RDA

heading authorized access point

author, composer, artist, etc.

creator

main entrypreferred 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”

33

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 type2. media type3. carrier type

chief source preferred sources

34

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.

35

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

36

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

37

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

38

RDA: What it is -- Controlled Vocabularies

Only a few are closed lists Content type Media type Carrier type Mode of issuance

Most are open lists Cataloger can supply term if not in list

Vocabularies registered on the Web (http://metadataregistry.org/rdabrowse.htm)

39

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

40

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)

41

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)

42

The Structure of RDA:Core-ness

Based on attributes mandatory for a national level record (FRBR/FRAD)

Defined at the element level Always “Core if” – situation described

Core elements listed: as a group in RDA 0.6 separately in appropriate chapters

LC has identified additional elements as “LC Core”

CORE ELEMENT

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

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

46

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%20RDA%20course%20table.html

LC’s training materials Program for Cooperative Cataloging Web Page

http://www.loc.gov/aba/pcc/ PCC policies

Task Group reports

47

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

R-5 MARC 21 encoding to accommodate RDA elements: LC practice for November 2011+

R-6 Name authority record printouts

R-7 Some possible RDA implementation scenarios

R-8 Shelflisting Monographs Cataloged with RDA

48

Unit 4: IdentifyingManifestations and Items

Identifying RDA Records Sources Transcription Where are the Instructions? Detailed Discussion of Elements

49

Identifying RDA Records

Leader/18 contains the value “i” (ISBD punctuation included)

040 $e contains the code “rda”

50

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

51

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

52

Sources: Resources Issued inMore Than One Part

e.g., serials, multiparts, integrating resources, kits

RDA 2.1.2.3 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

53

Sources:Moving-Image Resources

Typically contained in carriers such as film, DVD, etc.

Generally, where the title appears RDA 2.2.2.3 priority order

Title frames or title screens Label permanently printed on or affixed to the

resource (excluding accompanying textual material or a container)

embedded metadata in textual form containing a title

source with formal presentation Alternative: use label, skip title frames

54

Sources:Other Resources

RDA 2.2.2.4 priority order Label Embedded metadata in textual form

containing a title If neither of the above is appropriate,

use a source where the data is formally presented

55

Sources:Other Sources of Information

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)

56

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

57

Transcription: ‘Take What You See and Accept What You Get’

What does this mean for you?

Alternatives at RDA 1.7.1 allow for in-house 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.”

58

Transcription:Capitalization

RDA 1.7.2 “Apply the instructions on capitalization

found in Appendix A.” LCPS 1.7.1 First Alternative

“For capitalization of transcribed elements, either “take what you see” on the resource or follow [Appendix] A.”

Your choice!

59

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!

60

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

61

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).

62

Transcription:Language and Script

RDA 1.4 “Transcribe … in the language and script found in the

resource” List of elements to be transcribed

Non-transcribed elements 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)

63

RDA Chapters for the Remainderof this Module

The remainder of this module covers the identification of manifestations and items.

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.

64

What am I Cataloging?

65

RDA Chapters for the Remainderof this Module

Chapter 2: Identifying manifestations and items

Primary focus on: LC core elements

66

Core Elements from Chapter 2:“Identifying Manifestations

and Items”

67

Title and Statement of Responsibility (RDA 2.3 – 2.4)

Title proper Parallel title proper Other title information Statement of responsibility

68

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

69

Title Proper Transcription

General guidelines on titles (RDA 2.3.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

70

Examples:Error in Title Proper

RDA record for this monograph: 245 $a Teusday’s tasks

246$ i Corrected title: $a Tuesday’s tasks

RDA record for a serial: 245 $a Zoology studies 246 $i Misspelled title on number 1:

$a Zooology studies

AACR2 record for a monograph: 245 $a Teusday’s [i.e. Tuesday’s] tasks

71

Parallel Title Proper

LC CORE ELEMENT

RDA 2.3.3

Scope = title proper in another language or script

Sources expanded to any source -- not just same source as title proper

MARC 245 $b

72

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

73

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

74

Recording Variant Titles

LCPS 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 authorized 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

75

Earlier Title Proper andLater Title Proper

RDA 2.3.7 - 2.3.8

Earlier title proper Of an integrating resource (MARC 247) Of a serial or multipart monograph if not cataloged

from first issue or part (MARC 246) Later title proper (MARC 246)

For minor changes in title proper of a serial For changes in title proper of a multipart

monograph

76

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

77

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

78

Statement of Responsibility Relatingto 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.”

Source: Dr. Logan Carroll, Harvard Medical School

RDA/LCPS: 245 … / $c Dr. Logan Carroll, Harvard Medical School.

RDA allows: 245 … / $c Dr. Logan Carroll.

79

Statement of Responsibility Relating to Title Proper - Transcription

LCPS: “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].

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.].

“Rule of Three” -- Change from AACR2!

80

If Multiple Statements ...

Only the first recorded is required If you record more than the first …

Record them in the order indicated by the sequence, layout, or typography of the source of information (RDA 2.4.1.6)

If not giving all statements of responsibility, give preference to those that identify 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 _____”

81

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

82

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: Third revised editionAACR2: 250 $a 3rd rev. ed.RDA: 250 $a Third revised

edition

Source: 2nd enlarged ed., revisedAACR2: 250 $a 2nd enl. ed., rev.RDA: 250 $a 2nd enlarged ed., revised

83

Recording Changes of 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 if … 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

84

Numbering of Serials: for First or Last Only Sequence

LC CORE ELEMENT

Numeric and/or alphabetic designation of first issue or part of sequence – RDA 2.6.2

Chronological designation of first issue or part of sequence – RDA 2.6.3

Numeric … of last issue or part of sequence – RDA 2.6.4

Chronological … of last issue or part of sequence – RDA 2.6.5

85

Recording Numbering of Serials

RDA 2.6.1 General guidelines:

Transcribe terms and months as on the resource

Alternative to record numerals as on the resource

Can give as formatted or unformatted 362 field

362 1# $a Began with January 2010 issue.

362 0# $a Volume X, number 1-

86

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

87

Production Statement

Date of production is an LC CORE ELEMENT for resource in unpublished form

RDA 2.7

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”

88

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 Choosing sources for CIP material

89

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 – cataloger judgment

90

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.

91

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

92

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]”

93

Examples:Supplying Place

Known country, state, etc.: [Canada]

Probable country, state, etc.: [Spain?]

Known local place: [Toronto]

Probable local place: [Munich?]

94

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

95

Examples: Place of Publication

On resource: London -- New York – Boston264 #1 $a London or264 #1 $a London ; $a New York ; $a

Boston

264 #1 $a [Place of publication not identified](Generally, no! LCPS says to supply a place if you can, even if just the country)

264 #1 $a Red Oak [Iowa] (addition OK, but not required)

96

Publisher’s Name

LC CORE ELEMENT - If more than one, only the first is required

RDA 2.8.4 Record the publisher's name in the

form in which it appears on the source of information

LCPS: do not omit levels in corporate hierarchy

97

More Than One Publisher

If you record more than one: Record the entities in the order indicated

by the sequence, layout, or typography of the names on the source of information

98

Publisher’s Name inMore 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

99

Publisher’s Name not Identified

If no publisher is identified within the resource or from other sources, record “[publisher not identified]” Not “[s.n.]”

100

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 Section264 #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]

101

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.

Add dates of Gregorian or Julian calendar if it’s not already on the source

Record supplied date in numerals if it appears in the form of chronogram; indicate that the information was taken from a source outside the resource itself

102

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-

103

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.

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.

1968-1973

-1977

104

Multipart Monographs, Serials,and Integrating Resources

For an integrating resource, supply the date of the last update if it is considered to be important.

If the date of publication is the same for all issues, parts, or iterations, record only that date as the single date.

1995–1998 [updated 1999]

1997

105

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 but information about ending date known]

[1988-1991] [First and last issues not available but information about beginning and ending dates known]

106

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]”

107

Examples:Supplying Dates

Title page verso: ©2009Item received in: 2008Date of publication: not givenTranscription: 264 #1 $a … $b … $c [2009]

optionally: 264 #4 $c ©2009 008/06: t008/07-10: 2009008/11-14: 2009

Title page verso: Copyright ©2009 Prefaced signed: June 2009Date of publication: not givenTranscription: 264 #1 $a … $b … $c [2009]008/06: s008/07-10: 2009008/11-14: ####

108


Title page verso: ©1978//Sixth Printing 1980Prefaced signed: June 1978Date of publication: not givenTranscription: 264 #1 $a … $b … $c [1978]

optionally: 264 #3 $a … $b … $c 1980.588 ## $a Description based on sixth

printing, 1980.008/06: s008/07-10: 1978008/11-14: ####

Title page verso: ©1980//1980 printingDate of publication: not givenTranscription: 264 #1 $a … $b … $c [1980]008/06: s008/07-10: 1980008/11-14: ####

109


Title page verso: Distributed in the USA in 1999Prefaced signed: London, January 1993Date of publication: not givenTranscription: 264 #1 $a … :$b … $c [between 1993 and 1999]008/06: q008/07-10: 1993008/11-14: 1999

Title page verso: Distributed 2008Bibliography includes citations to 2007 publicationsDate of publication: not givenTranscription: 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: ####

110


Title page verso: First Printing 1980Date of publication: not givenTranscription: 264 #1 $a … :$b … $c [1980]008/06: s008/07-10: 1980008/11-14: ####

Title page verso: 15th Impression 1980Date of publication: not givenTranscription: 264 #1 $a … :$b … $c [not

after 1980]optionally: 588 ## $a Description based

on 15th impression, 1980.

008/06: q008/07-10: uuuu008/11-14: 1980

111

Supplying Dates – 5 Categories in RDA 1.9

Actual year known264 $ … c [2010]

Either one of two consecutive years264 $ … c [2009 or 2010]

Probable year264 $ … 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]

112

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

113

Examples:Supplying Publication Data

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-Recommended: 264 #1 $a [Seattle?] : $b ABC Publishers, $c 2009.

114


On source: On title page: Means Pub. Co., Omaha, Nebraska

On 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-Recommended: 264 #1 $a Omaha, Nebraska : $b Means Pub. Co, $c [2009?]

115


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]

Sometimes, distribution information must be provided

116

• 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

Recording Distribution Information

117

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

118

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

119

Series, Mode of Issuance,and Frequency

Series Statement - RDA 2.12

Mode of Issuance – RDA 2.13

Frequency – RDA 2.14

120

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

Remember that LC policy is to not trace series; no authorized access points are made for series

121

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

122

Recording Changes in Series Statement

Multipart Monographs and Serials If a series statement is added, deleted, or

changed on a subsequent issue or part…, and this change cannot be stated clearly in the series statement, make a note if the change is considered to be important.

Integrating Resources If a series statement is added, deleted, or

changed on a subsequent iteration…, change the series statement to reflect the current iteration. Make a note if the change is considered to be important.

123

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

124

Recording Title Proper of Series

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

300 ## $a 5 volumes ;$c 14 cm.490 0# $3 volumes 1, 3-5: $a Music bibliographies ;$v

12, 15, 21-22490 0# $3 volume 2: $a Baroque musical studies ;$v 2 Note: Volumes of multipart monograph are in different

series

125

Title of Series in More Than One Language or Script

Choose the title proper of the series in the language or script of the content of the resource

490 0# Mercury series

Title of series also appears as: Collection Mercure. Resource in English

126

Title of Series in More Than One Form

Choose the title proper of the series on the basis of the sequence, layout, or typography of the titles on the source of information; if not, choose the most comprehensive title of series

Collection "À pleine vie"Title of series also appears as: À pleine vie

127

Other Title Information of Series

Record other title information of a series only if it is considered necessary for the identification of the series

490 0# $a English linguistics, 1500-1750

Other title information of series: a collection of facsimile reprints

128

ISSN of Series and Subseries

LC CORE ELEMENT RDA 2.12.8 and 2.12.16 MARC 490 $x now repeatable

LCPS for the optional omission in 2.12.8.3 Do not omit the ISSN of the main series if the

ISSN of the subseries is given

129

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

490 $a … $v volume 32

490 $a … $v Band LXXXVIII

130

Mode of Issuance

LC CORE ELEMENT LCPS 2.13.1.3 MARC Leader: Bibliographic Level

“m” for both “single unit” and “multipart monograph”

“s” for “serial” “i” for “integrating resource”

131

Frequency

LC CORE ELEMENT RDA 2.14 Scope = “intervals at which the issues or

parts of a serial or the updates to an integrating resource are issued”

Make a note (RDA 2.20.12.3) If appropriate term not in list in RDA

2.14.1.3 or the frequency is irregular For former frequency On a change in frequency

MARC 310/321 for current/former frequency

132

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.

133

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)

134

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

135

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)

136

Note on Manifestation or Item

LC CORE ELEMENTS – Note on Title Note on Issue, Part Used as Basis for

Identification of the Resource

RDA 2.20

137

Note on Title

LC CORE ELEMENT: Title source Monographs: provide if other than title page Serials: always give, combine with 588

“description based on” note RDA 2.20.2

Title from containerCaption title

138

Note on Issue, Part Used as Basis for Identification

LC CORE ELEMENT Always give in a serial record, even if based on first/last

issue or part (per CSR). RDA 2.20.13

Multipart monographs: 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

139

Examples: Note on Issue, Part Used as Basis for Identification

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.

140

Other Notes

Not LC CORE ELEMENTS

Note on Statement of Responsibility 2.20.3 Note on Edition Statement 2.20.4 Note on Numbering of Serials 2.20.5 Note on Production Statement 2.20.6 Note on Publication Statement 2.20.7 Note on Distribution Statement 2.20.8 Note on Manufacture Statement 2.20.9 Note on Copyright Date 2.20.10 Note on Series Statement 2.20.11 Note on Frequency 2.20.12

141

Unit 5: Exercises on Manifestations and Further Practice

Exercise #1-2 Identifying

Manifestations

142

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%20training%20materials/LC%20RDA%20Training/LC%20RDA%20course%20table.html