RDA Training Topic 1: Recording Attributes of Manifestation and Item

For Ohio State University LibrariesApril 2012

Prepared by the RDA Training Team

RDA: THE BIG PICTURE

RDAResource Description and Access (RDA) is A content standard that tells us what to put into

catalog records• Used with MARC

Replaces AACR2• Implementation for original cataloging at OSU will

occur in June 2012• National implementation is scheduled for March 2013

Available online: http://access.rdatoolkit.org/

FRBRFunctional Requirements for Bibliographic Records is a

conceptual model that is the foundation for RDA

Explains relationships between entities

Defines attributes of entities– Example: title is an attribute of a work

RDA uses the terminology of FRBR and provides guidelines for which attributes to record and how to record them

Group 1 Entities: Primary Relationships

Work: a distinct intellectual or artistic creation

Expression: the intellectual or artistic realization of a work in some form (e.g. alpha-numeric, musical notation)

Manifestation: the physical embodiment of an expression (e.g. a print publication)

Item: a copy of a manifestation

Hamlet--Work

French translation of text of Hamlet by Gide--Expression

Gide French translation of text of Hamlet published in 1946 by Gallimard—Manifestation

Copy of this text owned by the OSU Libraries--Item

realized in

embodied in

exemplified by

RDA GENERAL PRINCIPLES

Language and Script (RDA 1.4)

Elements should be transcribed from the resource in found language/script

• Alternative: record transliteration• Optional addition: give both vernacular form and

transliteration (OSU is taking this option)

Other elements should be transcribed in the language/script preferred by the agency

Principle of Representation

Transcribed information = “Take what you see” and “accept what you get” – general guideline at RDA 1.7.1:• Capitalization, punctuation, abbreviations, inaccuracies,

symbols, numerals

Alternatives: • Follow in-house guidelines or preferred style manual• Accept data from scanning, downloading

Principles of Representation

Appendix A for capitalization• Contains Instructions for some specific situations• But alternatives (RDA 1.7) possible

Appendix B for abbreviation• Except in a few specific situations, use

abbreviated forms appearing on the piece.• In specific situations, refer to RDA 1.7 for possible

abbreviations

Do not capitalize a compound term with unusual capitalization.

Describe it as it appears in the source (A.4)

Examplese-commerce

eBayhttp://english.aljazeera.net/watch_now/

eBooks

Pre-Cataloging Decision

Before you begin cataloging, decide what you are cataloging:

The whole, a part, a part of a part, or the whole and its parts together.

This decision affects other decisions(choice of title proper, who is responsible for the

content, etc.)

New description needed?

Changes requiring a new description (RDA 1.6)

New reasons:Change in mode of issuanceChange in media typeChange in edition statement: serials and

integrating resourcesThe re-basing of an integrating resource

Depends on the type of description (comprehensive, analytical, etc.)

Depends on mode of issuance, including number of parts

Basis for identifying the resource (RDA 2.1)

Mode of Issuance

Definition:

“A categorization reflecting whether a resource is issued in one or more parts, the way it is updated, and its intended termination” – RDA Glossary

Source of Information

Preferred source (not “chief source”)

Fewer categories for sources in RDA 2.2:

#1: Pages, leaves, etc., or images of pages …#2: Moving images#3: All other resources

• There can be more than one preferred source• Other sources of information can be used

Item Issued as a Single Unit

Choose a source of information identifying the resource as a whole

If there is no source of information identifying the resource as a whole, treat sources identifying its individual contents as a collective source for the resource as a whole

Example: you might have a single videodisc containing multiple feature films with no source identifying the resource as a whole

Resource Issued in More Than One Part

For a resource issued in more than one part, choose one of the following:

• If issues or parts are sequentially numbered, choose a source of information identifying the lowest available numbered issue or part

• If the issues or parts are unnumbered or not sequentially numbered, choose a source of information identifying the issue or part with the earliest date

Example: you might have a series of scientific treatises or a journal

Integrating Resources

For an integrating resource choose a source of information identifying the current iteration of the resource as a whole.

• If there is no source of information identifying the current iteration of the integrating resource as a whole, treat the sources of information identifying the current iteration of its individual contents as a collective source of information for the current iteration as a whole.

