Online Quiz on FRBR, RDA Terminology, and Structure of RDA

• Online Graded Quiz – 15 minutes

• Multiple Choice
• True/False
• Graded results at end of quiz
• Instructor will guide you through the first question

1
 RDA Chapters for this Module
• This module mainly covers the identification of
manifestations and items.
• It does not cover the identification of works and
expressions (except for 336, 300 $a duration and
$b), nor the recording of authorized access points
or relationships. Those topics will be covered in
subsequent modules.

2
 RDA Chapters for this Module
• Chapter 2: Identifying manifestations and items
• Chapter 3: Describing carriers
• Chapter 7: Describing content
• Some elements of works & expressions, but covered
here due to MARC coding for these elements
• A few elements from Chapter 4 and Chapter 6

• Primary focus on: LC core elements

3
 Elements; notes on elements

• RDA instructions on elements may refer to giving

notes or giving “details on” (latter are notes in MARC)

• RDA instructions on notes are near the ends of the

chapters but “details on” instructions are with
elements

4
Core Elements from Chapter 2:
“Identifying Manifestations
and Items”

5
 Title and Statement of Responsibility
(RDA 2.3 – 2.4)

• Title proper
• Parallel title proper
• Other title information
• Statement of responsibility

6
 Title Proper

• LC 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: RDA 2.2.2-2.2.3
• If no title within the resource: RDA 2.2.4

• MARC 245 $a $n $p
7
 Title Proper Transcription

• General guidelines on titles (RDA 2.2.1)

• Principle of representation (RDA 2.3.1.4)
• Don’t correct errors for monographs = no more “[sic]”
or “[i.e., ____]” – give note to explain
• Do correct errors for serials and integrating resources
to have a stable title

• Changes in title proper: RDA 2.3.2.12-2.3.2.13 - same as

AACR2

8
 Examples:
Error in Title Proper

RDA record for a monograph:

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

AACR2 record for a monograph:

245 $a Teusday’s [i.e. Tuesday’s] tasks

RDA record for a serial:

245 $a Zoology studies
246 $i Misspelled title on number 1:
$a Zooology studies
9
 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

10
 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
11
 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

12
 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

13
 Earlier and Later Titles 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

14
 Statement of Responsibility
Relating to Title Proper - Scope

• LC 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

15
 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

16
 Statement of Responsibility Relating
to Title Proper - Transcription

• Transcribe a statement of responsibility in the form in which it appears

on the source of information (follow general guideline in 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.

17
 Statement of Responsibility Relating to Title
Proper - Transcription

• LCPS: “Generally do not omit names in a statement of

responsibility.”

“Rule of Three” -- Change from AACR2!

Source: by Susan Brown, Melanie Carlson, Stephen

Lindell, Kevin Ott, and Janet Wilson.
RDA allows: 245 $a … / $c by Susan Brown [and four
others].
RDA/LCPS: 245 $a … / $c by Susan Brown, Melanie
Carlson, Stephen Lindell, Kevin
Ott, and Janet Wilson.

AACR2: 245 $a … / $c by Susan Brown … [et al.].

18
 If Multiple Statements ...

• Record 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 identifying creators of intellectual or artistic content
(RDA 2.4.2.3)
• Only first recorded is required

On source: “introduction by ______”

“written by _____”

If only transcribing one in 245 $c, give

“written by _____”
19
 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
20
 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 edition

AACR2: 250 $a 3rd rev. ed.
RDA: 250 $a Third revised edition

Source: 2nd enlarged ed., revised

AACR2: 250 $a 2nd enl. ed., rev.
RDA: 250 $a 2nd enlarged ed., revised
21
 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

22
 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 23
 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 0# $a Volume X, number 1-

362 1# $a Began with January 2010 issue.

24
 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

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

26
 Publication Statement

• CORE ELEMENTS for published resources

• RDA 2.8
• Scope – “a statement identifying the place or places of
publication, publisher or publishers, and date or dates of
publication of a resource”

• MARC field 264, second indicator 1

• Choosing sources for CIP material

27
 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
28
 More Than One Place of Publication

• If more than one, only the first is required

• No “home country” provision

• No need to look for a place in the U.S.

29
 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

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

31
 Examples:
Supplying Place

Known local place: [Toronto]

Probable local place:[Munich?]

[Göteborg?, Sweden]

Known country, state, etc.: [Canada]

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

32
 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

33
 Examples: Place of Publication

On resource: London -- New York – Boston

264 #1 $a London or
264 #1 $a London ; $a New York ; $a Boston

264 #1 $a Red Oak [Iowa]

(addition OK, but not required)

264 #1 $a [Place of publication not identified]

(Generally no! LCPS says to supply a place if
you can, even if just country)

264 #1 $a Minneapolis
500 $a Actually published in St. Paul.
34
 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

35
 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

36
 Publisher’s Name in
More Than One Language

o If the name of a publisher appears in more than

one language or script, record the form that is in
the language or script of the title proper

37
 Publisher’s Name not Identified

• If no publisher identified within the resource or

from other sources, give “[publisher not
identified]” – not “[s.n.]”

38
 Examples:
Publisher’s Name
264 #1 $a New York : $b J.J. Wilson Publishing
Company

Not: 264 #1 $b Wilson Pub. Co.

Source: Humanities Association, Literature

Division, Renaissance Literature Section
264 #1 $a Chicago : $b Humanities Association,
Literature Division, Renaissance Literature
Section

Source: Toronto -- Pilkington Pub. Co.

Houston -- Davidson Publishers
264 #1 $a Toronto : $b Pilkington Pub. Co.

264 #1 $b [publisher not identified] 39

 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
40
 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-

41
 Multipart Monographs, Serials,
and Integrating Resources

• Record the dates of publication of those issues, parts, or

iterations, separated by a hyphen, if publication of the
resource has ceased or is complete and the first and last
issues, parts, or iterations are available.
1968-1973
• Record the publication date of the last issue, part, or
iteration, preceded by a hyphen, if publication of the
resource has ceased or is complete and the last issue, part,
or iteration is available, but not the first.

-1977

42
 Multipart Monographs, Serials,
and Integrating Resources

• For an integrating resource, supply the date of the last

update if it is considered to be important.
1995–1998 [updated 1999]
• If the date of publication is the same for all issues,
parts, or iterations, record only that date as the single
date.

1997

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

[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]
• If the date or dates cannot be approximated, do not record
a date of publication.

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

45
 Examples:
Supplying Dates
Title page verso: Copyright ©2009
Prefaced signed: June 2009
Date of publication: not given
Transcription: 264 #1 $a … $b … $c [2009]
008/06: s
008/07-10: 2009
008/11-14: ####

Title page verso: ©2009

Item received in: 2008
Date of publication: not given
Transcription: 264 #1 $a … $b … $c [2009]
optionally: 264 #4 $c ©2009
008/06: t
008/07-10: 2008
008/11-14: 2009 46
 Examples:
Supplying Dates
Title page verso: ©1980//1980 printing
Date of publication: not given
Transcription: 264 #1 $a … $b … $c [1980]
008/06: s
008/07-10: 1980
008/11-14: ####

Title page verso: ©1978//Sixth Printing 1980

Prefaced signed: June 1978
Date of publication:not given
Transcription: 264 #1 $a … $b … $c [1978]
optionally: 264 #3 $a … $b … $c 1980.
588 ## $a Description based on sixth
printing, 1980.
008/06: s
008/07-10: 1978
008/11-14: ####
47
 Examples:
Supplying Dates
Title page verso: Distributed 2008
Bibliography includes citations to 2007 publications
Date of publication: not given
Transcription: 264 #1 $a London :$b Gay Mens Press, $c
[2008]
optionally: also give 264 #2 $a Chicago, IL : Distributed
in North America by InBook/LPC Group, $c 2008
008/06: s
008/07-10: 2008
008/11-14: ####

Title page verso: Distributed in the USA in 1999

Prefaced signed: London, January 1993
Date of publication:not given
Transcription: 264 #1 $a … :$b … $c [between 1993 and 1999]
008/06: q
008/07-10: 1993
008/11-14: 1999 48
 Examples:
Supplying Dates
Title page verso: First Printing 1980
Date of publication: not given
Transcription: 264 #1 $a … :$b … $c [1980]
008/06: s
008/07-10: 1980
008/11-14: ####
Title page verso: 15th Impression 1980
Date of publication: not given
Transcription: 264 #1 $a … :$b … $c [not
after 1980]
optionally: 588 ## $a Description based
on 15th impression,
1980.
008/06: q
008/07-10: uuuu
008/11-14: 1980 49
 Supplying Dates –
