Web Client: Registering patron with same identification link broken

Bug #1712635 reported by Terran McCanna on 2017-08-23
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Medium
Unassigned

Bug Description

In 2.12.4:

When registering a new patron with a primary ID that already exists in the database, the "1 patron(s) with same identification" message appears, but clicking on it just makes it disappear without open a new tab showing the other patron.

(The alert link that goes to patrons with the same name works fine.)

tji@sitka.bclibraries.ca (tji) wrote :

The link on secondary ID is broken, too.

Andrea Neiman (aneiman) wrote :

Confirmed this in a very specific case on 3.0 beta

1) If the Primary Identification Type field is empty, and I enter a known duplicate value in Primary Identification, I see the behavior Tina describes where the alert message shows up but disappear without action when I click on it.

2) If any value is set in the Primary Identification Type, and I enter a known duplicate value in Primary Identification, clicking on the alert message works as expected and retrieves the matching patron. This is regardless of whether the Primary Identification Type is the same or different between the new patron and the existing patron. I think that Primary Identification Type is a globally required field (but correct me if I'm wrong) so it should be a rare occurrence that a new patron record is being entered without this information (and it should fail to save, which I understand is after the duplicate checking).

3) I was not able to reproduce the issue with secondary ID. I entered known duplicate values in Secondary Identification & in all cases I got the alert message and was able to click it to retrieve the patron. This was regardless of whether the value I entered in the new patron's Secondary Identification was in the existing patron's Primary or Secondary fields -- in either case I could retrieve the existing patron.

I'm marking it confirmed for the specific use case in #1 since it is a deviation from XUL behavior.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Low
Terran McCanna (tmccanna) wrote :

This is actually worse in 3.0.0 - now, I'm not even seeing an alert message if there is another patron with the same ID. (I was seeing the alert message in 2.12.4, but clicking on the link wouldn't pull up anything.)

Changed in evergreen:
importance: Low → Medium
Terran McCanna (tmccanna) wrote :

Tested on a fresh 3.0.0 server - I'm getting the alert message, but if I try to either right or left click on it, it disappears and doesn't go anywhere.

Andrea Neiman (aneiman) wrote :

Tested on demo.evergreencatalog.com (3.0.0)

I also now see that clicking on the alert message disappears with no further action ... but not consistently. There were times when I could get it to work normally.

The normal workflow would be to enter the value in Primary ID, and tab down to the next field. When I do this, the alert message that appears shows the disappearing behavior that Terran describes.

BUT! If I click back into the Primary ID Type box, the alert message reappears and is now clickable & will retrieve the expected search. Also, if I clicked from the Primary ID box into any field other than Secondary ID, the alert message would appear and would be clickable as normal.

So I'm not sure what the answer is, but something about tabbing/clicking into the Secondary ID field makes the alert message behave wonkily.

Terran McCanna (tmccanna) wrote :

Still wonky in 3.1

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers