Variable fields
1. Title and Statement of Responsibility
1.1 Look at the
cataloged item and describe it according to AACR2 rule. If you
have a copy, check if a title in the bib record (245 $a) is a
current iteration of a title. If not, describe the
current title in 245 $a and move the earlier title (which
you found in the bib record in 245 $a) to the field 247, or
delete the earlier title if is not considered to be important.
-----------
The rule states: 247 or 547 are used for the earlier title (only if this title is considered to be important).
Example:
245 10
$a Resources for early music $h [electronic resource]
247 10 $a Early
music resource on the Web $f <Jan. 5, 1999>
Field 247 is repeatable. Each earlier title needs the separate
247 field.
1.2. Do not transcribe introductory words not intended to be a part of the title (e.g. “Welcome to…”, “Disney presents”). Instead, give the title with these words in a note (1.1B1, 12 1.B).
Exceptions: Title with introductory words should be used in 245 if
1. The credit is within the title, rather than preceding or following it:
CBS special report
IBM close up
IBM puppet shows
2. The credit is actually a fanciful statement aping a credit
Little Roquefort in Good housekeeping
3. The credit is represented by a possessive immediately preceding the remainder of the title
Neil Simon’s Seems like old times” [1]
1.2.1 If in doubt, give the
longer form as the title proper and give a title added entry for
the shorter form.[2]
1.2.2 Nancy Olson recommends to use the 246 03 field for a note
if it is likely that a patron might search for it as a title.
Example:
246 03 $I Title on item: Welcome to NASA quest
1.2.3 If wording not likely to be searched as a title, the 500
field can be used:
Example:
500 Title appears on item as: Disney presents Sleeping Beauty[3]
1.3
Correct the obvious mistakes in the title and give
a title as it appears in a note.
Example:
241 1 Theater
meets guests
500 Title
appears on item as: Teater meets guests
1.4 Give a title appears in a full form and in form of an
acronym or initialism in the chief source of information, chose
the full form as a title proper the title if it
appears in full and abbreviated form.
Example:
245 1 Anglo-American
Cataloging Rules
246 3 AACR
1.5.1 Give
the other title information in 245 $b only if considered
important.
1.5.2 Do not transcribe
other title information that “consists solely of words relating
to the currency of the contents.”[4]Example:
245 $a Texas
rules of civil procedure
not 245
$a Texas rules of civil procedure : $b including amendments
through order of December 5, 1983, effective
April 1, 1984
1.6.1 Transcribe
editors in 245 $c only if considered important
1.6.2 If statement of responsibility is changed or deleted, give
in 245 $c the latest iteration information
1.6.3 Create a note for the earlier statement only if considered
important
1.7 Give a
source of title proper in a note (12.7B3).
Example:
245 00 Mergent
online
500 Title from title screen
(viewed on Sep.2, 2003)[5]
2.
Edition Area
2.1 Transcribe an
edition statement only if considered important.
2.2
”Edition,
revision, or release numbers that appear on a resource and that
change frequently with each new iteration, for example on the
home page of an updating online database, need not (and in most
cases should not) be recorded as edition information in area 2
(MARC 250 field).[6]
2.3 Give information of a frequency update or regular revision
in a note (field 362 1)
2.4 Some changes in edition require a new record
2.4.1 Create a new record for a remote electronic resource
only if the resource
described in the given record continues to exist separate from
the resource to be cataloged.[7] Databases
and updating Web site usually do not have numbers. So numbering
area is not applicable in database cataloging.
3.
Material-specific Details Area
3.1 Do not use
this area in the original remote electronic resource cataloging.
3.2 Except: if copy record
includes the information for area 3 (field 256, computer file
characteristics), don’t delete it[8]
3.3 If the256 field
presents in the record, and the type and/or extent of the IR
changes, change the type and extent of resource area to reflect
the current iteration; make a note if the change is considered
to be important.
4.
Publication, distribution, etc.
4.1 If
publisher and/or place of publication is changed, change the
record to reflect the current iteration (260 $a $b)
4.2 Give an earlier publisher/place of publication name in a
note if considered important.
4.3 The main rule for dates of publication (260 $c)
directs a cataloger to record the first or/and the last
iteration’s date if it is stated clearly.
4.4 If a cataloger is not sure he/she has the first or last
iteration of the resource, do not give the 260 $c ; instead give
the dates in a note;
4.5 Optional rule permit to put the dates in a square brackets
if the dates can be readily ascertained (1.4F8; 12.4F)
4.6 Date of publication Note (field 362) is used
for integrating resources with the indicator “1” only. Field
362 with 1st indicator “0” is used for serials, but not for IR.
Examples:
“A. In rare
cases
where you know you are viewing the first iteration
of an updating Web site or updating database:
Resource
has explicit statement about beginning date:
260 New York : $b Corona, $c 1997-
Resource
does not have explicit statement about beginning date:
260 New York : $b Corona, $c [199-?]-
B. In most
cases you
will not be viewing the first iteration, or in
some cases you may not know for certain:
Web site
has explicit statement about beginning date:
260 New York : $b Corona, $c [1997]-
(Brackets because the date not from 1st iteration)”
Web site does not have explicit statement about beginning
date; and has no date information or copyright date for current
year only:
260 New York : $b Corona (no date; no ending punctuation)
362 1 Began in late 1990s. (2 variants of a note)
362 1 Probably began after 2001.
Web site does not have explicit statement, but has range
of copyright dates that apply to entire resource being
cataloged, e.g.: © 1997-2003:
260 New York : $b Corona (no date; no ending punctuation)
362 1 Began in 1997? (date punctuation given in note)”
[9]
According to a new practice, a publisher’s name is given in a
full form, but older records would have a shorten name.
5.
Physical Description Area
5.1 Do not used for remote
access electronic resources (IR databases and Web Sites).[10]
6.
Series Area
Series
is not typical for updating Web Sites and databases. Cataloger
has a lot of flexibility there. He/she can supply the bracketed
information such as [new ser.] or its equivalent if the source
is a new series, but does not bear numbering (AACR2 12.6B). In
case of changes in series information, the current information
should be added and the previous can go to a note if considered
important (AACR2 12.6B2b)
If a series was added, deleted, or changed in a later iteration
a) change the
series area to reflect the current iteration (4XX-8XX);
b) make a note (field 500) with an explanation of
changes in the series if considered important (see 12.7B14.2);
retain former series entry in 8XX.
Example
440_0 $a Court
rules series
500__ $a In Federal
practice series, 1980-1990.
830_0 $a Federal
practice series[11]
Earlier series information is considered important if the series
are traced. See LCRI 21.30L for more information.
7.
Note Area
Typically, IR
record includes many notes. Some of them are mandatory, such as
the source of the title proper note, or mode of access, and some
are not (the rule says “give a note if information considered to
be important), such as information about earlier title, former
frequencies of update, etc.
Catalogers add notes to:
(a) justify an
added access point,
(b) record changes in the resource from previous iterations,
(c) emphasize a specific aspect of the resource (content, or
physical),
(d) show relationships of the resource to other resources.
Notes in AACR2 are
constructed according to Chicago Manual of Style.[12]
A typical formula is:
[introductory
word(s)]:[information]: [dates]
Clarity and consistency are most important for a notes’ quality.
Notes are given in English (LCRI 12.7A2).
|The date in angle brackets provides information about
the timing of a change for notes that do not apply to all
iterations of the resource.
Example:
500__ Edited by
John Chandler <2002->
7.0 Order of notes
Practices vary. Monograph catalogers use the order of note
prescribed by AACR2. Serial catalogers follow MARC21 order of
fields. PCC/BIBCO Manual accepts both AACR2 (prefer by
monographs catalogers) and MARC21 (prefer by serials) order of
notes for IR.
Rule also gives catalogers
flexibility to “give a particular note first when it has been
decided that note is of primary importance.”[13]
General rules for description in Note Area prescribe following order of notes (Chapter 1, excepts):
| MARC | AACR2 |
| 500 | Nature, scope, or artistic form (1.7B1) |
| 546 | Language of the item and/or translation or adaptation (1.7B2) |
| 500 | Source of title proper (1.7B3) |
| 500 | General notes arranged in the order of AACR2 areas |
| 530 | Other formats (1.7B16) |
| 520 | Summary (1.7B17) |
| 500 | Item described (1.7B23) |
|
Chapter 9 |
Chapter 12 |
||
|
MARC |
AACR2 |
MARC |
AACR2 |
|
538 |
Mode of access (9.7Bc)(12.7B1) |
310,321 |
Frequency |
|
546 |
Language & script (9.7B2) |
546 |
Language |
|
500 |
Source of title proper (9.7B3) |
500 |
Source of title proper |
|
|
|
247,547 |
Change in title proper |
|
580 |
Bib. history & relationship |
||
|
530 |
Other formats |
||
Library of
Congress issued a special LCRI 1.7B (Fall, 2003):
Prefer the order of notes as specified
in the rules unless there are mitigating circumstances that
result in a different order (e.g., a policy decision applicable
to a particular cooperative enterprise, the requirements of a
particular system, an
administrative decision not to re-order notes when doing copy
cataloging.[14]
The WSU Libraries OPAC displays notes in following order:
|
OPAC Label |
MARC21 Fields |
|
Description |
310 Frequency of update 362 1 Publication date note |
|
Electronic Resource |
856 Electronic location and access |
|
System Details |
538 Mode of access |
|
Language |
546 Language note |
|
Summary |
520 Summary note |
|
Local Note |
590 Local note |
|
Credits |
580 Linking entry complexity note |
|
Notes |
500 Source of title proper combined with item described 500 General notes (any AACR area) 504 Bibliographical note 530 Other formats available |
|
Contents |
505 Content note |
7.1 Most
important notes
Five notes
are considered the most important: frequency of update
(the 310 field), mode of access (the 538 field), source
of title proper (the 500 field), date of publication
(when no 260 $c in the record), and electronic location
and access
7.1.1 Always
include the note of frequency of update. Use the word
“updates” or “updated” [LCRI
12.7B1].
Examples:
310 Updated
weekly
310
Continually updated.
Additionally to field 310 you can use field 321 -- the
former publication frequency (either an item or an
update to an item). Field 321 is used only if a current
publication frequency is given in
field 310.
Examples:
310 Monthly, ‡b
1990-1998
321 Updated daily,
$b 1999-<2002>
Usually, if the
record has multiple 321 fields, they replaced by
Frequency varies note[16].
OCLC
Bibliographic Formats and Standards use the following
guidelines for capitalization and punctuation: the first
letter of the first word in subfield $a should be
capitalized; subfields $a and $b divides by comma; no
final punctuation needed (unless the field ends with an
abbreviation).
The 321 field is repeatable. Each former frequency
should be entered in a separate 321 field in the order
of earliest to most recent.
Existing
record:
| 245 | 00 | $a Database of prescription drugs $h [electronic resource]. |
| 260 | $a San Francisco : $b Medical College | |
| 310 | $a Updated weekly | |
| 362 | 1 | $a Began in 1999. |
| 500 | $a Title from title screen (viewed Feb. 5, 1999). |
Same record updated:
| 245 | 00 | $a Database of prescription drugs $h [electronic resource]. |
| 310 | $a Continually updated, $b <2001-> | |
| 321 | $a Updated weekly, $b 1999-<2001> | |
| 362 | 1 | $a Began in 1999. |
| 500 | $a Title from title screen (viewed May 28, 2001)[17] |
7.1.2 Always
include source of the title proper (12.7B23). The source
of the title proper note can be combined with the item
described note, given in parentheses.
Examples:
500 Title from
title screen (viewed on Sep. 15, 2002)
500 Title from HTML
header (viewed on Aug.3, 1998)
OLAC Subcommittee on Source of Title Note for Internet
Resources[18]
developed terminology[19]
for this note. Committee used terms: home page, login
screen, menu, splash screen, and title page of source
code document to describe the page. They also chose
terms for description a specific source: banner,
caption, graphic, logo, and source code.
These terms are used to describe a specific place on the Web page given in the 856 of the catalog record.
|
Banner |
See http://www.lib.uconn.edu/libraries/art/artauction.htm (Broken link 8/1/03) |
|
Caption |
|
|
Graphic |
|
|
Logo |
See http://www.wowmuseum.org/ (Broken link 2/20/03) |
|
Source Code |
See http://www.amergeog.org/theags.htm (Broken link 3/8/01) |
Committee prefers a term “homepage” to terms web
page, title screen, welcome screen, and others.
“Homepage” can include links to an “about us” or to
a “search”. It also can have a link to the homepage
of a higher corporate body. But if no homepage can
be identified, the login screen, splash screen,
menu, or title page of source code document can be
used as a source for description. See Glossary for
descriptions of the term and the Subcommittee Final
Report for more details.
7.1.3 Always
specify the mode of access.
Examples:
538
Mode of Access: Internet
538 Mode of
Access: World Wide Web
Usually do not describe system requirements for
remote access electronic resources.
7.1.4
Give Dates of publication note, if first/last
iteration is not available.
Use the 362 field with indicator 1 (unformatted
note). The 362 0 (formatted note) is not used for IR,
but for serials only.[20]
Examples:
260 __New York : $b
Corona
362 1_ Began in
late 1990s.
362 1_ Probably
began after 2001.
260 __ New York : $b Corona
362 1_ Began in
1997?
7.1.5 Always provide electronic access information.
Give in public note (subfield “z”) the local
information about restriction for access if
any. The 856 field is repeatable. If a resource
has several URIs, or a cataloger decides to
provide access to the part of a resource, add
additional the 856s.
Examples:
856 40 $u
http://www.mergentonline.com $z Click here
for online access to the database.
856 41 $u
http://purl.access.gpo.gov/GPO/LPS6143
In cases of subscribed databases, the WSU OPAC
does not display the subfield “u”. It displays a
public note only (856 $z There is no prescribed
wording for a public note. A cataloger can
create a note that is clear and short as
possible.
Examples of wording for a public note:
Click
here for online access to the database.
Search the
database (Off campus access restricted to WSU
users)
Online access to the database at Chemistry
Library only.
Current trend is to move “restriction on access”
information from the 506 field to the 856 $z
public note. But there are copies with the 506
restriction on access note (usually in general
form).
Example:
506 Access
restricted to subscribers.
506 Subscription
required.
The
general information does not very useful for
users. The 856 $z field usually provide specific
local information about restriction on access.
The restriction on access note is provisional
and wording is not prescriptive.
Examples:
816 $z Access
restricted to individuals with WSU IP addresses.
816 $z Access
available only through IP addresses on the WSU
campuses.
816 $z Access
restricted to WSU community.
Electronic access note to the government Web
sites usually include subfield “u” (URL) only.
7.1.6
In general
(not always!), give information about earlier
title proper in a note (12.7B4.2).
Use field 247 for former title proper.
Examples:
245 00 Washington
State newsstand $h [electronic resource].
247 10 Washington
newspapers database $f <viewed on Aug. 6, 1999>
The right choice of indicators is important,
when you use the 247 field.
The 1st indicator defines if title added entry
would be made:
0 – no title added entry
1-- title added
entry
The 2nd indicator is a note controller.
0 –
display note
1 – do not display
note
The 2nd indicator value 1 is chosen in cases when the additional 547 note is made.
The 547 field -- title history note – is used in
complex cases when 247 information is not
enough.
Example:
247 1 1 Printing
trades blue book. $p New York edition $f 1916
547 Edition varies:
1916, New York edition.
LCRI directs to use separate 547 note in addition to the 247 field only if the situation requires more explanation than can be given in the 247 field. Do not give a 547 field just because there are multiple 247 fields.
7.2 Notes required cataloging decision
7.2.1
AACR2 directs a cataloger to include all notes
describing changes to all areas of AACR2 that
considered important.
247 Former title proper (12.7B4.2b)
Examples:
245 00 Mergent
online
247 10 FIS online
$f <June 18, 1998
247 10 Moody’s
company data
321 Past frequencies of updates
Examples
310 Updated
monthly, $b 2002--
321 Updated
quarterly, $b 2000-2002
500 -- Titles (12.7B4.1) and statement of
responsibility (12.7B7.2b)
500 – Change in edition information
(12.7B9.2b)
500 -- Change in publication, distribution,
etc. (12.7B11.2b)
500 -- Changes in Series (12.7B14.2b)
7.2.2 The other notes
516 -- Type of electronic resource – does not
display in the OPAC Do not use this note in
original cataloging, but accept it in a copy
(9.7B1a)
Examples:
516 Searchable Web
site.
516 Text (HTML and
PDF), image (GIF, JPG, and RPM), sound (RAM),
and search engine
516
Text (article citations, abstracts, and
full-text articles)
530 -- Another physical format available
(12.7B8)
Examples:
530 Online version
of: America, history and life.
530 Issued also in
a CD-ROM version.
530 Also available
in paper format.
520 -- Summary or abstract includes short
description of IR content.
Example:
520 Online
directory of contact and basic financial
information on over 12 million businesses in the
United States. Search by company name,
geographic area, business type, SIC and NAICS
codes, yellow page listing, revenue, location,
number of employees or any combination of the
above.
550 -- Issuing body notes, such as former
issuing body.
“A
note referring to current and former issuing
bodies, including notes containing compiling,
editing or translating information that involves
an issuing body. Use field 550 also for notes
denoting the item as an official organ of a
society, etc.
Use
for issuing bodies traced in a 7xx added entry
field (7xx
fields). The field explains their
relationship to the publication and justifies
the 7xx added entry.“[21]
Examples:
245 00 Occasional
newsletter $h [electronic resource] / ALRA
550 __ Issued by:
Abortion Law Reform Association
710 2_ Abortion
Law Reform Association
550 __ Issued by: Association of Research
Libraries, <1996>
550 __ Hosted by:
University of Michigan.
550 __ Published in
cooperation with the Blanton-Peale Institute.
550 __ Official
publication of the Henry James Society;
digitized and made available Project Muse.
580 – Linking entry complexity note.
Used together with linking entry.[22]
Example:
580 __ Continues print publication: America,
history and life.
771 10 $t America,
history and life (Santa Barbara, Calif., 1989) ‚
$w (DLC) 89659058 $w (OCoLC)19247941
590 – Local note
Voyager OPAC displays a separate label for a local note
to show its importance. Electronic serials
records have the 590 fields with wording
“electronic journal”. To be consistent, records
of Web sites and databases should include
similar information to a local note. It helps
users to distinguish different types of
electronic resources.
Examples:
590__
Subscribed electronic
database
online.
590__Updated Web site.
A
local note can be used also for local
accessibility information.
Example:
590__
This database accessible through library’s Web
site.
590__ Item accessible in Chemistry library only.
590__Also available
on Sociology Subject Pages (http://library.wichita.edu/socsci/)
There is also suggestion to use the 936 local field for record maintenance purposes (see p. 38-40 for details).
[1] See LCRI 7.1B1.
[2] LC Cataloging Service Bulletin, no.100, Spring 2003, p.17).
[3] Olson, Nancy. Some changes hidden in AACR2 Amendments 2002. In: OLAC Newsletter, vol.23, no.2, June 2003
[4] 12.1E1b
[5] See p. 27-28 for more details on the source of title.
[6] Online Audiovisual Catalogers. Cataloging Policy Committee. Introduction to Cataloging Electronic Integrating Resources. An online training presentation, c2003, note to a slide 34. http://www.olacinc.org/capc/ir.ppt
[7] Ibidem, slide 36.
[8] This is LC policy and practice.
[9] Online Audiovisual Catalogers. Cataloging Policy Committee. Introduction to Cataloging Electronic Integrating Resources. An online training presentation, c2003, note to a slide 45-46. http://www.olacinc.org/capc/ir.ppt
[10] It is used for loose-leafs.
[11] PCC/BIBCO Participant’s manual. Appendix A: 1-8 p.1.
[12] The Chicago manual of style. (1993)14th ed. Chicago.: Univ. of Chicago Press, p. 494-517.
[13] AACR2 2002 ed. 1-39 (1.7B).
[15] PCC/BIBCO participants’ manual. Appendix A. Cataloging integrating resources. I-10 p. http://www.loc.gov/catdir/pcc/bibco/irman.pdf
[16] OCLC Bibliographic Formats and Standards. Field 321. 3rd ed.
[17] Introduction to Cataloging Electronic Integrating Resources. An Online Training Presentation From the Cataloging Policy Committee (CAPC) of the Online Audiovisual Catalogers, Inc, 2003.
[18] OLAC. Subcommittee on Source of Title Note for Internet Resources (Final report). January 8, 2001. by http://ublib.buffalo.edu/libraries/units/cts/olac/capc/stnir.html
[19] See Glossary of the manual.
[20] See: Cataloging electronic resources: a prototype PCC training resource. Rev. of a training workshop given at LC on May, 2002 by Steven Jack Miller, slide 38. http://www.loc.gov/catdir/pcc/bibco/irtrng702_files/v3_document.htm
[21] OCLC bibliographic formats and standards. 3rd ed. http://www.oclc.org/bibformats/en/5xx/550.shtm
[22] See details in OCLC bibliographic formats and standards. http://www.oclc.org/bibformats/en/5xx/580.shtm
