2.45.1 Field 1 Function Keys

2.45.2 Field 2 Profile Number: 2 characters, tab stop

Purpose: this field is both a table lookup field and a means to create a new Profile. By entering an existing Profile Number, the user may edit that Profile. Conversely, to create a new Profile, enter a number that is not being used.

Format: the Profile Number must be a positive integer. The numbers have no special meaning, i.e., a Profile Number may be 1, 2, 3, 852, or 901, etc.

2.45.3 Field 3 Profile Name: 40 characters, mandatory, tab stop

Purpose: the Profile Name should uniquely describe an individual Profile, so that a user may select the correct profile in MARC Batch Control.

Format: this field is free text.

2.45.4 Field 4 MARC Tag Number: 3 characters, mandatory, tab stop

Purpose: MARC Tag Number specifies the MARC Bibliographic or Holdings tag number whose subfields represent the holdings data.

Format: The value should be 3 digits, e.g., 852, 901, etc.

2.45.5 Field 5 Profile Status: mandatory, tab stop

Purpose: the Profile Status grants access to the profile for use in the MARC Batch Control. A Profile might be deactivated for after a conversion, or if a cataloging service changed.

Menu Style: Radio Button/Check Box

Menu Values:
Active
Inactive

2.45.6 Field 6 Run function Fix Corrupt Bibs: tab stop

Function [Fix Corrupt Bibs] makes the following corrections:

1) Converts all indicators that are not 0 through 9 or the space character to the space character;

2) Removes trailing spaces from subfield values;

3) Removes subfields with no values;

4) Removes tags with no subfields (obviously, steps 2 and 3 can result in this condition);

5) When found in a subfield value, converts the Carriage Return or Linefeed character to a space.