Example: you might have a Website that has been updated or perhaps you are adding content to a file of loose-leaf pamphlets

ISBD Conventions in RDAIt is OSU Policy to use ISBD punctuation

Ending Punctuation

“When punctuation occurring within or at the end of an element is retained, give it with normal spacing. Prescribed punctuation is always added, even though double punctuation may result.” (RDA D.1)

• 3rd ed..• Not: 3rd ed.

Bracketing

• When each data element is enclosed within separate sets of brackets

260 $a [Washington, D.C.] : $b [Government Printing Office], $c [2009?]

Ten Things to Remember

1. User needs/user tasks

2. “Take what you see”3. Work, Expression,

Manifestation, Item4. Core and Core If5. Alternatives, optional

omissions and optional additions

6. Fewer abbreviations7. Content, Media and

Carrier types8. No more “rule of 3”9. Sources of information

expanded10. Controlled vocabularies

RECORDING ELEMENTS OF DESCRIPTION OF THE MANIFESTATION

Cataloging a Manifestation

Most cataloging begins with a manifestation “in hand”

Record the attributes of the manifestation according to RDA instructions

Identifier for the manifestation (MARC 21 fields include 020, 022

RDA 2.15)

No change from AACR2

“Record both the identifier for the resource as a whole and any identifiers for individual parts, adding a qualification to each identifier” RDA 2.15.1.5, plus LCPS

020 ## 3854852177022 0# 1648-6897

RDA: TITLE

Title Elements

In AACR2 second level description (1.0D2) the following elements are required:

Title proper Parallel title Other title information

In RDA:

Only title proper is a core element (RDA 1.3)

Other titles are optional

OSU practice is to follow LC Core+: other titles are core

ParallelOther title informationEtc.

Title Proper

A title is a word, character, or group of words and/or characters that names a resource or a work contained in it (RDA 2.3.1.1)

Sources: • For the preferred source of information see

RDA 2.2.2-2.2.3• If there is no title in the resource see RDA 2.2.4

Title Proper TranscriptionRDA 2.3.1Transcribe the title exactly as it appears on the

source of information. Transcribe elements appearing on the source of

information following general guidelines on capitalization, punctuation, etc. (RDA 1.7.2-1.7.9)

Use the same spelling, punctuation and capitalization that appears on the original (including errors and inaccuracies).

Capitalization

DO capitalize the first word of the title proper (RDA Appendix A.4.1)• But not for other titles

After that, follow the principle of take-what-you-see

When the beginning of the phrase from which a title is derived has been omitted and is

replaced by punctuation, do not capitalize the first word. Rather, transcribe the punctuation

as it appears on the resource.(RDA A.4.2)

Examples… if elected : $b a memoir of a defunct politician

… and master of none-- and that is how it all began!

Examples of Title Proper

245 10 $a Alnomuc, or, The golden rule : $b with twenty-four engravings /$c John H. Amory.

245 10 $a Tillie Olosn , a profile246 $i $a Corrected title: $a Tillie Olson, a profile 245 10 $a Sports leaders & success : $b 55 top sports leaders & how they achieve greatness.

Title Proper for Serials and Integrated Resources

In general, transcribe the title as it appears on the resource (RDA 1.7.9)

However:“when transcribing the title proper of a serial or integratingresource, correct obvious typographic errors, and make a notegiving the title as it appears on the source of information”(RDA 2.3.1.4)

This means that when cataloging serials, correct obvious typographical errors in the title proper. If it is considered important for access, give the errant form of the title in a MARC 246 field

Errors in Title ProperMonograph vs. Serial

Monograph:

245__ $a Teusday’s tasks246__ $i Corrected title: $a Tuesday’s tasks

Serial: (RDA 2.3.1.4)

245 00 $a Zoology studies246 1_ $i Misspelled title on number 1:

$a Zooology studies

245 00 $a Housing starts246 1_ $i Sources of information on v.1, no. 1 reads: $a Housing sarts

Title of serial includes a date… If a title of a serial includes a date, name, number, etc., that varies

from issue to issue, omit this date, name, number, etc. Use a mark of omission (…) to indicate such an omission.”

If the source of information reads:

Report on the 4th Conference on Development Objective and Strategy

Transcribe the title as:

Report on the … Conference on Development Objective and Strategy

