Accommodating Standing Orders

Bug #1287258 reported by Erica Rohlfs
44
This bug affects 9 people
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:

 http://www.btol.com/pdfs/CD_brochure.pdf

Erica Rohlfs (erohlfs)
description: updated
Kathy Lussier (klussier)
Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Don Butterworth (don-butterworth) wrote :

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.

Revision history for this message
Christine Burns (christine-burns) wrote :

Blanket Order functionality was added in 2.9

I believe this bug can be resolved.

Revision history for this message
Kathy Lussier (klussier) wrote :

Although Blanket Orders have helped some with some Standing Orders, I think more can be done to accommodate the different types of standing orders a library may have. I'm not the best person to describe what is needed to accommodate those orders, but, in discussions with some of our acq staff, I know they are looking for something different to accommodate series standing orders, for example, or periodicals.

tags: added: needsdiscussion
tags: added: acq-po
Revision history for this message
Tiffany Little (tslittle) wrote :

This bug was discussed at today's AIG meeting. The general consensus is that the original intent of this bug has been satisfied with blanket orders, but there are still specific use cases for standing orders that aren't addressed in current code and should get their own individual bug reports.

Once one or more other bugs have been opened to represent those workflows, I'll mark this bug as Won't Fix.

Revision history for this message
Lena Hernandez (lfhernandez) wrote :

Initial bug for standing orders has been submitted, Bug #2038551

Revision history for this message
Tiffany Little (tslittle) wrote :

Marking this bug as Won't Fix per comments #4 and #5.

Changed in evergreen:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.