Label Generating Program

Note. The label printing examples are based on the SML label-printing program. The Selin label will accommodate up to 13 spaces on a line. The number of lines has been tested successfully to 11 and there seems to be no reason why additional lines could not be printed. When entering ENUM and CHRON data, provide a line break by inserting a space after the colon (or equal sign) to separate volume from part detail or main chronological designation from subordinate chronological designation whenever combined main/subordinate detail cannot fit on a single line. Always prefer keeping each level of subordinate detail on the same line. When in doubt, force a subsequent line by inserting a space. Descriptor terms like Index or Suppl. should always be forced to a separate line.

NOTE: for LSF and any other location where label-printing is not relevant, providing a line break is not necessary.

A limitation of the label printing program is that it will place ENUM/CHRON text below (LC) or (LC) Oversize when these elements are in 852 $i and $m respectively. In such cases, Preparations staff use cut and paste functionality to move the ENUM/CHRON text block into the proper position below the call number but above (LC) or (LC) Oversize. The examples in this document reflect the label output after editing by Preparations staff. Staff entering ENUM/CHRON text should follow the formatting guidelines in the previous paragraph even if the call number ends with (LC) or (LC) Oversize.

The label generating program has been updated to do the following:

a. If data is in ENUM and no data is in CHRON, label will print with ENUM data below the call

b. If no data is in ENUM and data is in CHRON, label will print with CHRON data below the call number. (In this example, the volume represents 2 complete years, 2000 and 2001.)

c. If data is in both ENUM and CHRON, both ENUM and CHRON data will print below the call number, in that order. If both enumeration and chronological designations are recorded in the bibliographic record (362 or 500) or the MFHD 86x fields, record the part specific data in both of the appropriate fields, even if this results in both designations printing below the call number.