Follett VERSION 6.00 - Manual (Page 176)

04/04 176 Circulation Desk
Before recording transactions with a PHD
Because your PHD does not store information about your patrons, if you use it to
circulate your collection, transactions that would normally produce block
conditions continue as if the patron had violated none of your loan policies. You
can help reduce the size of the Remote Circulation exception report by printing
the following reports from Reports and using them to monitor transactions
before you record them with your PHD:
S Patron Name List Ċ You should print two of these: one that shows patrons
that have a status of restricted, and one that shows patrons that have
graduated or are inactive. You probably do not want to check out or renew
any copies to restricted patrons. It is also unlikely that you want to circulate
items to patrons who have graduated. For more information, see page 575.
S Checkouts/Fines Transactions Ċ This report is sorted according to patron
name and shows every overdue and fine each patron currently has. Using
this report to monitor patrons as they check out and renew copies is the
equivalent of the block conditions that would normally appear in Circulation
Desk during a transaction. For more information, see page 540.
Recording transactions with a PHD
Follett Software currently supports four PHD models. For instructions on
recording transactions with the PHD+, PHD+ II, or PHD Laser+, see Recording
remote circulations" on page 661. To record transactions with a PHD Dolphin+,
see Collecting circulation information" on page 674. When you finish collecting
transactions, connect your PHD to your computer.
See also: For more information about using your PHD, please see the
manufacturer's user documentation as well as Appendix E, Using a PHD+,
PHD+ II, or PHD Laser+," or Appendix F, Using a PHD Dolphin+."
Processing remote circulation transactions
Before Circulation Desk can process your scans, you must decide how to process
problematic transactions.
An example of a problematic transaction would be a checkout where either the
patron barcode or the copy barcode does not exist in your database. Anytime
Circulation Desk encounters a problem while processing the remote circulation
data, it sends a message to the exception report. The above example would also
cause the transaction to fail.