Selecting this feature will cause the Fix function to automatically run before running functions [Compare Import Holdings Profile to Call#] or [Item Creation].

2.45.7 Field 7 Namespace Subfield: 1 character, tab stop

Purpose: Namespace specifies which subfield is used to determine the target database. Only a programmer can specify this value.

Format: a valid subfield. Typically, it is nil.

2.45.8 Field 8 Namespace Xecute: 60 characters, tab stop

Purpose: Namespace Xecute allows a programmer to manipulate the MUMPS variable NAMESPACE in order to file the item in the correct directory.

Format: This field should be a MUMPS Xecute.

2.45.9 Field 9 Call Number Subfield: 1 character, mandatory, tab stop

Purpose: field Call Number Subfield specifies which subfield represents the Call Number.

Format: it should be a valid subfield, e.g., "h" but without the quotes.

2.45.10 Field 10 Call Number Xecute: 120 characters, tab stop

Purpose: Call Number Xecute allows a programmer to manipulate the MUMPS variable CNO in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.11 Field 11 Location Subfield: 1 character, tab stop

Purpose: field Location Subfield specifies which subfield represents the Circulation Location.

Format: it should be a valid subfield, e.g., "b" but without the quotes.

2.45.12 Field 12 Location Xecute: 120 characters, tab stop

Purpose: Location Xecute allows a programmer to manipulate the MUMPS variable LOCATION in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.13 Field 13 Bar Code Subfield: 1 character, tab stop

Purpose: field Bar Code Subfield specifies which subfield represents the Bar Code.

Format: it should be a valid subfield, e.g., "p" but without the quotes.

2.45.14 Field 14 Bar Code Xecute: 120 characters, tab stop

Purpose: Bar Code Xecute allows a programmer to manipulate the MUMPS variable BARCODE in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.15 Field 15 Copy Number Subfield: 1 character, tab stop

Purpose: field Copy Number Subfield specifies which subfield represents the Copy Number.

Format: it should be a valid subfield, e.g., "t" but without the quotes.

2.45.16 Field 16 Copy Number Xecute: 120 characters, tab stop

Purpose: Copy Number Xecute allows a programmer to manipulate the MUMPS variable COPY in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.17 Field 17 Year Subfield: 1 character, tab stop

Purpose: field Year Subfield specifies which subfield represents the Year.

Format: it should be a valid subfield, e.g., "f" but without the quotes.

2.45.18 Field 18 Year Xecute: 120 characters, tab stop

Purpose: Year Xecute allows a programmer to manipulate the MUMPS variable YEAR in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.19 Field 19 Volume Subfield: 1 character, tab stop

Purpose: field Volume Subfield specifies which subfield represents the Volume.

Format: it should be a valid subfield, e.g., "f" but without the quotes.

2.45.20 Field 20 Volume Xecute: 60 characters, tab stop

Purpose: Volume Xecute allows a programmer to manipulate the MUMPS variable VOLUME in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.21 Field 21 Issue Subfield: 1 character, tab stop

Purpose: field Issue Subfield specifies which subfield represents the Issue.

Format: it should be a valid subfield, e.g., "f" but without the quotes.

2.45.22 Field 22 Issue Xecute: 60 characters, tab stop

Purpose: Issue Xecute allows a programmer to manipulate the MUMPS variable ISSUE in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.23 Field 23 Public Comment Subfield: 1 character, tab stop

Purpose: field Public Comment Subfield specifies which subfield represents the Public Comment.

Format: it should be a valid subfield, e.g., "z" but without the quotes.

2.45.24 Field 24 Public Comment Xecute: 60 characters, tab stop

Purpose: Public Comment Xecute allows a programmer to manipulate the MUMPS variable PUBLIC in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.25 Field 25 Nonpublic Comment Subfield: 1 character, tab stop

Purpose: field Nonpublic Comment Subfield specifies which subfield represents the Nonpublic Comment.

Format: it should be a valid subfield, e.g., "x" but without the quotes.

2.45.26 Field 26 Nonpublic Comment Xecute: 60 characters, tab stop

Purpose: Nonpublic Comment Xecute allows a programmer to manipulate the MUMPS variable NONPUB in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.27 Field 27 Circulation Class Subfield: 1 character, tab stop

Purpose: field Circulation Class Subfield (a.k.a. Loan Class) specifies which subfield represents the loan period. Usually the item inherits the Circulation Class from the Location Table, so that this mapping is typically unnecessary.

Format: it should be a valid subfield, e.g., "b" but without the quotes.

2.45.28 Field 28 Circulation Class Xecute: 60 characters, tab stop

Purpose: Circulation Class Xecute allows a programmer to manipulate the MUMPS variable CIRCCLAS in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.29 Field 29 Circulation Status: 1 character, tab stop

Purpose: field Circulation Status Subfield specifies which subfield represents the item's Circulation Status, e.g., Available, Non-circulating, On Loan, etc. Usually the item inherits the Circulation Status from the Location Table, so that this mapping is typically unnecessary.

Format: it should be a valid subfield, e.g., "b" but without the quotes.

2.45.30 Field 30 Circulation Status Xecute: 60 characters, tab stop

Purpose: Circulation Status Xecute allows a programmer to manipulate the MUMPS variable CIRCSTAT in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.31 Field 31 Price Subfield: 1 character, tab stop

Purpose: field Price Subfield specifies which subfield represents the Call Number.

Format: it should be a valid subfield, e.g., "9" or "p" but without the quotes.

2.45.32 Field 32 Price Xecute: 60 characters, tab stop

Purpose: Price Xecute allows a programmer to manipulate the MUMPS variable PRICE in order to perfect it.

Format: This field should be a MUMPS Xecute.

2.45.33 Field 33 Controls Ok, Cancel, & Help: tab stop

Purpose: To specify an action that controls the window's flow. [Ok] will save and apply the displayed values, whereas [Cancel] will reject the changes. [Help] will display all of the documentation for the window. Press the Help key for context sensitive help for each field.

Format: It is an action that toggles the push button.

Menu Style: Push Button

Menu Values:
Ok
Cancel
Help
Remove...

Function [Remove] will expunge a selected Profile from the table of Profiles. Removal will have no effect on MARC bibs or existing items.