5 Categories in RDA 1.9

1. Actual year known

264 $c [2010]

2. Either one of two consecutive years

264 $c [2009 or 2010]

3. Probable year
264 $c [2010?]

4. Probable range of years (“between ___ and ___?”)

264 $c [between 2008 and 2010?]

5. Earliest and/or latest possible date known (“not

before,” “not after,” or “between ___ and ___”)
264 $c [not before January 15, 2010]

50
 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 If you cannot supply this data

• 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

51
 Examples:
Supplying Publication Data

On source: ABC Publishers, 2009

Distributed by Iverson Company,
Seattle

RDA: 264 #1 $a [Place of publication not

identified] : $b ABC Publishers, $c 2009.
264 #2 $a Seattle : $b distributed by
Iverson Company, $c [2009]

LC-Recommended: 264 #1 $a [Seattle?] : $b

ABC Publishers, $c 2009.

52
 Examples:
Supplying Publication Data

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

53
 Examples:
Supplying Publication Data

• Sometimes, distribution information must be

provided

On jewel box: Published in 2010 in

Providence; distributed in
Boston and Ottawa by KL,
Inc.
RDA and LC:
264 #1 $a Providence :$b [publisher not
identified], $c 2010.
264 #2 $a Boston ; $a Ottawa : $b KL,
Inc., $c [2010]
54
 Recording Distribution Information

• CORE ELEMENTS 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, given a complete
distribution statement
• Generally do not omit levels in corporate
hierarchy

55
 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
56
 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.

Examples: 264 #4 $c ©2002

264 #4 $c ℗1983
57
 Series, Mode of Issuance,
and Frequency

• Series Statement - RDA 2.12

• Mode of Issuance – RDA 2.13

• Frequency – RDA 2.14

58
 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 no longer trace series; no

authorized access points are made for series

59
 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

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

61
 Title Proper of Series and
… of Subseries

• LC CORE ELEMENT

• RDA 2.12.2 & 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

62
 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-22
490 0# $3 volume 2: $a Baroque musical studies ;$v 2
Note: Volumes of multipart monograph are in different
series
63
 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

64
 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

65
 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

66
 ISSN of Series and Subseries

• LC CORE ELEMENT
• RDA 2.12.8, 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

490 $a Title of main series, $x ISSN of

main series. $a Title of subseries,
$x ISSN of subseries

67
 Numbering Within Series and … Within
Subseries

• LC CORE ELEMENT

• RDA 2.12.9, 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

68
 Mode of Issuance

• LC CORE ELEMENT
• RDA 2.13
• MARC Leader: Bibliographic Level
• “m” for both “single unit” and “multipart
monograph”
• “s” for “serial”
• “i” for “integrating resource”

69
 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

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

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

72
 Recording Identifier for the Manifestation

• Record in accordance with which there is a 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: Record ISBNs in 020 $z if they clearly 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

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

74
 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

75
 Note on Title

• LC CORE ELEMENT
• Always give this note in a CONSER Standard Record
• RDA 2.20.2
• If earlier title is removed due to reformatting of an
electronic serial, update the existing record

Existing record:
245 00 $a Legal medicine open file
Same record updated:
245 00 $a Legal medicine
247 11 $a Legal medicine open file
547 ## $a Issues published from 1992-1996 with
the title Legal medicine open file have been
reformatted with the new title: Legal medicine
76
 Note on Issue, Part Used as
Basis for Identification

• LC CORE ELEMENT
• Always give this note in a CONSER Standard Record
• RDA 2.20.13

• Multipart monographs and serials: if not based on first issue

or part (LCPS 2.20.13.3)
• Integrating resources: latest iteration consulted
• Any online resource: date resource viewed

• MARC 588 field

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

588 ## $a Identification of the resource

based on: part 2, published 1998.

588 ## $a Identification of the resource

based on version consulted: Oct. 26, 2000.

588 ## $a Viewed on Jan. 13, 2000.

78
 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

79
 Unit 5: Describing Carriers

