Some libraries would like to be able to restore items accidentally deleted. This should be possible, rows can be copied over as long as there are checks in place for unique ids.
This is a great idea.
Agreed! I've heard interest in this feature from other libraries.
I have written this code already and would like to add the feature.
(In reply to davewood from comment #3) > I have written this code already and would like to add the feature. If you haven't already, take a look at the following: https://koha-community.org/get-involved/for-developers/ If you need help attaching patches, I'd suggest hopping on IRC or the Koha Developers List: https://koha-community.org/support/
We'd be also interested in this. Items seem a little less complicated, maybe they would make a good starting point.
*** Bug 13556 has been marked as a duplicate of this bug. ***
Yes, this should be a core feature! Maybe the InLibro Plugin is a good start ? https://github.com/inLibro/koha-plugin-undelete-records
(In reply to Michaela Sieber from comment #7) > Yes, this should be a core feature! > > Maybe the InLibro Plugin is a good start ? > > https://github.com/inLibro/koha-plugin-undelete-records I ended up using this as inspiration for a pure SQL undelete for 1 bib record (and attached items) I needed to undelete. I should look at biblio_metadata again, as it seems that the ID wasn't able to be restored. Had to use a new ID... which is reminiscent of that autoincrement bug. Hmm... it was an old database. (I noticed the InLibro code also gets a new ID for restoring biblio_metadata, so must be a more common issue?)
Of course, "undelete" only works for the bib record and items themselves. Other tables using foreign keys will have cascading deletes. So the data in the "linktracker" table for instance cannot be restored. It's permanently deleted. Given how many people seem to accidentally delete things... I reckon that soft delete feature would be handy. (Of course, it would be a mountain of work to refactor Koha to handle soft deletes...)
Plug-in for InLibro also doesn't work for 24.05. :( We are still getting a lot of request about this from libraries.
Some sort of undelete function would be great. However, I can just pull the record from an old backup of our catalog. Thankfully I've not needed to do this very often.