Looking at late orders, we still have some orders that are "open" but they relate to deleted bibliographic records. It is not clear anymore how that exactly happened. I can only "Edit" the order (change delivery date). But I just want to cleanup here.
Similarly: How to reproduce this, not clear now. But I have quite a bunch of orders that have no biblionumber, no deleted biblionumber, orderstatus ordered and a filled datecancellationprinted. The system only allows you to edit the delivery date.
Hi Marcel, this is a duplicate I think - there are multiple issues with deleted records and acquisition orders. I'd love to work together on solving these. The way to create a problem goes like this: * Order something, receive it, etc. * Delete the bibliographic record from the catalog. Until bug 33262 that created entries in aqorders with no biblionumber left. Now we keep the connection with a new column deleted_biblionumber, but we are not making use of it yet. For other bugs see: * Bug 10869 - Can't cancel order line if title deleted * Bug 10758 - Show bibliographic information of deleted records in acquisitions * Bug 27893 - Delete of biblio with order does not always warn I believe we cannot tell people to not delete records, because items bought might also be removed from the library at one point, but we still need to allow the library to keep track of these for accounting/auditing purposes on how money was spent.
I thought that I saw an orderline with date cancellation too in the first table. But I cant reproduce.. Code seems to be fine.
Another observation: Open basket, order with deleted biblio. Can place a hold on that record!? The link contains no biblionumber..
(In reply to Marcel de Rooy from comment #4) > Another observation: Open basket, order with deleted biblio. Can place a > hold on that record!? The link contains no biblionumber.. https://master.rijkskoha.nl:28443/cgi-bin/koha/reserve/request.pl?biblionumber= Fun
(In reply to Marcel de Rooy from comment #3) > I thought that I saw an orderline with date cancellation too in the first > table. But I cant reproduce.. Code seems to be fine. We have seen this with orders in any state. I think it's always possible to overwrite the warning and delete the bibliopgrahic record somehow. Maybe also need to think of batch record deletion/batch item deletion with 'delete record' checkbox set. (In reply to Marcel de Rooy from comment #5) > (In reply to Marcel de Rooy from comment #4) > > Another observation: Open basket, order with deleted biblio. Can place a > > hold on that record!? The link contains no biblionumber.. > > https://master.rijkskoha.nl:28443/cgi-bin/koha/reserve/request. > pl?biblionumber= > > Fun I'd say this is a separate bug to report, but overall we need better handling for the "deleted record" case. Did you see the earlier comment and bugs?
Created attachment 161884 [details] [review] Bug 36030: acqui/basket: Do not place hold on deleted biblio Trivial fix. Test plan: Find a deleted biblio record in ACQ (in active orders part) and verify that there is no Place hold option on that row. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
(In reply to Marcel de Rooy from comment #4) > Another observation: Open basket, order with deleted biblio. Can place a > hold on that record!? The link contains no biblionumber.. Added a fix for this now along the way.
(In reply to Katrin Fischer from comment #6) > Did you see the earlier comment and bugs? Yes, thanks! Added few comments on the 10869. Awaiting comments there.
Okay. I am changing title here. The original 36030 is a duplicate. Continue that discussion on 10869. I am moving this one to "Do not show Place hold for deleted biblio".
This is a very trivial patch. Self SO.
Created attachment 163724 [details] [review] Bug 36030: acqui/basket: Do not place hold on deleted biblio Trivial fix. Test plan: Find a deleted biblio record in ACQ (in active orders part) and verify that there is no Place hold option on that row. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov>
Pushed for 24.05! Well done everyone, thank you!
Pushed to 23.11.x for 23.11.06
Doesn't apply cleanly to 23.05.x, no backport.