UI Customization (UXPROD-1732)

[UXPROD-3610] Provide Free-form "Full Name" or "Display Name" Text Fields for Users Created: 10/Mar/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: UI Customization

Type: New Feature Priority: TBD
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: notice_tokens, resourceaccess, usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3609 Provide Freeform "Full Address" Text ... Draft
Epic Link: UI Customization
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem:

Dealing with names is hard. The current method of collecting user information presents problems, particularly in the area of cultural inclusivity. We should provide an affordance in the FOLIO user record (and other forms that collect name information) to allow for free-form entry of full name and preferred name (not JUST preferred first name).

In scope

  • Update all data models in FOLIO that capture name information to include a dedicated "full name" and optional "preferred name" text field
  • Add this field as an available token in notices and staff slips where other name information is currently available
  • Update UI framework to handle/display this information

Out of scope

  • Validation of this field

Use case(s)

  • Deployment of FOLIO in cultural contexts where the patronymic naming system common in English-speaking countries is not used/common.
  • Better support for atypical names, honorifics, suffixes, etc.

Proposed solution/stories

  • In records that store names (eg. Users and Organizations), provide a data field that is meant for storing full representations of names ("full names"), formatted by the user who enters the data.
  • When displaying a textual representation of a given full name, this field should be used in lieu of concatenating the existing fields. This includes the FOLIO UI, as well as things like notice/staff slip tokens.
  • If names are searchable/queryable, this field should have a full-text index in the database.

Links to additional info

Questions

  • What can we do to improve the flexibility of fielded names in FOLIO?
  • Should the availability of this functionality be configurable? Should libraries be able to force the use of structured fields?

Generated at Fri Feb 09 00:33:23 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.