Ability to capture the invoice number, price, date of a subscription without creating the items records. This bug depends on bug 8415
Created attachment 10932 [details] [review] Capture the invoice number, price, date of a subscription Create an order using a subscription. This order is different from regular orders in that it is for a serial subscription, not for a book. When receiving, the item add function does not work as it does in the case of books. Here no item is added since items are added from serials module. But invoice, invoice date, actual cost is captured when receiving. Two cases here: 1) Systempreferences "AcqCreateItem" is set to "receiving an order" When receiving this message is displayed instead of the usual add item fields -- "This order is for a serial subscription. Items are added in the serial module." 2) Systempreferences "AcqCreateItem" is set to "placing an order" When ordering this message is displayed instead of the usual add item fields -- "This order is for a serial subscription. Items are added in the serial module." this bug depends on 8415
Patch applies and I started testing it. What irritates me is the fact that it allows to enter a quantity >1. At the moment for each copy of a serial we have to add 1 subscription in the serials module. So to me it seems like an order linked to a subscription should only allow to order 1 copy of the serial. It's not ideal that we have this 1:1 relationship between copies and subscriptions at the moment, but while it's still the case it would probably be better to reflect it in acq? Or is there a workflow I am missing?
Also it seems that the initial feature from Biblibre solves this differently: http://git.biblibre.com/?p=koha;a=blobdiff;f=koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tmpl;h=e0d802bf0753c71683dda1f595905d11030648b5;hp=8135154960e9e5e2df6eea1c72100462a99941d5;hb=4d3255f90c0845e68904ba835c0bbc3cb289e2ad;hpb=c6d5309fe041567595d3f6144b1c94398135371f
Hi Amit, I proposed the original patch of this feature in Bug 5343. Given that it was easiest to me to recreate a new patch from scratch and the patch I proposed do the same thing as your one, I mark this bug as duplicate. *** This bug has been marked as a duplicate of bug 5343 ***