Punctuation

Transcribe the punctuation as it appears on the source (RDA 1.7.3),

or

Use the ISBD prescribed punctuation from Appendix D (RDA D.1.2)

Examples:Why is the sky blue?“The other" in American popular film

Symbols (RDA 1.7.5)

Transcribe symbols and other special characters as they appear on the source of information (RDA 1.7.5).

Examples:Barnes & NobleAll-in-One: CompTIA A+ Exam Guide, 7th Ed

Introductory Words in Title Proper

Omit introductory words such as “Disney presents”, if they are not intended to be part of the title (RDA 2.3.1.6)

For example:(If the source of information reads: Radio Pictures presents King Kong )

Transcribe as:245 00 $a King Kong.

Parallel Title Proper (RDA 2.3.3) [MARC 21 field 245, subfield $b]

Parallel titles are NOT core elements in RDA. However, OSUL and LC policy is that parallel

titles are “core if” applicableRDA does not have restrictions on how many

parallel titles can be recorded. They can all be recorded in the order they are presented on the source of information.

Example of Parallel Title245 10 $a International meteorological vocabulary =

$b Vocabulaire météorologique international = Mezhdunarodnyĭ meteorologicheskiĭ slovar’ = Vocabulario meteorológico internacional.

246 31 $a Vocabulaire météorologique international246 31 $a Mezhdunarodnyĭ meteorologicheskiĭ

slovar’ 246 31 $a Vocabulario meteorológico internacional

Other Title Information

In RDA, other title information is NOT core• It may be recorded, but it is not required

OSUL Policy:• Required LC Core+ element (if applicable):

transcribe in record for RDADo not capitalize first word“take what you see”

Other Title Information

Examples:

245 00 $a Gender, language, and myth : $bessays on popular narrative.

245 00 $a Education 14-19 : $b critical perspectives.

Collective Title When a source contains a collective title as well as the titles of its individual

contents , record the collective title as title proper (RDA 2.3.2.6)

245 10 $a Five novels.

(Source of information also includes the title of individual novels: Adventures of Tom Sawyer; Prince and the pauper; Adventures of Huckleberry Finn; Connecticut Yankee in King Arthur's Court; Tragedy of Pudd'nhead Wilson)

Access points should be created for each title, using MARC field 700 12 $i

contains (work) $a author. $t title. A 505 contents note can also be added if more clarification is needed.

As an optional instruction, the title of the individual contents

can be recorded as titles of related works (RDA 25.1)

Compilations Lacking Collective Title

If there is no collective title, record the titles proper of the parts as they appear on the source of information (RDA 2.3.2.9).

Example: 245 00 $a Fall River legend / $c Morton Gould.

Facsimile / Leonard Bernstein.

Alternative: Devise a Title

In addition to (or instead of) constructing access points for each of the works in the compilation, construct an authorized access point representing the compilation using a devised title formulated according to the instructions given under RDA 2.3.2.11

Indicate in a note that the title was devised (RDA 2.3.2.10)

No Title

If there is no title on the source, and a title can not be found using an external resource, devise a title based on the nature of the content or subject. Indicate in a note that the title was devised (RDA 2.3.2.10).

Example:245 05 $a [The Egyptian revolution]500 __ $a Title devised by cataloger

Example of devised title:

245 00 $a [Three Norwegian symphonies].500 __ $a Title devised by cataloger.505 0_ $a Sinfonia espressiva / Conrad Baden -- Symphony no. 3, op. 26 / Hallvard Johnsen -- Symphony no. 2 / Bjarne Brustad.700 12 $a Baden, Conrad. $t Symphonies, $n no. 6.700 12 $a Johnsen, Hallvard. $t Symphonies, $n no. 3, op. 26.700 12 $a Brustad, Bjarne. $t Symphonies, $n no. 2.

Note: Points of access have also been created for each title in the work

Later title proper (RDA 2.3.8)[MARC 21 field 246]

When the title proper is different on a later issue or subsequent part of a monograph

Record the change in the title proper if it is minor but considered important

Note which numbers or parts have the variant title

Make a general note if the changes have been numerous

If the change is significant, create a new record

Example of a Later Title (with a minor change)

