Related product I-Share

Circulation System Adminisration: How Circulation Administration Values are Used During a Checkout

  1. Circulation person logs in at a circulation terminal.
    1. Sysadmin looks up the userid.
    2. Sysadmin links to the circulation profile for that person.
    3. Sysadmin determines the circulation happening locations in the security profile.
    4. If more than one happening location exists in the security profile, a selection screen appears in the circulation module.
    5. Once one happening location is chosen, the circulation module is opened.
    6. The happening location chosen at login determines the Sysadmin circulation policy group, which in turn determines the circulation calendar, notice intervals and patron blocks checked.
       
  2. A patron’s barcode is scanned.
    1. If this is a UB patron, patron barcode lookup will automatically choose the home library of the patron using the patron barcode prefix found in the table. If the patron barcode prefix is not found in the barcode table, you will be prompted to choose the patron’s home library from the drop down menu.
    2. If more than one patron group is active, the circulation person chooses a patron group.
    3. If this is a UB transaction, the patron’s home library UB policies are checked for UB privileges and blocks.
    4. If this is not a UB transaction, the patron’s limits (items charged, overdues, lost items, etc) are checked against the Sysadmin circulation policy group patron blocks.
    5. NOTE: The remaining items are done regardless of UB vs. non-UB transaction.
    6. d. The patron’s expiration date is checked.
    7. e. If a patron block screen appears, it would need to be cleared.
       
  3. Charge/Renew
    1. If this is a UB transaction, item barcode lookup will automatically choose the owning library of the item using the item barcode prefix found in the table. If the item barcode prefix is not found in the barcode table, you will be prompted to choose the item’s owning library from the drop down menu.
    2. NOTE: The remaining items are done regardless of UB vs. non-UB transaction.
    3. Scan the item barcode.
    4. The item is checked for item blocks (lost item, already charged, etc) that come from the status of the item.
    5. The item location (or temporary location if it exists) is checked against the Sysadmin circulation policy groups.
    6. The policy group of the item is determined.
    7. The Sysadmin circulation matrix matching the item location is determined.
    8. If the item and the patron are both OK for the charge, the item type (or temporary type if it exists) and the patron’s group are used to look up the potential loan period.
    9. The potential loan period is computed and checked for the earliest of the following:
      • Computed loan period
      • Patron expiration date
      • Fixed due date (if it exists)
      • Minimum loan period for recalled items (if it exists)
      • Calendar expiration date
    10. Charge goes through.
    11. Patron counters are incremented.
    12. Due date slip prints if applicable.
       
  4. Next item charged will repeat steps 2A through 3L. (System rechecks patron blocks for every charge.)