[UXPROD-4603] Add Pronoun Field to User Record Created: 18/Dec/23 Updated: 20/Dec/23 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Amelia Sutton | Assignee: | Amelia Sutton |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | usermanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Development Team: | Volaris | ||||||||
| PO Rank: | 0 | ||||||||
| RCA Group: | TBD | ||||||||
| Description |
|
Current Situation and Purpose: Currently, libraries can use custom fields to store a user's pronouns. However, because those fields are displayed under the custom field accordion, and are not visible without expanding the accordion, the information is not visible at a glance. In scope
Out of scope
Use case(s)
|
| Comments |
| Comment by Amelia Sutton [ 18/Dec/23 ] |
|
I think more discussion is warranted to decide the type of field pronouns should be. In discussion with the UM SIG there was interest in a configurable list of values for the field. There was also interest in allowing some kind of ranked-multiselection for pronouns.
I'd also like to note my hesitance around the proposed additional functionality to add pronouns as tokens for notices as it could add new layers of complexity to notice templates to adapt verb conjugation to match pronouns. |