The title proper of a periodical is recorded as Annual report of pipeline safety. Annual report on pipeline safety is a later title proper appearing on issues from 1999.

245 10 $a Annual report of pipeline safety. 500 __ $a Some issues have title: Annual report

on pipeline safety.

Earlier title proper (RDA 2.3.7)[MARC 21 field 247]

Applies to integrating resourcesWhen the title proper on an earlier iteration is

different from the current title properRecord earlier titles proper if considered importantNote which iterations have the earlier titleMake a general note if the changes are numerous

Example of Earlier Title

Business library for businessmen.(Earlier title proper issued in 1925. Current title proper: The Cumulative loose-leaf business encyclopedia).

245 04 $a The cumulative loose-leaf business encyclopedia.

500 ## $a Published 1925 under title: Business library for businessmen

STATEMENT OF RESPONSIBILITY(RDA 2.4)

Statement of Responsibility

Core element“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” (RDA 2.4.2)

Source of Statement of Responsibility

Sources: RDA 2.4.1.2• Same source as title proper• Another source within the resource• Another source: RDA 2.2.4

In RDA, the only statements of responsibility that will appear in square brackets are those taken from outside the resource (RDA 2.2.4)

Recording Statements of Responsibility

Transcribe as found on the source of information. (RDA 2.4.1.4)

245 … / $c by Rear Admiral Edwin T. Layton, U.S.N. (Ret.), with Captain John Pineau, U.S.N.R. (Ret.), and John Costello.

Example of a Statement of Responsibility245 10 $a Law of war deskbook / $c authors: LTC Jeff A. Bovarnick, JA, USA, LtCol J. Porter Harlow, USMC, CDR Trevor A. Rusch, JAGC, USN, MAJ Christopher R. Brown, JA, USANG, Maj J. Jeremy Marsh, USAF, MAJ Gregory S. Musselman, JA, USA, MAJ Shane R. Reeves, JA, USA.

Note: the “rule of 3” no longerapplies, all authors arerecorded.

Optional Omission: Abridge a statement of responsibility only if there is no loss of essential information

On source of information: by the most esteemed and wise Professor Harrison Smythe of the Society for Minimal Horticulture245 10 …/$c by Harrison Smythe

On source of information: Sponsored by the Library Association (founded 1877)245 10 …/ $c by the Library Association

Statement Naming More Than One Person, Etc. (RDA 2.4.1.5)

Record a statement of responsibility naming more than one person, etc. as a single statement regardless of whether the person, family, or corporate bodies named in it perform the same function or different functions:

245 10 …/$c by Nancy Drew, Bess Marvin, George Fayne, and Ned Nickerson.

Optional omission:

245 10 …/$c by Nancy Drew [and three others]*

*Note: the phrase “ … [et al.]” is not used

OSUL Local Policy

OSUL policy is to apply LCPS 2.4.1.5 which instructs cataloger’s to generally not omit names in the statement of responsibility

OSUL will provide access points for responsible entities – persons, families, or corporate bodies

If there are numerous names, apply cataloger’s judgment to determine if it is appropriate/practical to omit names

Clarification of Role (RDA 2.4.1.7)

If the relationship between the title, designation of edition, etc., and any person, family, or corporate body named in a statement of responsibility is not clear, add a word or short phrase clarifying the relationship.

Example:245 10 … /$c [collected by] Chet Williams.

Multiple Statements of Responsibility

100 1_ $a García Márquez, Gabriel, $d 1928-240 1_ $a Cien años de soledad. $l English245 10 $a One hundred years of solitude / $c Gabriel García Márquez ; Gregory Rabassa.700 1_ $a Rabassa, Gregory, $e translator.

Noun Phrase Occurring in Conjunction with a Statement of Responsibility

According to RDA 2.4.1.8 the noun phrase occurring in conjunction with a statement of responsibility are always considered part of the statement of responsibility.

(The source reads: research and text by Colin Barham)245 as … /$c research and text by Colin Barham

(The source reads: a novel by Heidi W. Durrow)245 14 $a The girl who fell from the sky / $c a novel by Heidi W. Durrow.

EDITION STATEMENTS

Designation of Edition and … Named Revision of an Edition

RDA 2.5.2 and 2.5.6

Marc 250 $a Designation of edition = a word, character, or

