Date: Sun, 25 Sep 1994 16:10:00 -0700 (PDT)
From: Brian Schottlaender <ECZ5BRI@MVS.OAC.UCLA.EDU>
Subject: CONSER Proposal: Core Record for Serials
X-To: AUTOCAT <autocat@UBVM.CC.BUFFALO.EDU>,
Cooperative Cataloging Discussion <coopcat@IUBVM.BITNET>,
SERIALST <serialst@UVMVM.UVM.EDU>
Colleagues:
The CONSER Core Elements Task Force invites your comments on its
proposed definition of a Core Record for Serials, detailed
below. Please submit any and all comments to the particular list
where this message appears, rather than only to me. In this
way, the largest number of interested individuals will be able
to participate in the discussion.
I shall appreciate receiving your input by Friday, October 7.
After that date, the CONSER Core Elements Task Force plans to
finalize the proposal for submission to and review by the CONSER
Operations Committee at its meeting in November. The Proposal
will then be forwarded to the CONSER Policy Committee for review
and endorsement by year's end.
I look forward to your comments on this latest of the proposed
core record standards. Many thanks in advance!
--Brian E.C. Schottlaender, Chair
CONSER Core Elements Task Force
UCLA
ecz5bri@mvs.oac.ucla.edu
CONSER Core Elements Task Force:
Bill Anderson (Library of Congress)
Cecilia Botero (University of Florida)
Robert Bremer (OCLC)
Carol Fleishauer (MIT)
Marianne Kasica (University of Pittsburgh)
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CORE RECORDS FOR SERIALS
A proposal for definition and incorporation into the CONSER program
I. INTRODUCTION
At the end of 1992, the CONSER Policy Committee charged
the CONSER Core Elements Task Force to evaluate the nature of
the CONSER record; to determine the core elements of the record,
with an emphasis on the identification of the publication; and
to reevaluate the bibliographic requirements for CONSER
cataloging. In Spring 1993, the CONSER Operations Committee
endorsed this review of the bibliographic requirements.
In late 1993, the Cooperative Cataloging Council (CCC)
defined a core level record for monographs to serve as an
intermediate level between full and minimal level records. Only
full or core level monographic records will be acceptable as
program records in the planned Program for Cooperative
Cataloging (PCC). While the CCC has undertaken supplementary
initiatives to define core record standards for other types of
material (e.g., JACKPHY, Music), it left the definition of such
a standard for serials to CONSER.
In February 1994, the CONSER At-Large group that met in
Los Angeles indicated its interest in exploring the utility of a
core record for serials, although a desire was also expressed
to retain flexibility within CONSER. The CONSER Core Elements Task
Force was asked to draft the CONSER Core Record for Serials Proposal.
II. OBJECTIVES OF DEFINING A CORE RECORD FOR SERIALS
A. To provide for the creation of an intermediate level
of records that are easier to create than full-level records but
provide more complete and authoritative access than
minimal-level records.
B. To facilitate maintenance of CONSER records by
defining a core group of record data elements.(1)
(1) The CONSER Core Record Task Force recommends that
the CONSER Maintenance Task Force determine which data elements
are to be maintained.
III. PROPOSAL SYNOPSIS
A. Define a single set of Serial Record Core Elements,
common to all levels of CONSER cataloging.
B. Define three levels of CONSER records: Minimal, Core, and Full.
C. Code Minimal level CONSER records as Encoding Level
"7." Code Core level CONSER records as Encoding Level "3" or
"4" {to be determined by MARBI}. Code Full level CONSER records
as Encoding Level "b" <blank>.
D. Retain 042 codes currently used in CONSER records.
IV. PROPOSAL
A. Define a single set of Serial Record Core Elements,
common to all levels of CONSER cataloging (to be augmented by
a separate list of additional core elements for non-print serials):(1)
LEADER Code all elements M
008 00-05/Date entered on file M
06/Type of date/publication status M
07-10/Date 1/beginning date of publication M
11-14/Date 2/ending date of publication M
15-17/Place of publication, distribution, etc. M
18/Frequency M
19/Regularity M
21/Type of serial M
22/Form of original item M
23/Form of item M
34/Successive/latest entry M
35-37/Language M
38/Modified record M
39/Cataloging source M
010 LC Control number M
022 ISSN MA (if available)
042 Authentication code M
1XX Main entry MA
240 Uniform title MA
245 Title M
246 Variant title MA
250 Edition MA
260 Imprint M
310 Current frequency MA
362 Designation MA
4XX Series statement MA
500 Note (source of title or DBO) MA
5XX Notes(2)
6XX Subject added entries MA
700- Name/title added entries MA
730(3)
780/785 Earlier/later title MA
{Include other 7XX linking fields, if considered significant.}
8XX Series added entry MA
(1)System-generated fields (e.g., 040) are also part of
the Core Elements set, though excluded from this list.
(2)Information that is essential to the identification of the serial.
(3)Bodies, etc. that are essential to the identification
of the serial or are essential for record access.
B. Define 3 levels of CONSER records:
1. Minimal level
a. Serial Record Core Elements are present, as
appropriate to the item (see IVB1c).
b. Name headings are checked in NAF. If present,
authorized heading is used. If not, heading is constructed
according to AACR2, but NACO authority record need not be
submitted to NAF.
c. Subject headings are not required in new records. In
adapted records, subject headings are left as found.
d. Classification is not required.
2. Core level
a. Serial Record Core Elements are present, as
appropriate to the item (see IVB2c).
b. Name headings are checked in NAF. If present,
authorized form is used; if not, NACO authority record is
created and submitted to the NAF.
c. At least one subject heading is included in new
records, if appropriate. In adapted records, subject headings
are checked for current validity and appropriateness;
construction and tagging are also checked.
d. Classification is not required.
3. Full level
a. Serial Record Core Elements are present, as
appropriate to the item. In addition, all other non-core notes,
added entries, and linking fields are included as appropriate to
the item.
b. Name headings are checked in NAF. If present,
authorized form is used; if not, NACO authority record is
created and submitted to the NAF.
c. All appropriate subject headings are included in new
records. In adapted records, subject headings are checked for
current validity and appropriateness; construction and tagging
are also checked.
d. Classification is not required.
C. Use Encoding Level values for CONSER records as follows:
7 Minimal level
3/4(1) Core level
b Full level
(1)To be determined by MARBI.
D. Retain 042 codes currently used in CONSER records.
