As a librarian I do not want username to be a required field in Folio Because a.) my patrons will never access Folio (only staff), b.) my institution uses another identifier to identify patrons (i.e. barcode) in our system(s).
In our existing database, we have people that have no username. I.e. they have a barcode, but, not a username. Would it be possible to make the username field not required? This isn't an issue with our current system (OLE) because there are separate people/patrons and users tables. If a person doesn't have a username, they are in the people table, but, not in the users table.
As a librarian
I do not want username to be a required field in Folio
Because a.) my patrons will never access Folio (only staff), b.) my institution uses another identifier to identify patrons (i.e. barcode) in our system(s).
Acceptance Criteria
Ensure backend no longer requires a username
Requirement validation
this requirement was validated at the March 13 2018 UM SIG meeting and August 27 2017 UM Meeting https://folio-org.atlassian.net/wiki/display/UM/2017-08-09+User+Management+Meeting+Notes
Univ of Chicago Feedback
In our existing database, we have people that have no username. I.e. they have a barcode, but, not a username. Would it be possible to make the username field not required? This isn't an issue with our current system (OLE) because there are separate people/patrons and users tables. If a person doesn't have a username, they are in the people table, but, not in the users table.