----------------------------Original message----------------------------
FORMAT INTEGRATION:
CODING OF ATLASES IN THE BIBLIOGRAPHIC FORMAT
This paper addresses the question as to whether, with format
integration, atlases should be coded using the maps
specifications rather than using the books and serials
specifications. If you have any comments regarding this issue,
could you send them to the following person by AUGUST 31, 1993?
Phyllis Bruns
Network Development and MARC Standards Office
Library of Congress
Washington, DC 20540-4020
FAX: (202) 707-6269
EMAIL: (internet) [log in to unmask]
1. BACKGROUND
An atlas, as defined by AACR 2, is "A volume of maps,
plates, engravings, tables, etc., with or without
descriptive text."
2. CURRENT SITUATION
On p. 2 of the Introduction to the "USMARC Format for
Bibliographic Data," it states
Printed map
Manuscript map
A bibliographic record for maps (printed, in
manuscript, or a microform), atlases, globes, and
other types of cartographic material. This type
of record is created using the MP specifications.
Although atlases are included in the above descrption, in
actual practice, institutions are NOT using the maps
specifications for atlases. Instead, the books and serials
specifications are being use, depending on how the atlas is
issued. This means that in USMARC records:
Leader/06 (Type of record): a (Language mateial)
Leader/07 (Bibliographic level): m (Monograph) or s
(Serial)
008 (Fixed-Length Data Elements): either books or
serials
No 007 Physical Description Field
034 (Coded Mathematical Data)
255 (Mathematical Data Area)
Perhaps this practice of MARC coding such items as books (or
serials) came about because the atlases are bound as books.
At LC, atlases were fully cataloged for printed cards prior
to MARC; when MARC came into being, the data was captured,
MARC coded using the books specifications, and input into
the books file.
Today, at the Library of Congress, atlases (i.e., those
items classed in G1000-G3122) are cataloged in the Geography
and Map Division if they are monographs; however, the data
is MARC coded as books and input into the books file.
Atlases that are serials are cataloged by the Serial Record
Division, are MARC coded as serials, and are input into the
serials file on OCLC.
3. Possible Change with Format Integration
QUESTION: With format integration, should atlases be coded
using the maps specifications?
There are two considerations:
a. See Attachment A for the General Model to be followed
with format integration. The argument has been
raised that since atlases are not basically textual
that the specifications for "items that are not
basically textual" on the general model should be
followed. This change would mean that in USMARC
records:
Leader/06 (Type of record): e (Printed map)
Leader/07 (Bibliographic level): m (Monograph)
or s (Serial)
008 (Fixed-Length Data Elements): maps
A 007 (Physical Description Fixed Field) - There
could be a maps 007 field if a code value for
atlases is defined for 007/01 (Specific
Material Characteristics)
034 (Coded Mathematical Data)
255 (Mathematical Data Area)
Optionally, one could use the books 006 (Fixed-Length
Data Elements-Additional Material Characteristics)
field if an atlas is a monograph. Optionally one could
use the serials 006 field (and also the books 006) if
an atlas is issued serially.
Note that institutions are currently cataloging and
inputting serially-issued maps using the maps
specifications. Leader/06 (Type of record) contains
code e (Printed map). Leader/07 (Bibliographic level)
contains code s (Serial). The maps 007 field is used.
The maps 008 field is used; code m (Multiple dates) is
used in 008/06 (Type of date). Fields 034 (Coded
Mathematical Data) and 255 (Mathematical Data Area) are
present. With format integration, 008/06 will be coded
with one of the serial codes c (Serial item currently
published), d (Serial item ceased publication), or u
(Serial item status unknown).
b. Having atlases coded as maps could ensure that all
cartographic materials are available in one file. Most
cartographic collections have maps, globes, and atlases
housed together in the same physical unit; thus, it
would make sense to have the records for such entities
in the same file. A user would not have to search
maps, books, and serials files to locate all necessary
cartographic materials.
Additional comments:
- If atlases are to be USMARC coded using the maps
specifications, then it should be clarified that only
"geographical" atlases are to be coded using such
specifications.
- If atlases are to be USMARC coded using the maps
specifications, then there would be a code defined for
atlases in character position 25 (Cartographic
materials type) in the maps 008 Fixed-Length Data
Elements field. Perhaps a code for digital should also
be defined. The description of 008/25 would need to be
changed slightly to read: A one-character alphabetic
code indicates the type of cartographic item being
described.
- According to Hugo L.P. Stibbe, at the National
Archives of Canada, all Canadian map collections he is
familiar with catalog atlases as cartographic material,
using the cartographic material chapter rather than
the book chapter of AACR 2. Coding is therefore for
cartographic materials. However, some Canadian
libraries which do not have separate map collections
(and these may well include most public libraries) may
describe atlases as books but as far as he knows would
still classify them in Class "G" for atlases, He is
not sure what their practice would be in the encoding;
the records may well be coded as monographs in these
cases. Many of these libraries catalog atlases as
monographs because they do not know how to handle scale
information; however, for atlases the scale information
is usually "scale varies." Mr. Stibbe has never heard
of any Canadian library using the serials
specifications to catalog atlases and then code them as
a serial. In the map collection of the National
Archives of Canada, if serial characteristics are
needed in cataloging atlases, those characteristics
would simply be imported and used from the serials
chapter, e.g., a Numeric and/or Alphabetic,
Chronological, or other Designation Area in addition to
a Mathematical Data Area. (The special areas of
description are repeated.)
ATTACHMENT A
Model
Beginning with the implementation of format integration, the
following model is to be used to determine data to be included in
a record:
If an item is basically textual:
Leader/06 - code for language material, manuscript language
material, or mixed material
Leader/07 - code for monograph, serial, collection, etc.
008 - book or serial (depending on Leader 06/07 codes) or
archival and manuscripts control
006 - music, map, visual material, computer file, serial (as
needed)
Variable fields - any applicable to the form or control of
the item.
If an item is NOT basically textual:
Leader/06 - code for printed music, manuscript music,
printed map, manuscript map, projected medium,
two-dimensional nonprojectable graphic, nonmusical sound
recording, musical sound recording, computer file, kit,
or three-dimensional artifact or naturally occurring
object
Leader/07 - code for monograph, serials, collection, etc.
008 - music, map, visual material, or computer file
006 - serial, archival and manuscripts control, map, visual
material, computer file (as needed)
Variable fields - any applicable to the form or control of
the item
(See "Format Integration and its Effect on the USMARC
Bibliographic Format" for a more complete description of the
model.)
================================================================
submitted to MAPS-L by Betsy Mangan
|
