5. Gap and Non-Gap Breaks; Line Breaks

When volumes are added, Yale practice is to enter a new 866 field, the equivalent of a "line break," under the following circumstances:

5-1. When a Gap Occurs. The line preceding the new 866 field should end with a comma:

5-2. When a Non-Gap Break Occurs. A non-gap break in enumeration may be caused by units that were never published or some other irregularity in the numbering scheme caused by the publisher. According to the standard, a non-gap break is represented optionally by the use of a semicolon.

Use a semicolon followed by a line break (i.e., new 866 statement) primarily to indicate where units were never published.

Example 5-2a. Set complete; information from publisher available that v. 4 was not published.

Example 5-2b. Volume mis-numbered by the publisher.

5-3. Use of Line Break Without Comma or Semicolon. If conditions warrant recording holdings in itemized form, and neither a gap nor a change in numbering occurs between items, the standard does not use punctuation at the end of the 866 field when the items are recorded in separate 866s. (See ANSI p. 45, Example 28)

Example 5-3a. No change in the numbering scheme from volume to volume, but cataloger chose to display each volume in a separate volume holdings statement rather than to compress because the location does not use item records.

Example 5-3b. Change in numbering scheme at v. 2; because the set is small, and because the parts are bound separately, the cataloger itemized in order to bring out the part detail. (Remember that if parts are bound in a single physical volume, the part detail is not recorded. See Section 4. on fascicles.)

Example 5-3c. In the absence of publisher information, cataloger may be unsure whether v.1:pt.3-v.1:pt.4 and v.3:pt.4 may be wanting or may not exist. Compression (v.1-v.3) may cause ambiguity if v.1:pt.3 were added.

Ambiguity. When volumes and parts are issued without captions, compression may cause ambiguity; for purposes of clarity separate 866 fields may be preferable.

Example 5-3d.Compressed form (ambiguous):

Example 5-3e. Same volume holdings, itemized for clarity:

Example 5-3f.

In this case converting the recon holdings information to ANSI standards would probably require examination of the volumes, so the recon data is left as found, and a new line denotes the change in enumeration display to the standard. (Catalogers should NOT retrieve previously cataloged volumes in order to revise the entire MFHD to ANSI standards!)

Since the pre-Orbis volumes may not have item records, the part detail captured to some degree in the pre-ANSI volume holdings statement would also be lost if the holdings were summarized in ANSI form. In most cases, the part detail for the volume added on Orbis and displayed in summarized form in 866-2 will be recorded in the ENUM field of the item record, e.g. ENUM t.5:1 and ENUM t.5:2.