If records are staged with the item rule: Replace items if matching bib was found (only for existing items) And some items are successfully updated those items are deleted when you click: Undo import into catalog.
I think the item values from before the update are not stored anywhere, os it might be a problem turning them back... maybe what we could do for now is print a big warn?
Is this report specific to 3.18.x? If it is valid in master, please mark it as such.
I wonder if we store if the item was added or replaced - if it was replaced, we could keep it and only delete it if it was added. Would still need a big note somewhere and documentation.
Although a big warn would certainly be helpful, it would be better to get it fixed (so undo could happen). We are on elastic search. Warn should include advising to keep a marc file of the previous state of affairs to load to recreate the items that disappeared.
This is still true and still bad.
I am raising severity as this is about data loss.
Checking on the status of this Bug. As Katrin noted, this is about data loss.
I agree. It erases data. From an acquisitions standpoint, I need to add the item back on to the Bib record and input the item information again. It seems like the reversion should simply "undo" the process.
After a discussion in the koha-US acquisitions SIG, we determined that this bug is negatively impacting a number of libraries. This bug is deleting item records when the import is undone.