webclient: undelete is subject to weird possibly caching-related issues

I ran into it last night. I undeleted a record in the web client, but could not clear the "deleted" labeling in the OPAC view. I tried searching for the Record ID in a new tab, but got the same "deleted" message.

I'll add more the next time I run into this.

Possibly related to bug 1778314 ?

We are currently on webclient 3.2.5. I ran into this issue this week. I undeleted a record on Tuesday afternoon. It still showed the red box around the title saying it was deleted, even though the MARC editor showed it as undeleted (and I could delete it again). I added a copy back to the record, refreshed many times, and it still showed in the OPAC view as deleted and I could not see the copy information there. Our System Admin and I tried a bunch of things, editing the LDR to change the code "d" back to "n" or "c", etc., with no success.

We decided that maybe we were waiting for some process to run later/overnight before it would change. I went on to do a search that would include this title, because I needed to work on a related project. The undeleted title came up first in my search, and when I clicked on the title, the record was visible in the OPAC view with no red box, etc. I assumed that whatever we were waiting for to happen had done so.

Today I had to access that record again. I scanned the barcode into the item status, and said show in catalog. The red box was back showing deleted again. I checked the holdings view and the item was still there. I went over to ask our System Admin what to do now, and he brought the record up by TCN number, and it did not appear as deleted to him. He then went and searched it in the OPAC and it still did not show as deleted.

I came back to my desk and told a coworker about it. She searched it by TCN and it did not appear deleted to her.

I opened a new tab on my computer, used the TCN search and it still showed deleted for me.

In another tab I searched it again by title, and it does NOT show deleted for me.

In yet another tab I put the TCN number into an advanced keyword search and it also did NOT show deleted.

In another tab and put the TCN into the home screen search, and it did NOT show deleted.

I am not sure how it is caching it to cause this difference depending on how the search is performed but it must be. I work in Chrome, so I created a new workstation in Firefox, and I didn't get the red deleted box at all regardless of the search, so it isn't somehow tied to my login or workstation. I don't know if this will help anyone troubleshoot it, but I wanted to offer the example in case it does.

We are now on 3.2.7. I noticed about a month ago that I was no longer able to undelete records at all. The green popup window appears in the lower right saying the record was successfully updated, but the "undelete" button flashes to "delete" and then goes right back to "undelete". I asked our system administrator, and he was not able to undelete the record either. I have tried a few times since then, including today, and the same behavior happens no matter what record I attempt to undelete.

We have 3.4.2 on our test server and I am notable to undelete a record.

When the record was deleted, the TCN switched to the record ID number rather than retaining the OCLC based TCN.

I tried overlaying the record and the deleted label was still on the record and it couldn't be retrieved with the TCN search.

If I attempt to undelete the record from MARC edit after I have overlaid to get the correct TCN, the TCN flips to the record ID and still remains deleted (even if I save the record as well)

PINES is seeing the change in TCN for all edited record in 3.4.2 so this probably is not related to undelete

The TCN change issue is addressed in bug 1859191.

SCLENDS can also confirm. We're on 3.3 (3.3.5, as I write this), and I can confirm this behavior. I'm not able to undelete a record and see the same behavior Chrisy describes: when I select "undelete," I get a "record successfully updated message." And then the "delete" very quickly reverts to "undelete."

It does intersect with the TCN change issue in bug 1859191, in that I was trying to restore records with an OCLC based TCN. When the TCN flips to a non-OCLC number, I'm hard-pressed to track down the record that needs undeleting.

Two different issues, but they don't play well together!

See also duplicate bug 1892511, which has some useful info