Add unique constraint for user externalSystemId
Description
CSP Request Details
CSP Rejection Details
Potential Workaround
relates to
Checklist
hideTestRail: Results
Activity
Marc Johnson February 28, 2022 at 4:53 PM
I have closed this because it is my understanding that the awaiting release status is only to be used for issues that require back porting. And as far as I can tell, this issue does not require back porting for 2022 R1.
Julian Ladisch February 18, 2022 at 8:31 PM
: Yes, please create that story. In addition there should be a catch-all handler for unexpected back-end errors () that is ugly but better than nothing.
patty.wanninger February 18, 2022 at 8:01 PM
This feature needs a little red "This external system ID already in use" or something like that. In snapshot now, you can't save a duplicate ID and there isn't any message. Should I write a separate story?
Julian Ladisch February 15, 2022 at 2:33 PM
The pull request has been merged and the fix awaits a mod-users release.
patty.wanninger February 4, 2022 at 6:36 PMEdited
and In trying to rank , we discovered that this ticket has an unmerged pull request. What is the status of this pull request.
Details
Details
Assignee
Julian LadischReporter
Jon MillerPriority
P2
FOLIO is allowing more than one user to have the same externalSystemId. This field is missing a unique constraint. Please add one like the existing ones for barcode and username.
The Check-Out settings allow to use the external system id as a unique patron identifier: https://folio-snapshot.dev.folio.org/settings/circulation/checkout
If external system id is not unique the check-out will pick one of the multiple matches without any warning that it might be the wrong patron.
The upgrade will fail if existing patrons have non-unique external system id with an error message containing the duplicate value. This is mentioned in the https://folio-org.atlassian.net/wiki/display/REL/Lotus+%28R1+2022%29+Release+Notes
There is no automated way to fix duplicates during migration therefore the failure is the only option we have.
See also https://folio-org.atlassian.net/wiki/display/UM/2021-02-17+Meeting+Notes