group of words and/or characters, identifying edition to which the source belongs.

Designation of a named revision = particular revision of a named edition.

In RDA, the edition statement is a transcribed (or Core) element

Use only abbreviations that appear on the source of information

When recording numbers expressed as numerals or as words, enter them in the form in which they appear on the source of information

Edition Statement

Edition Statement ExamplesAACR2 vs RDA

AACR2 1.2B1, B.5A

Source of information reads: Second edition

250__$a 2nd ed..

Source of information reads: Nouvelle edition.

250__$a Nouv. ed..

RDA 2.5.1.4, B.4, 1.8.1

Source of information reads: Second edition

250__$a Second edition.

Source of information reads: Nouvelle edition

250__$a Nouvelle edition.

Edition Statement ExamplesAACR2 vs RDA

AACR2 1.2B1, B.5A, C.2B1

Source of information reads: Version X.

250__$a Version 10.

Source of information reads: Ny udgave.

250__$a Ny udg.

RDA 2.5.1.4, B.4, 1.8.1

Source of information reads: Version X

250__$a Version X.

Source of information reads: Ny udgave

250__$a Ny udgave.

Statement of Responsibility

Transcribe statements of responsibility relating to the edition

Example: 250 $a Fourth edition / $b with maps redrawn by N. Manley

PUBLICATION INFORMATION AND DATE (CHAPTER 2): RDA 2.7-2.11

Place of publication (RDA 2.8.2)

If more than one place is listed, only the first recorded place is required – there is no “home country” provision

Supply a probable place whenever possible

MARC 260 $a

Supplying Place

Known local place[Toronto]

Probable local place[Munich?][Göteborg?, Sweden]

Known country, state, etc.[Canada]

Probable country, state, etc.[Spain?]

Place of Publication If no probable place can be determined, give “[Place of

publication not identified]”– but never give “[S.l.]”

Do not supply higher jurisdiction for a found local place

Do not correct fictitious or incorrect information; make a note to explain the error

Give probable information in brackets

MARC 260 $a

Examples: Place of Publication If the resource states that the work was published in

London, then the MARC 260 $a field should read:

260__$a London

If the resource states that the work was published in Red Oak, then the MARC 260 $a field should read:

260__$a Red Oak

Note: In the past the cataloger may have supplied the information that Red Oak is in Iowa. However, this is no longer necessary.

Examples: place of publication

If there is no publication data on the resource or if a place of publication can not be determined than the MARC 260 $a field should read:

260__$a [Place of publication not identified]

If there is an error in the publication data than the bibliographic record should contain a note such as:

260__$a Minneapolis500__$a Actually published in St. Paul

Publisher’s name (RDA 2.8.4)• If more than one is provided, only the first recorded

is required

• Do not shorten the form of name or use abbreviations (unless this is printed on the item)– you can omit corporate hierarchy

• If no publisher is identified, then give “[publisher not identified]”– never give “[s.n.]”

• MARC 260 $b

Examples: Publisher’s Name

260 … $b J.J. Wilson Publishing Company

(but not 260 … $b Wilson Pub. Co.)

No abbreviations are used. The full name of the publisher is spelled out as it appears on the source.

260… $b Pilkington Pub. Co.

(but not 260 … $b Pilkington Publishing Company)

Abbreviations are used only if the publisher’s name IS abbreviated on the source. Take what you see, use what you get.

Examples: Publisher’s Name

On source: Humanities Association, Literature Division, Renaissance Literature Section.

260 … $b Humanities Association, Renaissance Literature Section

Note: Corporate hierarchies are not transcribed.

If the publisher can not be identified, then indicate this in the 260 $b field. Supplement missing publication data with distribution data (upcoming slides).

260 … $b [publisher not identified]

Date of Publication (RDA 2.8.6)

If no publication date can be found on the resource, supply a probable date or range of dates whenever possible

If no probable date can be determined give “[date of publication not identified]”, do this only for single part monographs

MARC 260 $c

Supplying Dates (RDA 1.9)

If the actual year of publication is known260 … $c [2010]

Either one of two consecutive years can be determined

260 … $c [2009 or 2010]

The probable year can be determined, but is not known for sure

260 … $c [2010?]

A probable range of years can be determined (“between ___ and ___?”)

