D3.  Description/Instructions

The explanation of each field consists of a brief description of the field, editing instructions, indicator and subfield usage, and related fields.  Additional instructions are given where applicable.

D3.1.  Delimiter

Prior to 2002, the double dagger (‡) was used for the subfield delimiter in the text and examples.  With the 2002 update, a dollar sign ($) has been used in those CEG field descriptions that have been updated and will be replaced in other fields as they are updated for other reasons in the future.

D3.2.  Abbreviations, acronyms, etc.

The following abbreviations and acronyms are used throughout the text:

D3.3.  "CONSER policy" and "CONSER practice"

The phrases "CONSER policy" and  "CONSER practice" are used throughout the CEG.  In general, "CONSER policy" refers to usage that is backed by an LC rule interpretation, while "CONSER practice" refers to agreed-upon practices resulting from various needs (e.g., automation, cooperative cataloging, etc.).  In most cases where a specific LCRI is the basis of a policy, the LCRI is cited in the text.

D3.4.  Examples

A significant effort has been made to provide examples that are appropriate to serial records.  In addition, examples illustrate both simple and complex situations.  Both English and foreign language examples are included; however, the limitations of the word processing software used to create this publication restricts the use of some diacritics.  Therefore, diacritics will not appear in some examples (e.g. Chinese, Russian).

Examples in the 1994 edition have been revised to reflect format integration, as well as current policies and practices.  They may or may not reflect the online record.  Examples will be changed only when they are found to be incorrect or to reflect changes in the format.  In general, examples will not be changed if they were correct when created but current versions of AACR2 rules or LC rule interpretation would call for a different construction.  New examples will be added as the need arises.

D3.5.  System requirements

The common database used by CONSER members is the OCLC Online Union Catalog.  All references to system-supplied elements or punctuation refer to OCLC.  Because subfield $a is not displayed but system generated, and therefore, is not input on OCLC when it is the first subfield code in a field, it is not given in the examples.

D3.6.  Spacing requirements related to card production

Throughout the instructions in Part E there are various spacing requirements left over from the days of catalog card production.  In May 2000, the CONSER Operations Committee agreed to stop following this practice and use normal spacing (e.g., a single space following a hyphen for an open date in subfield $c of the 260 field; an open date given in a note, or an incomplete designation system when recording an alternative system in the 362 field).  This brings bibliographic and name heading practices in line.  Note that this change applies only to spacing preceding or following a hyphen in an open date.  It does not apply to spacing requirements for subfield $w in linking entry fields, which remain as stated in the instructions.  For linking fields, a CONSER participant may leave one space after a period that separates distinct elements of a name or title used in a linking field, if the participant's local system will allow this.  Some ILS systems may require that two spaces be used.

See also:

Section D.  Introduction to Format

CONSER Editing Guide:  Contents