Registering Pending Patron Screen Does Not Recognize Potential User Matches

[Erica Rohlfs]

Tested on EG staff client version 2.4.2. Feature not available until version 2.5

When loading pending patrons (Circulation -> Pending Patrons -> select a self-registered patron and click the Load Patron button), a new tab opens to register the pending patron. However, the pending patron registration screen does not recognize potential patron (user) matches that may already be in the database. This patron registration screen should be recognizing potential User matches. Please let me know if you need a more detailed example or screen images. Thank you!

[Terran McCanna (tmccanna)]

To expand on this bug...

If you have a Pending Patron open in the registration screen and you change the patron's name, it will then look for potential user matches.

However, if it finds a potential user match and you like on the 'Found xx patrons with same name' link, it opens a new tab but then fails with the following error message:

!! This software has encountered an error. Please tell your friendly system administrator or software developer the following: \npatron/display.xul\nSyntaxError: JSON.parse: unexpected character\n

This bug may be related to:
https://bugs.launchpad.net/evergreen/+bug/1365661

Tested on:
Evergreen 2.5.1 (PINES production) and Evergreen 2.6.2 (branch created from master on 8/26/2014)

[Erica Rohlfs (erohlfs)]

I tested Terran's workflow on version 2.6.2. I can confirm the behavior as described.

[Steve Callender (stevecallender)]

I just want to add that I have also just ran into this issue today on 2.6.1.

[Adam Bowling (abowling)]

I just pushed a patch for this. The index.xhtml file in .../xul/../server was missing a reference to the "JSON_v1.js" script. Adding that script reference solved this issue in the test environment.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=84300dde4230e0f78f67f1bdf91c7158d7831dc3

user/abowling/lp1243853_register_patron_match_fix

[Terran McCanna (tmccanna)]

I tested this and it solves the problem on bug #1365661 relating to new patron registrations, but it does not solve the problems here related to pending registrations.

I've removed the pullrequest tag here and added it to bug #1365661.

[John Yorio (jyorio)]

Just adding a note that this still the behavior in 3.1 web client.

[Steve Callender (stevecallender)]

This appears to still be an issue in 3.5.

[Jennifer Pringle (jpringle-u)]

In 3.9 Evergreen doesn't automatically check for duplicates when you load the pending patron but it does check if you click into any of the applicable fields.

Clicking on the link to the potential user match successfully opens in a patron search in a new tab and allows you to access the patron account.

So it looks like the outstanding issue is that Evergreen should check for duplicates on the fields when it loads the pending patron.

[Elizabeth Davis (elidavis)]

Once you have the list of duplicates, there's no easy way to merge them though, correct?