Inactive Barcode Alert Doesn't Consistently Display in Web Client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Evergreen 3.0.3
I'm not sure if this is a possible bug or more of a possible enhancement.
Here's the steps to reproduce:
In the web client, use an inactive barcode to retrieve a patron with no standing penalties or other alerts.
The first time you'll go to the /alerts page:
"Patron account retrieved with an INACTIVE card. Press a navigation button above (for example, Check Out) to clear this alert."
Repeat the search with the same, or a different, inactive barcode for the same patron: no alert.
I expected to see the alert each time.
Clearing the browser cache brings the alert back.
In the XUL client, when searching for a patron using an inactive barcode, the alert comes up as expected even with successive searches of the same inactive barcode.
It seems like it would be helpful if the web client behaved the same way.
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: patron |
John, does this still happen if you search for and load a different user between the two searches for the same user via an inactive barcode? Does simply hard-refreshing (shift-reload) the page between the searches make the alert work as expected? If those are true, I suspect this is happening because the user object and state info are cached in (probably) the patron service, so the alert page is marked as already "seen" for the current user. If that's the case, I'm not surprised that the alert doesn't show on the second search+selection of the same user with an alert. And, if that's the case, I'm not sure that's a bug since the client has already alerted the staff to the, um, alert. I'd think of that as an enhancement over the XUL version, but would like to hear front-line opinions!