This document discusses how a Perl script is used to log circulation transaction data from Voyager into a text file on a daily basis. Specifically, it logs item, MFHD, and bib data from various tables to preserve information not kept long-term in Voyager, like patron IDs. Going forward, the plan is to log the data directly into a MySQL database to more easily develop reports combining the logged and Voyager data.

1. Logging Data on Voyager
Transactions that Voyager
does NOT Log
Ray Schwartz
William Paterson University
Systems Specialist Librarian
Friday, October 19, 2012
ENUG 2012 Ithaca College

2. Why?
• Some data is not preserved.
• Needed for long term studies, etc. etc.

3. CIRC_TRANSACTIONS
table

4. CIRC_TRANS_ARCHIVE
table
• Transactions are move to
this table when:
• After items are
discharged
• Fines are paid
• Patron_ids are zeroed.

5. Table Relationships

6. Relationships with ITEM table

7. Using perl script to log
item, mfhd, and bib data
• Runs daily
• Logs past 24 hours
• Presently outputs into a text file

8. Logging these fields into a text file
CIRC_TRANS_ARCHIVE.CIRC_TRANSACTION_ID, ITEM.HISTORICAL_CHARGES,
CIRC_TRANS_ARCHIVE.DISCHARGE_DATE, ITEM.HISTORICAL_BROWSES,
CIRC_TRANS_ARCHIVE.ITEM_ID, ITEM.CREATE_DATE,
ITEM_BARCODE.ITEM_BARCODE, ITEM.CREATE_OPERATOR_ID,
BIB_MFHD.MFHD_ID, ITEM.MODIFY_DATE,
BIB_MFHD.BIB_ID, ITEM.MODIFY_OPERATOR_ID
BIB_TEXT.TITLE_BRIEF,
MFHD_MASTER.LOCATION_ID,
ITEM.PERM_LOCATION,
ITEM.TEMP_LOCATION,
MFHD_MASTER.NORMALIZED_CALL_NO,
ITEM.ITEM_TYPE_ID,
ITEM.TEMP_ITEM_TYPE_ID,
ITEM.ON_RESERVE,
ITEM.RESERVE_CHARGES,
ITEM.HISTORICAL_CHARGES,

9. Future
• Log data directly into a MySQL database
• Develop reports that combine both the
MySQL and Voyager Databases