260 … $c [between 2008 and 2010?]

The earliest and/or latest possible dates are known (“not before,” “not after,” or “between ___ and ___”)

260 … $c [not before January 15, 2010]

An approximate date can be established

260 … $c [approximately 1950]

Note: The term “ca.” or circa is no longer used.

Supplying Dates (RDA 1.9)

Multipart Monographs, Serials, and Integrating Resources

(RDA 2.8.6.5)

Whenever possible, give the beginning and ending dates of the publication, particularly if you have the first and/or last issue, part, or iteration in hand

260 … $c 2001-2009.

Multipart Monographs, Serials, and Integrating Resources (RDA 2.8.6.5)

If the first and/or last issue, part, or iteration is not available, supply an approximate date or dates of publication

260 $c 1998-[2012]

Don’t record the date or dates of publication if they can not be identified or approximated. Do not use the phrase “[date of publication not identified]”

Using Distribution Data to Supplement Publication Data (RDA 2.9)

If publication data is missing, then use distribution data in the MARC 260 field. Use the same guidelines that you would use in recording publication data to record distribution data

This is only core if publication data is missing

Using Distribution Data to Supplement Publication Data (RDA 2.9)

Note: in MARC 260 $c the date of distribution cannot be explicitly identified as such (that is the date can not be differentiated from the date of publication)

In MARC 260 when $b is repeated the cataloger can add a designation of function in square brackets. (For example, [distributor])

Examples: Place of Distribution

On source: ABC Publishers, 2009, Distributed by Iverson Company, Seattle

260__$a [Place of publication not identified] : $b ABC Publishers ; $a Seattle, $c 2009.

On source: Sherman & Brothers, Inc., 2010 Distributed in Australia by Goodman Ltd.

260__$a [Place of publication not identified] : $b Sherman & Brothers, Inc. ; $a [Australia], $c 2010.

Examples: Distributor’s Name

On source: Chicago, 2009, RD Distributors, Evanston

260__$a Chicago : $b [publisher not identified] : $b RD Distributors, $c 2009.

On source: Published in 2010 and distributed by KL, Inc. in Boston and Ottawa

260 $a [Place of publication not identified] : $b [publisher not identified] ; $a Boston : $b KL, Inc. [distributor], 2010.

Examples: Date of Distribution

On source: Means Pub. Co., Omaha, Nebraska, 2009 distribution

260__$a Omaha, Nebraska : $b Means Pub. Co., $c [date of publication not identified], 2009.

On source: Published by Rand McNally; distributed in the U.S. by WM Services, 2010.

260__$a [place of publication not identified] : $b Rand McNally ; $a [U.S.] : $b WM Services [distributer], $c [date of publication not identified], 2010.

Using Manufacture Data to Supplement Publication or Distribution Data

(RDA 2.10)

If no publication or distribution data is available, then use manufacturing data in the MARC 260 field. Use the same guidelines that you would use in recording publication or distribution data.

Manufacture data is only core if there is no available publication or distribution data.

MARC 260 $e (for place) and $f (for manufacturing agency)

Example: Place of Manufacture

On source: Published 2009 by the International Group; 2009 printing, Johnson Graphics, New York and Buenos Aires. No distribution information available

260__$a [Place of publication not identified] :$b International Group, $c 2009 $e (New York)

Example: Place of Manufacture

On source: Published 2009 by the International Group; 2009 printing, Johnson Graphics, New York and Buenos Aires. No distribution information available

260 $a [Place of publication not identified] : $b International Group, $c 2009 $e (New York).

On source: Published in Boston, 2010, Cambridge, Kinsey Printing Company. No distribution information is recorded

260 $a Boston : $b [publisher not identified], $c 2010 $f (Kinsey Printing Company).

Examples: Manufacturer’s Name

On source: Published in Boston, 2010; Cambridge, Kinsey Printing Company, No distribution information is available

260__$a Boston : $b [publisher not identified], $c 2010 $f (Kinsey Printing Company).

On source: Published 2009; printed by B. Ross Printing (Arlington, VA), May 2009, No distribution information

260__$a [Place of publication not identified] : $b [publisher not identified], $c 2009 $e (Arlington, VA : $f B. Ross Printing).

