Formatting Transaction Files for Uploading: rd* File Formats

Files for inventory counts, circulation transactions, and internal use counts are generally compiled using Innovative software. Occasionally you may wish to manually compile a file to upload and process, for example to batch renew a file of items. The library can compile a file manually as long as you use the proper format.

For information on loading and processing files, see Processing Offline Circulation Files.

Following are format specifications for files to be uploaded to the server, including the following types:

• Inventory counts
• Check-out/ Renew/ Check-in transactions
• Internal Use counts

File Name

The system expects the following naming convention:

You may use the alphanumeric characters of choice for the file name, so long as the first three letters indicate the file's type.

File Formats

The programs that accept uploaded data expect the following file formats:

Where:

• [prefix code] is the prefix code.
• [transaction date] is the date and time of renewal activity in yymmddhhmm format.
• [barcode] is the item barcode.
• [patron barcode] is the patron barcode.
• [null] is empty.
• [due date] is the item's due date in yymmddhhmm format.
• [statgroup] is the statistics group number.

Examples:

The following is a valid example for a check-in transaction:

i:0310020355:b30650000156732:::15

The following is a valid example for a check-out/renewal transaction:

o:1212010830:b31551010350230:b215510204020201:1301310400:992

In Inventory and Use Count files, each line should contain a single barcode.

Below are valid examples for inventory count barcodes:

n:35239000000060
n:35239000000078
n:35239000000086
n:35239000000094
n:35239000000102
n:35239000000110

Valid Prefix Codes