Skip to Main Content

Collection Management Procedures: Sierra Checklist

Sierra Checklist

Acquisitions Checklist

      From CSDirect: http://csdirect.iii.com/sierra/kb/article.php?cat_id=1&typ_id=3&art_id=344

 

The following checklist is meant to be a guide to help you manage your Sierra System.

The frequencies we suggest are only recommendations. Your library may perform certain activities more or less often depending upon your needs and policies.

Daily

  • View the Acquisitions/Serials Status screen and note the number of:
    • encumbrances ready to post
    • pay file records to post
    • Payment History file records ready for Fund Activity report
    • purchase orders to print
    • claims to print
  • Post. Do not allow the total of all records to post (encumbrances plus records in a payfile) to exceed 2,000.

Weekly

  • Print Purchase Orders.
  • Send electronic orders.
  • Print Fund Activity reports weekly (recommended) or monthly (at least) and clear the Payment History file. Do not allow the combined total of encumbrances to post, payfiles to post, and records in the Payment History file to exceed 10,000.
     

    If funds are in balance, after printing the Fund Activity report, the user will have the option to clear the Payment History file. If the funds are not in balance, contact the Innovative Customer Services Department Help Desk.

  • Claim overdue orders weekly (recommended) or monthly (at least).
     

    Since the claim cycle is calculated from the order date (ORD DATE) fixed field, irregular claiming may cause the system to repeatedly identify an order record as claimable. For example, if the claim cycle is every 30 days, and you do not send the first claim until 100 days after ordering, subsequent sessions will immediately present the same record for a second and third claim.

Monthly

  • Create a list of orders that have receive dates but that have not yet been paid. Evaluate these orders for potential further action (corrections in the case of mistakes, follow-up with vendors in the case of unusual delays, etc.).
  • Print Web Management Fund reports monthly or as needed.

Yearly

  • Update order records to enable continued payment for ongoing subscriptions and standing orders.

As needed