In this topic:

D2.1.  Asterisk


D2.2.  Captions


D2.3.  Order of code listing


D2.4.  Repeatability codes


D2.5.  Requirement codes

Each field begins with the indicator values, codes, or subfield codes defined in the MARC 21 Bibliographic.  Certain OCLC-defined content designators, labelled "[OCLC-defined]", are also given.

In cases where the current usage of a code requires qualification, an asterisk ( * ) or caption appears with the code.

D2.1.  Asterisk

*    The asterisk appearing after a field name or a value or code name means the following:

--   LC does not use (in all cases).

--   LC will distribute if used in an authenticated record (in all cases).

--   LC will not authenticate the validity of the information provided (in all cases).

--   The code is defined for use by other national libraries (e.g., field 055) (in some cases).

D2.2.  Captions

The following captions appear in square brackets after a field name, indicator value, or subfield code.

[Not applicable]  The element is not or is not likely to be applicable to serials.  With format integration, all subfield codes defined for a field are now eligible for use in serial records; however, many are not applicable.

[Not used]  The element may be applicable for serials but is not used by CONSER for one of several reasons.  These include CONSER policies as backed by an LC rule interpretation, CONSER practices relating to automation requirements, and institutional policy (for institution-specific fields).

[Not yet implemented]  The element has been defined in MARC 21, but has not yet been implemented by OCLC.

[… use only]  This caption identifies a field or code that is valid only for input by an authoritative agency (e.g. 055).

[Pre-AACR2]  This caption indicates that the value or code was used and is still valid in records created prior to AACR2, but should not be used in AACR2 records.  These values may be used in pre-AACR2 records newly created as part of retrospective conversion.

[Provisional]  This is a MARC 21-assigned caption that is used for fields or elements that are still somewhat experimental (037 $g, 786).  Final approval of content designation market as "[Provisional]" will await the experience gained from use of the field.

[Obsolete]  This caption indicates that the value or code was used and is still valid in older records, but should not be used in current cataloging.

D2.3.  Order of code listing

All indicator values are given in numerical order.  All subfield codes are given in alphabetical order, followed by those with numeric values, given in numeric order.  In the 6XX and 8XX heading fields, the numerous subfield codes are divided into categories:  name portion of heading, title portion of heading, control subfields, etc.  Fixed field codes are given in alphabetical order.  Because some fields include many subfield codes and not all are used, it is not useful to indicate the input order for all; however, those most commonly used are given in their input order under the section "Subfields" within the description of the field.

D2.4.  Repeatability codes

Repeatability codes are given, as specified in the MARC 21 Bibliographic, in parentheses following the name of each field or element.  Repeatability codes are not given for indicators because none are repeatable.  Repeatability codes are provided for all subfield codes with the exception of those qualified as "[Not used]" or "[Not applicable]".

At the field level, the repeatability code specifies whether the field may be repeated in a record.  For subfield codes, the repeatability code specifies whether the subfield code is repeated within a field.  Further instructions on the repeatability of specific content designators are given in the instructions when necessary.

R  Repeatable

NR  Not repeatable

Repeatability codes for fields 022 and 222 intentionally differ from the MARC 21 Bibliographic which defines these as repeatable.

D2.5.  Requirement codes

CONSER records may be created at the full, core, or minimal level as defined in B6.  Requirement codes no longer appear with individual fields.  Fields that are system-generated are designated as such to the right of the field name.  All indicators must be used, as specified within each field.  No requirement codes are provided at the indicator or subfield level.  The use of subfields is generally determined by the data that they contain, which is governed by AACR and rule interpretations.

See also:

Section D.  Introduction to Format

CONSER Editing Guide:  Contents