o RDA Chapter 3
o Will not discuss specific elements for resources
of special format (films, maps, scores, etc.)
• Examples available in RDA, in MARC
documentation, and in LC compilation of
examples

80
 Replacement for GMD - 245 $h

• Three new MARC fields - developed with ONIX

publishing community:

• Content type -- RDA 6.9 -- MARC 336 field

• Media type -- RDA 3.2 -- MARC 337 field
• Carrier type -- RDA 3.3 -- MARC 338 field

81
 MARC for Content, Media, Carrier

• In each of the three fields for these elements (336-338):

• $a: term
• $b: code
• $2: “rdacontent” or “rdamedia” or
“rdacarrier” as appropriate
• $3: materials specified - give if
appropriate

82
 Controlled Vocabularies for
Content, Media, Carrier Types

• Closed lists in RDA 6.9.1.3, 3.2.1.3, 3.3.1.3

• If more than one term appropriate, two choices:
• Give all: repeat subfield $a or repeat field
• Pick term representing the predominant or most
substantial content, media, carrier
• If the information is unknown, record “unspecified”
• If no term appropriate, give “other” and notify LC via a
message to LChelp4rda@loc.gov

83
 Content Type

• LC CORE ELEMENT
• RDA 6.9
• “Fundamental form of communication in which the content is
expressed and the human sense through which it is intended to
be perceived”
• Terms from Table 6.1
• Instead of recording all, you may record the content type that
applies to the predominant part of the resource or to the most
substantial parts of the resource
• MARC 336 field

Examples: performed music, still image,

text

84
 Media Type
• LC CORE ELEMENT
• RDA 3.2
• “A categorization reflecting the general type of
intermediation device required to view, play, run, etc., the
content of a resource”
• Table 3.1
• Instead of recording all, may record the media type that
applies to the predominant part of the resource or to the
most substantial parts of the resource
• MARC 337 field

Examples: audio, computer, microform,

unmediated, and video
85
 Carrier Type

• LC CORE ELEMENT
• RDA 3.3
• “A categorization reflecting the format of the storage medium
and housing of a carrier in combination with the type of
intermediation device required to view, play, run, etc., the
content of a resource”
• Terms listed in 3.3.1.3
• Instead of recording all, may record the carrier type that applies
to the predominant or most substantial parts of the resource
• Don’t confuse with term used in Extent (MARC 300 $a): some
terms in common
Examples: audio disc, computer disc,
microfiche, volume, videodisc

86
 Example:
MARC 336-338 Fields

Book:
336 $a text $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier

87
 Voyager Templates:
MARC 336 - 338 Fields

88
 Extent

• LC CORE ELEMENT
• RDA 3.4
• “The number and type of units and/or subunits making
up a resource”
• Unit = a physical or logical constituent of a resource
(e.g., a volume)
• Subunit = a physical or logical subdivision of a unit
(e.g., a page of a volume)

• MARC 300 $a

89
 Recording Extent

• Give if the resource is complete or if the total extent is

known
• RDA 3.4.1.3
• Give number of units and appropriate term:
• Sometimes a term from carrier type list (RDA 3.3.1.3)
• Another term to designate the type of unit (RDA 3.4.1.5)
if term not in list or prefer a term in common use
• Several categories covered by exceptions (e.g., text, still
images, notated music, cartographic resources)
• MARC field 300

90
 Extent of Text

• Single Volume with Numbered Pages, Leaves, or

Columns (3.4.5.2)
• Single Volume with Unnumbered Pages, Leaves, or
Columns (3.4.5.3)
• RDA lists three options
• LCPS 3.4.5.3 continues AACR2 practice
• For LC original cataloging, usually follow method c) 1
volume (unpaged)
• Complicated or Irregular Paging (3.4.5.8)
• RDA lists three options
• LCPS 3.4.5.3 continues AACR2 practice
• For LC original cataloging, usually follow method c) 1
volume (various pagings)
91
 Changes From AACR2
Related to Extent
• Do not use abbreviations for terms (e.g., “pages,”
“volumes”, not “p.,” “v.”)
• Use “approximately” (rather than “ca.”) and “that is”
(rather than “i.e.”)
• Use “unnumbered”, rather than square brackets
enclosing the numeral
• Be aware of changes in vocabulary from AACR2, e.g.:
“computer disc” is used for both “computer disk” and
“computer optical disc”

