Purpose: We want to line up the UI elements with the API names. The SIG had originally defined "User ID" as the name for the login ID but on the back end it was implemented as "username". Because changing the backend is difficult, the SIG has agreed to change the front-end label.
Acceptance Criteria:
Change "User ID" to "Username" wherever it displays in Users:
I'm about to do this; but it does strike me that aligning user-facing names with what we happen to use to implement them under the hood seems like a very odd thing to do. There are lots of places where these two sets of name diverge – e.g. "Patron Groups" in the UI are provided in a usergroups member of the FOLIO WSAPI response. Isn't it better to align UI names with what users expect to see?
Purpose: We want to line up the UI elements with the API names. The SIG had originally defined "User ID" as the name for the login ID but on the back end it was implemented as "username". Because changing the backend is difficult, the SIG has agreed to change the front-end label.
Acceptance Criteria:
Change "User ID" to "Username" wherever it displays in Users:
User details view mode (preview pane)
User details edit mode
User details create mode
User app search results
Anywhere else you can find?