3.3.1 Field 1 Function Keys

3.3.2 Field 2 Catalog Namespace: 20 characters, mandatory, tab stop

Purpose: To specify the database path to the catalog file.

Format: a valid operating system path or Cache namespace.

3.3.3 Field 3 Bibliography Namespace: 20 characters, mandatory

Purpose: To specify the database path to the bibliographic file.

Format: a valid operating system path or Cache namespace.

3.3.4 Field 4 MeSH Namespace: 20 characters, mandatory

Purpose: To specify the database path to the MeSH file.

Format: a valid operating system path or Cache namespace.

3.3.5 Field 5 System Namespace: 20 characters, mandatory

Purpose: To specify the database path to the database system files.

Format: a valid operating system path or Cache namespace.

3.3.6 Field 6 MARC Batch Namespace: 20 characters, mandatory

Purpose: To specify the database path to the batch file.

Format: a valid operating system path or Cache namespace.

3.3.7 Field 7 Products: multiple, mandatory, tab stop

Purpose: to specify the installed products in this catalog.

Menu Style: Radio Button/Check Box

Menu Values:
Acquisitions
Catalog
Circulation
DDS/ILL
Reserves
Serials
Utilities
MeSH

3.3.8 Field 8 Maximum Errors: 2 characters, mandatory

Purpose: To specify how many software errors the application should record per day.

Format: It is a positive number up to and including 99.

Discussion: The application should have no errors. Nevertheless, an error may occur if:

     - the application was programmed incorrectly (a bug);  
     - the database fails (usually due to hardware disruptions);  
     - hardware or supporting component (e.g., operating system) 
       failure;  
     - a feature was activated which was not installed.  
  

When an error occurs, the application may record the fact of the error as well as many of the current conditions. Such a recording can assist the vendor in diagnosing the problem.

Storing the error record takes a lot of disk space.

If a failure occurs, the application may send e-mail to the vendor' s support staff. This message should elicit a rapid response from the vendor.

3.3.9 Field 9 Number of errors to e-mail: 2 characters, mandatory

Purpose: To specify the number of errors per day which should be automatically sent to the vendor via e-mail. Once this number is reached, additional errors will not be sent to the vendor automatically.

Format: It is a positive integer.

3.3.10 Field 10 Timeout Rate: 4 characters, mandatory

Purpose: To specify the timeout rate for a field in minutes. If the user has no activity by the end of this period, then the application will display a warning window indicating the situation. If the user does not respond to the warning window with the same amount of time, then the application will terminate the session.

Format: It is a positive integer representing minutes. A timeout of 0 ( zero) means there is no timeout.