92
 Dimensions

• LC CORE for resources other than serials and online

electronic resources
• RDA 3.5
• “Measurements of the carrier or carriers and/or the
container of a resource”

• Use centimetres/millimetres for others (“cm” and “mm”

are symbols, not abbreviations) - use ISBD full stop after
symbol only if 490 in record

• MARC 300 $c

93
 LC Practices: Dimensions

• LC practice for Alternative:

• Use inches for discs (RDA 3.5.1.4.4) and for all audio
carriers; otherwise, follow the RDA instruction as
written
• LC Practice for serials:
• Note that dimensions is not a Core Element for
serials and online resources. But you may record it if
you wish

94
 Examples:
MARC 300 $a, 336-338

Book:
300 $a 123 pages, 28 unnumbered pages
336 $a text $b txt $2 rdacontent
337 $a unmediated $b n $2 rdamedia
338 $a volume $b nc $2 rdacarrier

Music CD:
300 $a 1 audio disc {or: 1 CD}
336 $a performed music $2 rdacontent
337 $a audio $2 rdamedia
338 $a audio disc $2 rdacarrier

95
 Examples:
MARC 300 $a, 336-338

DVD:
300 $a 1 DVD {or: 1 videodisc}
336 $a two-dimensional moving image $2
rdacontent
337 $a video $2 rdamedia
338 $a videodisc $2 rdacarrier

Online PDF:
300 $a 1 online resource (39 pages)
336 $a text $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier

96
 Example:
MARC 300 $a, 336-338

Website (with maps, text, and photographs):

300 $a 1 online resource
336 $a text $2 rdacontent
336 $a cartographic image $2 rdacontent
336 $a still image $2 rdacontent
337 $a computer $2 rdamedia
338 $a online resource $2 rdacarrier
Note: If copied records include repeated
subfields $a, rather than multiple fields, you
can accept these fields as is:

336 $a text $a cartographic image $a still image $2 rdacontent

97
 Example:
MARC 300 $a, 336-338
Book with accompanying CD of lecture: $3 and $e
300 $a 244 pages ... + $e 1 CD
336 $3 book $a text $2 rdacontent
336 $3 CD $a spoken word $2 rdacontent
337 $3 book $a unmediated $2 rdamedia
337 $3 CD $a audio $2 rdamedia
338 $3 book $a volume $2 rdacarrier
338 $3 CD $ audio disc $2 rdacarrier
* The use of $3 in this example is optional.

Instead of $e, can repeat 300 field

300 $a 244 pages ...
300 $a 1 CD ...

Instead of $e, can give a note

500 $a Accompanied by a CD. 98
 Examples:
MARC 300 $a, 336-338
Oral history CD:
300 $a 1 CD
336 $a spoken word $2 rdacontent
337 $a audio $2 rdamedia
338 $a audio disc $2 rdacarrier

Playaway audiobook:
300 $a 1 Playaway (or 1 audio media player
or 1 digital media player)
336 $a spoken word $2 rdacontent
337 $a audio $2 rdamedia
338 $a other $2 rdacarrier

99
 Example:
MARC 300 $a, 336-338

Kit (contains a book about a fireman, a CD narrating the

book, and a fireman’s hat):
300 $a 1 CD, 1 book, 1 plastic helmet
336 $a spoken word $a text $a three-
dimensional form $2 rdacontent
337 $a audio $a unmediated $2 rdamedia
338 $a audio disc $a volume $a object
$2 rdacarrier

* The use of multiple subfields $a in the 336 field is acceptable if this is a

copied record

100
 Examples:
MARC 300 $a, 336-338

Score:
300 $a 1 vocal score (xii, 300 pages)
336 $a notated music $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a volume $2 rdacarrier

Map:
300 $a 1 map
336 $a cartographic image $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a sheet $2 rdacarrier

101
 Expression Attributes
Covered in this Module

• RDA Chapter 7

• Recorded in MARC 300 field

• Duration
• Illustrative Content
• Colour Content

102
 Duration

• LC CORE ELEMENT
• RDA 7.22
• “Playing time, running time, etc., of the content of a
resource”
• MARC 300 $a
• Use abbreviations per RDA Appendix B

Examples:
300 $a 1 audio disc (45 min.)
300 $a 1 DVD (2 hr., 15 min.)

