Comment 9 for bug 1748464

We are currently using 3.1.6 and had a question about retrieving a patron account with two different barcodes from a recently migrated library. When I tested in the web client, I was able to retrieve the account with the inactive barcode (both by patron search and using the checkout function) without any alert message displaying in either case. The checkout entry box was active for checkout, so there was absolutely no indication that the account was retrieved with an inactive barcode.

This does not replicate the behavior in the XUL client, as other have noted. In XUL, there is an alert message and the checkout entry box is grayed out and not usable.

There are good discussions of the reasons for maintaining a record of inactive barcodes in the patron account while notifying staff that the barcode may be in possession of an unauthorized person here: http://masslnc.org/node/2985 and here: https://bugs.launchpad.net/evergreen/+bug/1154235