Fixed-length Fields

Each type of record has a set of valid fixed-length fields. The fixed-length fields are described in:

Fixed-length Fields in All Records
Fixed-length Fields in Authority Records
Fixed-length Fields in Bibliographic Records
Fixed-length Fields in Checkin Records
Fixed-length Fields in Contact Records
Fixed-length Fields in Course Records
Fixed-length Fields in Institution Records
Fixed-length Fields in Invoice Records
Fixed-length Fields in Item Records
Fixed-length Fields in License Records
Fixed-length Fields in Order Records
Fixed-length Fields in Patron Records
Fixed-length Fields in Program Records
Fixed-length Fields in Resource Records
Fixed-length Fields in Section Records
Fixed-length Fields in Vendor Records

Fixed-length fields can be enabled or disabled by contacting Innovative. Only Innovative can create new fixed-length fields.

If a fixed-length field is valid for a record type and enabled, it will appear in every record of that type. (Note that if a variable-length field is valid for a record type and enabled, it is not required to appear in every record of that type.)

Each fixed-length field contains one of the following:

• A code chosen from a set of valid codes
• A date (note limits, below)
• A monetary amount

Each code has a definition. For example, the fixed-length field ACQ TYPE can contain the code p, which for ACQ TYPE is defined as "purchase." The set of valid codes and their definitions is different for each fixed-length field in a record type.

For some fixed-length fields, your organization can determine the codes and/or definitions. Other fixed-length fields contain MARC codes or codes set by the system.

To see the fixed-length codes in use on your system, choose Admin | Parameters | General | Fixed-length Codes (see Fixed-length Codes File).

To edit a fixed-length field, see Modifying Fixed-length Fields.

Default Content in Fixed-length Fields When Creating Records

When you create a record, you begin by selecting a record template (or allowing the system to choose a template for you). A template contains default content for some or all of the fields.

The default content will be entered into the new record unless:

• You overwrite the default by entering other content.
• A bibliographic utility overwrites the default with content from the 008 field, the leader, or data entered at the bibliographic utility terminal.

To edit the default content in templates, see Editing Record Templates.

Templates also determine which fields you are prompted to provide content for when creating a record. To change the fields that you are prompted to provide content for, see Editing Record Templates.

Note that invoice records use system-defined templates that are accessible from the Invoice function. Users do not select templates when creating invoices.

Fixed-length Field Limits

Fixed-length fields may be limited by the length of the code, the length of the code's definition, the length of the code name, and the maximum number of codes. See the descriptions of each field for more information.

Each fixed-length field has a short label, with a maximum length of ten characters. An example of a short label is ACQ TYPE. In addition to the short label, many fixed-length fields also have a long label, with a maximum length of eighty characters. An example of a long label is Acquisitions Type. The system displays the long label if one is defined for the field or the short label if no long label is defined for the field.

You can edit the long names with Advanced System Access & Administration (ASAA).

Fixed-length Fields Defined by Your Organization

For each of the following fixed-length fields, your organization can:

• Ask Innovative to rename the field (sometimes referred to as changing the "code name").
• Specify the valid codes for the field.
• Specify the definitions of the codes.

¹ Innovative can only rename ICODE1 (change the label). Valid codes and code definitions cannot be specified for this field.

Fixed-length Field Codes and Code Values That Should Not Be Altered

The fields in the table below have certain values that should not be removed or altered. For example, the "NO MESSAGE" value for IMESSAGE should not be deleted from the system. "NO MESSAGE" must be present in the list of possible values, even if it is not the value assigned to IMESSAGE.