Provide An Indicator/Warning When Order Has Already Been Sent to a Vendor
This is a resubmission of a just-expired idea from Jeremy G.:
In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.
As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2) highlight any orders in red or blue where a sent message already exists in an ISBN pick field, similar to how duplicate invoices are colored in the import invoices function.
The second potential piece of this would be to generate a pop-up message along the lines of "File contains previously sent orders, do you wish to proceed?" that would appear at the point where the individual orders are packaged together into a single file for uploading to the vendor. That message would allow staff the opportunity to back out if they wish and remove any offending orders before proceeding.
Shawn P. Farrell
shared this idea
-
MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• Orders displayed in the “purchase orders to FTP” queue will include an order sent column to show the order has already been sent to a vendor.
• Sent orders can be highlighted on the display in a user-defined color according to a user preference.
• If orders that have been sent are selected to send again, a pop-up message containing the text "File contains previously sent orders. Do you wish to proceed?" appears when individual orders are packaged together into a single file for uploading to the vendor.
• The message allows the staff member to back out and remove any previously-sent orders before proceeding or continue.
• The text of the pop-up is internationalized so it can be translated into multiple languages. -
Lisa Bondy
commented
Any step to help prevent accidental duplicate ordering would be a benefit to libraries who use this ordering method.
-
Kim
commented
This would be extremely helpful!
-
Deena Zuckerman
commented
This is so important to avoid spending money on what is not wanted, and to avoid receiving more books than fit in a collection.
-
Alan Long
commented
We've had multiple issues with duplicate orders being sent. This would be so helpful in terms of preventing that. It would also prevent us from wasting unnecessary funds on duplicate orders.
-
Jeremy Goldstein
commented
In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.
As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2) highlight any orders in red or blue where a sent message already exists in an ISBN pick field, similar to how duplicate invoices are colored in the import invoices function.
The second potential piece of this would be to generate a pop-up message along the lines of "File contains previously sent orders, do you wish to proceed?" that would appear at the point where the individual orders are packaged together into a single file for uploading to the vendor. That message would allow staff the opportunity to back out if they wish and remove any offending orders before proceeding.
