Accommodating Standing Orders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Evergreen version 2.4.6 and 2.5.2
Evergreen does not currently support standing orders. Libraries currently utilizing the Acquisitions module have created their own, in-house workarounds for their standing orders (Bug #1027244 lists just one of these workflows). However, the Acquisitions module should provide a more intuitive way for users to set up and/or track their standing orders. With standing orders, acquisitions librarians need to have a way to track their funds and create purchase orders (and probably a few more considerations that I did not list).
There are multiple types of standing orders that need to be taken into consideration. In some instances, the standing orders arrive at known frequencies and known prices. Some standing orders span across multiple fiscal years. Some standing orders are “pre-approved” (for example, setting up a standing order for all of the new Oprah Book Club materials), however, the library does not know when it will receive the items or what the final price will be for those items. Other standing orders may be set at a specified price, but the library does not know when they will receive the items (such as an academic series, where the series is sporadically published).
I would really like to get this conversation going and hear other people’s thoughts on how they would expect Evergreen to handle the fund management and the seemingly nebulous nature of standing orders.
Here is a sample brochure from Baker and Taylor's Collection Development Services:
description: | updated |
Changed in evergreen: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | added: needsdiscussion |
tags: | added: acq-po |
At the very least there should be an "order type" category in the PO that would make it possible to identify what kind of order is being processed. e.g Firm, Series Standing Order, Periodical, etc. That would provide a hook for reports.