Examples: Date of ManufactureOn source: Garrison Publishers, Tampa; 2010 Printing, no distribution or copyright date is recorded on the item

260__ $a Tampa : $b Garrison Publishers, $c [date of publication not identified] $g (2010).

On source: Printed for distribution in Western Europe by ZZZ Printers (London, Zurich, and Vienna) in 2009

260__$a [Place of publication not identified] : $b [publisher not identified], $c [date of publication not identified] $e (London : $f ZZZ Printers, $g 2009).

Copyright Date (RDA 2.11)

The copyright date is not a core element in RDA If neither date of publication nor date of distribution

can be identified, then the copyright date should be used. The copyright date can also be used to guess the date of publication

Precede all copyright dates by the symbol (©). For sound recordings use the phonogram symbol (). If the symbols can not be entered in the system then use the words copyright or phonogram (at OSU these symbols can be entered)

MARC 260 $c

Entering ℗ and © Symbols

In OCLC Connexion Client• Edit Enter Diacritics• Or use the ALA button on the toolbar

In Millennium• Tools Character Map Enclosed

Alphanumerics

Examples: Copyright Date

On source: Published by Iowa Department of Transportation, ©2009, 2010 printing, No distribution information is recorded

260__$a [Des Moines?] : $b Iowa Department of Transportation, $c [date of publication not identified], ©2009.

On source: On disc label: ELC Publishers, Chicago, 2010, No distribution information is recorded

260__$a Chicago : $b ELC Publishers, $c [2010], 2010.

EXTENT AND TYPES

ExtentThe “extent” of the resource includes such details as:Numbers of pages or volumesItem format and quantityIllustrated contentPhysical dimensionsAll the details that are appropriate to record

in the MARC 300 field

Extent

The extent is a core element

(but only when the resource is complete and/or the extent is known. It should never be used for

incomplete serial records)

Extent

The extent should contain no abbreviations, except for abbreviations contained in RDA B.7. For example, pages, illustrations, leaves and portraits all should be spelled out.

Use the term “approximately” in place of “ca.” and “that is” rather than “i.e.”

For subfield $a use controlled vocabularies from RDA 3.3.1.3

ExtentIndicating dimension:

Metric symbols, are not considered to be abbreviations and should be used in subfield $c (RDA B.5.1)

For example, use cm (for centimeters) [no period]

Abbreviations for measurements of duration (RDA B.5.3) should be used

For example, min. (for minutes) and sec.(for seconds)

(See RDA B.7 for a list of usable abbreviations)

Extent

In accordance with ISBD punctuation rules, the 300 field should not end with a full stop, unless the 3XX fields are followed by a series statement (in a 490 field).

If the 300 field ends in a dimensional indicator such as “sec.”, “min.”, or “in.”, than the line may appear to have a full stop. However, this is part of the abbreviation. A full stop should be added. (example: 45 min..)

Extent

Examples:300__1 online resource (xxvi, 140 pages) : $b illustrations,

maps

300__approximately 500 pages

301__xv, 408 pages, 30 unnumbered pages of plates : $b illustrations (some color), maps (some color) ; $c 24 cm

300 __1 computer disc ; $c 4 3/4 in.

Accompanying materials : (RDA 27.1)[MARC 21 field 300 $e]

RDA provides three options:

Describe accompanying materials in the MARC 300 field using subfield $e

or

Describe accompanying materials in a second MARC 300 field, whichever seems most appropriate.

or

Describe the accompanying materials in a 500 note.

Examples300 __ $a 1 computer disc (2 text files. 27 image files) : $b CD-ROM, PDF, JPEG, color illustrations ; $c 4 ¾ in., in pocket enclosure (22 cm) + $e 1 press release (1 page ; $c 30 cm)

Or

300 __ $a 1 computer disc (2 text files. 27 image files) : $b CD-ROM, PDF, JPEG, color illustrations ; $c 4 ¾ in., in pocket enclosure (22 cm) 300 __ $a 1 press release (1 page ; $c 30 cm)

Or

500 __ $a Accompanied by 1 press release (1 page ; $c 30 cm)

Content, Media and Carrier Types

The GMD (General Materials Designation) is replaced by three elements

Content type (core element)Media type (not an RDA core element, but

considered core by LC and OSU)Carrier type (core element)These elements are represented by MARC

