# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | This describes the record as to function. | |
2 | abbreviation | 0;2 | FREE TEXT | This allows the record type to be selected by a few characters. | ||
3 | application | 0;3 | POINTER | 195.1 | C | This allows the record type to be associated with one or many applications. |
4 | inquiry display order(+) | 0;4 | NUMERIC | This is used by the system to allow application modification of displays. | ||
5 | record label format | 0;5 | POINTER | 194.4 | This defines the label format to be used when printing a record label. | |
6 | request notice format | 0;6 | POINTER | 194.4 | This defines the label format to be used when printing a request for a record. | |
7 | control of finding records | 0;7 | SET OF CODES | f:FILE ROOM SUPERVISOR ONLY! a:ANY USER | This allows the application to limit the designation of a missing record as found. | |
8 | request purge cutoff (days) | 0;8 | NUMERIC | This defines the number of days to retain requests before purging. | ||
9 | pending request cutoff (days) | 0;9 | NUMERIC | This defines the number of days before a request is considered not filled by the system. | ||
10 | pull list purge cutoff (days) | 0;10 | NUMERIC | This defines the number of days to retain pull lists before the pull lists are purged by the purge option. | ||
11 | overdue record cutoff (days) | 0;11 | NUMERIC | This defines the number of days that a charged record is allowed to be charged before it is considered by the system as overdue. | ||
11.1 | barcode renewal cutoff (days) | 0;20 | NUMERIC | This field contains the number of days required to consider re-printing a barcode label. | ||
12 | # previous movements to retain | 0;12 | NUMERIC | This defines the number of movements to not be purged by the purge option. | ||
13 | current borr request time min. | 0;13 | NUMERIC | This defines the time in the future when the current borrower may request the record again. | ||
14 | can record be requested? | 0;14 | BOOLEAN | y:YES n:NO | No means the record cannot be requested. | |
15 | is record temporary? | 0;15 | BOOLEAN | y:YES n:NO | This means that the record can only be charged out once. | |
16 | ask for content descriptor? | 0;16 | BOOLEAN | y:YES n:NO | Yes means the system will query the user to add free text for record description. | |
17 | multiple volumes allowed?(+) | 0;17 | BOOLEAN | y:YES n:NO | Yes means the system will allow creation of multiple volumes for this type of record. | |
18 | ok to purge data? | 0;18 | BOOLEAN | y:YES n:NO | NO means that all the purge parameters will be ignored by the purge option and no data is purged until this parameter is set to YES. | |
19 | retire record cutoff (days) | 0;19 | NUMERIC | This field will contain the number of days required for a record to be considered for retirement. | ||
21 | pending check-in cutoff (days) | 1;1 | NUMERIC | This describes the number of days a pending request will be displayed for a record when the record is being checked in. | ||
22 | ok to retire records? | 1;2 | BOOLEAN | y:YES n:NO | ||
50 | inactivation date | I;1 | DATE-TIME | This defines a date when the record is no longer available to be charged out. | ||
75 | linked records | LINKED;0 | MULTIPLE | 195.22 | This points to other record types which should be automatically created by the system when this record is created. | |
100 | allowable file rooms | F;0 | MULTIPLE | 195.21 | This defines which borrower/file areas may be allowed to check in this type of record. | |
150 | description | D;0 | WORD-PROCESSING | This free text allows the record to be described more fully. |