Created attachment 123213 [details] Accounting details to add an order When adding orders to Koha, it would be nice to be able to track certain dates for our orders, such as the date when the item is requested. We would like to track the time from when the item was requested, ordered, and then received. A requesteddate field could be added to the aqorders table and a text field in the accounting details when adding the order.
Hi Michael, can you explain the difference between requested and ordered in your workflow?
The requested date is when a patron submitted the request. We receive and approve patron requests from several different platforms and not just the purchase request form in Koha. We might receive them via a librarian liaison, for example. Since that is the case, we do not currently have a way to keep track of when a request was submitted, except through an excel spreadsheet. It would be time consuming to enter a purchase request while at the same time creating an order. Therefore, it would be simple to add a 'requested date' - when the item was requested - to the order when it was created. aqorders already has date fields in it, such as the budgetdate - according to the database schema it says budgetdate - 'not used? always NULL' - perhaps something like that could be recycled into a requesteddate? But, the order form itself does not have a text or date field for a date, as you can see in the attachment.
Thx for explaining! I guess if it comes from a suggestion the field could be pre-filled and manually updated otherwise?
(In reply to Katrin Fischer from comment #3) > Thx for explaining! > > I guess if it comes from a suggestion the field could be pre-filled and > manually updated otherwise? Yes, purchase requests utilizing Koha's suggestion form, pre-filling the date on the submitted form would be beneficial. When we create an order from other purchase requests not using Koha's purchase suggestion form, we would need to manually enter a date requested. As an FYI, we use this data for strategic goals and planning for Collections & Technical Services with Demand Driven Acquisitions (DDA) to show turn-around times between when requests are made and when they're fulfilled. Thus far, this data collection is all manual.
Hi Michael, we have custom fields for order lines now, maybe they could be used?