fields 336, 337 and 338 respectively.

Content Type

Definition:“fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived.” (RDA 6.9)

In other words, how the content of a resource is experienced by and transmitted to the consumer.

Content Type

This is a core element

The vocabulary is “closed” or controlled

Find terms in RDA table 6.1 under rule 6.9.1.3– for example: text, two-dimensional moving

image, spoken word, computer program

MARC Coding of Content Type

Tag 336Includes the subfield $2 rdacontent to indicate the

source for this controlled vocabularyIf multiple content types are present, then the

field is repeatable• Or subfield $a can be repeated provided that both

terms are consistent with subfield $2• LC recommends repeating the entire field when

appropriate 336 _ _ text $2 rdacontent

Media Type

“Categorization reflecting the general type of intermediation device required to view, play, run, etc., the content of a resource.” (RDA 3.2.1.1)

In other words, equipment required to access the content of a resource.

Media Type

This is not an RDA core element, but is considered core by LC and OSU.

The vocabulary is “closed” or controlled Find terms in RDA table 3.1 under rule 3.2.1.3• For example: microform, video, computer• Resources that can be accessed without the use

of equipment are unmediated

Media TypeMedia type from RDA 3.1:

audio computermicroform microscopicprojected stereographicunmediated video

If the media does not match any of these descriptions, then the media type should be recorded as other.

If the media type can not be identified, then it should be recorded as unspecified.

MARC Coding of Media TypeTag 337Includes the subfield $2 rdamedia indicating the

source of the controlled vocabularyIf multiple media types are present, then the field

is repeatable• Or subfield $a can be repeated provided that both

terms are consistent with subfield $2• LC recommends repeating the entire field when

appropriate 337 _ _ unmediated $2 rdamedia

Carrier Type

“Categorization reflecting the format of the storage medium housing of a carrier in combination with the type of intermediation device required to view, play, run, etc., the content of a resource.” (RDA 3.3.1)

In other words, the format of a resource.

Carrier Type

This is a core elementThe vocabulary is “closed” or controlled Controlled vocabulary can be found in RDA

3.3.1.3• for example, audio disc, audio cassette, computer

disc, microfiche

MARC Coding of Carrier Type

Tag 338Includes the subfield $2 rdacarrier to indicate

the source for this controlled vocabularyRepeatable field• Subfield $a can be repeated provided that both

terms are consistent with subfield $2• LC guidance to repeat field

338 _ _ volume $2 rdacarrier338 _ _ audio disc $2 rdacarrier

Multiple Carrier TypesOption: (RDA 3.3.1.3) Record as many terms as are applicable to the resource being described.

Option: (RDA 3.3.1.3, 3.1.4.3)Record the predominant or most substantial carrier type, with additional units recorded in the extent statement as “various pieces.” Other important details can be provided in a note (MARC 500).

Note: If it is impractical to record the number of units then the cataloger has the option to omit this detail in the extent. However, pieces should be noted in a 500 note.

Multiple Carrier Types

Option: (RDA 3.5.1.5)

If the carriers are in a container, then the cataloger has the option to name the container and to record its dimensions in the extent.

Content, Media and Carrier types

Example:

Books, printed serials and integrating resources in print336 text $2 rdacontent337 unmediated $2 rdamedia338 volume $2 rdacarrier

Suggestion: apply these fields via constant data in Connexion

Content, Media and Carrier Types

Example:

CD-ROMs336 computer program $2 rdacontent337 computer $2 rdamedia338 computer disc $2 rdacarrier

Suggestion: apply these fields via constant data in Connexion

Content, Media and Carrier Types

Example:

DVDs336 two-dimensional moving image $2

rdacontent337 video $2 rdamedia338 video disc $2 rdacarrier

Suggestion: apply these fields via constant data in Connexion

Content, Media and Carrier Types

Example:

eBooks , online serials and online integrating resources

336 text $2 rdacontent337 computer $2 rdamedia338 online $2 rdacarrier

Suggestion: apply these fields via constant data in Connexion

Content, Media and Carrier TypesExample:

Music CDs336 performed music $2 rdacontent337 audio $2 rdamedia338 audio disc $2 rdacarrier

Suggestion: apply these fields via constant data in Connexion