Bug 39263 - When an ILL request is closed the item and biblio record created for it should be deleted
Summary: When an ILL request is closed the item and biblio record created for it shoul...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ILL (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-06 08:37 UTC by Mathieu Saby
Modified: 2025-04-30 23:32 UTC (History)
5 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Saby 2025-03-06 08:37:49 UTC
When an ILL request is closed (I mean the document has been returned to the supplying library) the item and biblio record created for it should be deleted, either in real time (better I suppose) or with a script in cron

They were only created to enable the document to be checked out to the patron.
If we don't remove them, they will pollute the catalog.
Comment 1 Katrin Fischer 2025-03-06 09:11:25 UTC
We have implemented this in our backend. For sending notices we need the articles to stay around a little longer and delete them with a cron script (the nightly plugin one actually). 

I think libraries might want to handle this differently, so a cron with a configurable duration might be the most flexible solution.
Comment 2 Mathieu Saby 2025-03-06 10:40:56 UTC
I see you have implemented a lot of good ideas in your backend. the second in 2 days ;-)
Comment 3 Mathieu Saby 2025-03-06 10:43:53 UTC
I was thinking of a windows like we have when we delete the last item of a record ("This request is closed, the record and item are now useless, do you want to delete them?"). 
But clearly in my library we will want to delete it automatically without bothering to answer to that...
Comment 4 Katrin Fischer 2025-03-06 10:59:30 UTC
A lot of "nice" information for the notices is in the record, so we want to delete after we are sure there will be no more letters to create :) We are quite happy with the backend indeed :D
Comment 5 Mathieu Saby 2025-03-06 14:01:20 UTC
What notices are you thinking of?
Comment 6 Katrin Fischer 2025-03-06 15:10:32 UTC
(In reply to Mathieu Saby from comment #5)
> What notices are you thinking of?

I am trying to remember. I think it was re-printing some kind of slip for the article requests. The article requests get checked out and then immediately returned again, so the system knows they have been picked up/handed out. I'll try to remember the exact issue.
Comment 7 Alexander Wagner 2025-03-12 08:10:21 UTC
As there are some use cases to keep the records around (especially if they were pimped up using some SRU imports so you have decent data) an option could be to move them into some "shadow catalogue" instead of deleting them entirely.

Then they don't pollute the main OPAC, but would still be around for some time and the clean up could be more lazy.

(I am also imagining situations where we might learn that some subject is on higher demand e.g.)