Holdings and Related Files :  Circulation File                   Index

Primary Key

BIBRECNUM Bib Record Number

BK^ID Book barcode

ACT^TYPE Action type

OCCUR Occurrence

PAT^ID  Patron id	ACT^DTE  Action date	TR^DTE Transaction date	DUE^DTE  Due date	RNWLS  Renewals	LAST^NOTICE  Last notice
LOAN^PERIOD Loan period	ACT^SUB^TYPE Action sub type	NOTE^CNT Notice count	DUE^TIME Due time	RENEWED^TODAY Renewed today	AUTO^BLOCK Auto block
I^LOC Shelving loc	LOC Owning loc	CPY Copy number	CNNUM  Call number number	ITEM  Item statement and subfielded data

Analysis

BIBRECNUM.   int(32)
Unique system generated number which links related holdings records to each other, and to their associated BIBFILE records.

BK^ID.   string(13)
Barcode number identifying the circulating item. Currently a charge transaction can only be made against UCB barcode (*l), but field is set up to allow for use with the NRLF (*s) barcode at some point as well. Alternate key field.

ACT^TYPE.   string(1)
One character code identifying the type of circulation transaction which is active. The following ACT^TYPE codes are currently in use:

     c - charge
     r - recall
     p - pickup
     b - bill
     k - bill cancellation
     o - outstanding invoice charges
     x - fine at discharge
     f - search
     z - reserve prep

OCCUR.   string(1)
Normally set to 0.  Set to allow multiple ACT^TYPE “o” records for the same book to be written.

PAT^ID.   string(9)
Circulation id of patron involved in the circulation transaction represented. Links circulation record to patron record in the PATRECS file. Alternate key field.

ACT^DTE.   struct [int(3)]
Consists of 3 words, one each for YEAR, MONTH and DAY, indicating date on which next action (usually a notice) is to be taken on the circulation transaction represented. Alternate key field.

TR^DTE.   struct. [int(3)]
Consists of 3 words, one each for YEAR, MONTH, and DAY indicating date on which original transaction was initiated.

DUE^DTE.   struct. [int(3)]
Consists of 3 words, one each for YEAR, MONTH and DAY indicating date on which item is/was due. Should correspond to the date in the *d of the V/C.

RNWLS.   int(1)
Count of the number of times an item has been renewed. Incremented by CHARGE and CIBYLINE server programs at point of renewal.

LAST^NOTICE.   string(1)
Records the last notice issued to the patron and/or circulation staff regarding the circulation transaction. The same notice codes are used here as are used by MAKETRIG when setting up the PTRIGGER and LTRIGGER records which control notice production.

LOAN^PERIOD.  string(1)
Represents period for which item was loaned. Based on CIRCCODE in the V/C for the item loaned and the user’s borrowing privilege. Chart of loan period numeric codes and their corresponding loan periods.

ACT^SUB^TYPE.   string(1)
Used to make distinctions within a particular ACT^TYPE category. ACT^TYPEs that are subdivided include the RECALL, CARS billing, and DISCHARGE FREE categories. Chart of ACT^SUB^TYPEs.

NOTE^CNT.   string(1)
Count of the notices of a particular type which have been issued if multiples are possible. Multiple notices are only issued in the search and bill cleanup categories.  NOTE^CNT indicates how many search notices or bill cleanup notices have already been issued.

DUE^TIME.   struct [int(2)]
Consists of 2 words, one for hour due and one for minute due. Used to record the due time for items checked out with a two hour loan period and to record hold expiration time for items with a two hour loan period on pickup shelf.

RENEWED^TODAY.   string(1)
If set to 1 (by CHARGE program), indicates item has been renewed. Used by MAKETRIG to determine when to set up renew cleanup, rather than overdue notice.

AUTO^BLOCK.   string(1)
Indicates if user has been autoblocked for this charge due to overdue. Set to 1 by CIRCUPD when user is to be blocked due to an overdue on the charge represented by this CIRC  record. There is always a grace period between the time that the item becomes overdue and the time this block byte is set "on".

Also set by CHARGE when a manual bill is placed and by CIBYLINE when a claims returned item is restored, or if appropriate, on cancellation of a  claims return or renewal.

I^LOC.   string(1)
Set to location from which the item has been circulated if this differs from the owning location. Established to record "intermediate" charge location, when an item is charged from a location other than the owning unit.

In the past, this was used as part of a paging module, such as PAGE BOCC, PAGE MOFF,etc. For example, when BIOS items were charged from BOCC storage facility, I^LOC was set to a numeric code (103) representing BOCC. This information was used to signal the notice programs to append BOCC to the call number.

Currently this is used when a reserve item is circulated. In these cases I^LOC is set to the numeric  loc code representing the reserve location, even if the reserve location is the same as the owning location. The reserve location can be any of the standard location codes used in the LOC field (see below), or can be a special reserve loc, such as open stack reserves, within a standard location. The fourteen special reserve locations use numeric codes beginning with 150.  Six regular reserve locations have one or more of these special reserve locations: AH-C, BUSI, ED-P, MUSI, SOCW, and UNDE.

LOC.   string(1)
Location code of the library location that owns the item being circulated. Matches the location code in the corresponding V/C.

CPY.   string(3)
Originally set up to store the copy number of the item being circulated at a time when copy information was stored in a discreet field in the V/C. Copy is now stored as part of the volume/year information in the ITEM statement. Field is now largely obsolete, and is not filled in for new charges.  However it has been retained in the CIRCREC structure since old charge records in the CIRCFILE may still use it.

CNNUM.   string(1)
Number identifying the call number in the bibliographic record associated with the charged item. Matches the CNNUM in the corresponding V/C.

ITEM.  string(1319)
Contains the item statement from the corresponding V/C.  (The information down to, but not including the first "*" subfield). After the item statement, may include subfielded information.