103
 Illustrative Content

• LC CORE ELEMENT for resources intended for

children

• RDA 7.15

• Open list of vocabulary terms

• Recorded in MARC 008/18 as applicable and

field 300 $b

104
 A Key Change From AACR2

• No abbreviations
• “color” (not “col.”)
• “sound” (not “sd.”)
• “silent” (not “si.”)
• “illustrations” (not “ill.”)

105
 Colour Content

• Not LC CORE

• RDA 7.17

• LCPS 7.17.1.3
• Use spelling “color”

• MARC field 300 $b

Examples:
color (illustrations are in color)
some color (10 maps, some of which are in color)
chiefly color (illustrations, most of which are in color)
106
Unit 6: Other Elements of Manifestations and
Items
Providing Acquisition and Access Information

• Terms of availability (RDA 4.2)

• Contact information (RDA 4.3)
• Restrictions on access (RDA 4.4)
• Restrictions on use (RDA 4.5)
• Uniform Resource Locator (RDA 4.6)

107
 Terms of Availability

• RDA 4.2
• LCPS: Generally do not provide prices or other
availability information except for rental scores
or rental performance materials

Example:

020 $a 0460044524 : $c Rental material

108
 Contact Information
• RDA 4.3
• Record contact information for a publisher, distributor,
etc., if it is considered to be important for acquisition or
access

Example:

http://www.HaworthPress.com

Alabama Department of Archives and

History. 624 Washington Avenue,
Montgomery, AL 36130-0100
109
 Restrictions on Access
• RDA 4.4
• Record all restrictions on access to the resource,
including the nature and duration of the restriction, as
specifically as possible. The absence of restrictions may
also be noted if it is considered to be important

Example:

Access restricted to subscribers via

a username and password or IP address
authentication

110
 Restrictions on Use
• RDA 4.5
• LCPS: The CORE requirement is limited to the non-General
Collections at the Library of Congress

• MARC field 540

Example:

This film is restricted to classroom use

111
 Uniform Resource Locator

• LC CORE ELEMENT
• RDA 4.6
• Address of the remote access resource being cataloged
• Not in AACR2 although information is included in AACR2
records
• LCPS 4.2.1.3 -If there is more than one Uniform Resource
Locator for the resource, record all
• MARC 856 field

112
 Uniform Resource Locator

• Changes Requiring the Addition, Revision, or

Deletion of a Uniform Resource Locator
• LCPS 4.6.1.4 provides LC practice for two
situations:
• When the original URI is no longer active
• When the original URI is still active, but the original
resource is no longer available

113
 Other Characteristics

• Sound resources
• Type of recording - 3.16.2.3
• Recording medium - 3.16.3.3
• Playing speed - 3.16.4.3
• Groove characteristic - 3.16.5.3
• Track configuration - 3.16.6.3
• Tape configuration - 3.16.7.3
• Configuration of playback channels - 3.16.8.3
• Special playback characteristics - 3.16.9.3

114
 Other Characteristics

• Moving image resources

• Presentation format (film) - 3.17.2
• Projection speed (film) - 3.17.3
• Video format (videorecording) - 3.18.2
• Broadcast standard (videorecording) - 3.17.2
• Regional encoding (videorecording)

115
 Other Characteristics

• Electronic resources (digital files)

• File type - 3.19.2
• Encoding format - 3.19.3
• File size - 3.19.4
• Resolution - 3.19.5
• Regional encoding - 3.19.6
• Transmission speed - 3.19.7
• Date resource viewed - 2.20.13.5
• Equipment or system requirement – 3.20

116
 Other Characteristics

• Cartographic resources
• Layout - 3.11
• Digital file characteristics – 3.19
• Longitude and latitude – 7.4.2
• Horizontal scale – 7.25.3
• Vertical scale – 7.25.4
• Additional scale information – 7.25.5
• Projection of cartographic content – 7.26

117
 Other Characteristics

• Music resources
• Form of musical notation (scores) - 7.13.3
• Format of notated music (scores) - 7.20
• Medium of performance of musical content - 7.21

118
 Unit 7: Exercises and Practice
on Manifestations

• Exercise #1-2 Identifying

Manifestations

119
 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/staff/idt/training_documents/rda/rdat
raining.html

120