Users App (UXPROD-784)

[UXPROD-1790] Preferred name on user records and display thereof Created: 24/Jun/19  Updated: 14/Dec/21  Resolved: 10/Aug/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Users App

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: patty.wanninger
Resolution: Done Votes: 0
Labels: round_iv, users
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODUSERBL-101 mod-users-bl does not recognize field... Closed
is defined by MODUSERS-196 BE - Preferred name field on user record Closed
is defined by UIU-1649 Preferred first name field on user re... Closed
Relates
relates to MODUIMP-15 Support loading Preferred first name ... Closed
relates to STSMACOM-615 Add preferred name to the Proxy Modal Closed
relates to UIREQ-605 Add preferred name to Requests UI Closed
relates to UIU-1767 Users App: Search preferred first name Closed
relates to UXPROD-1812 Suffix on user record Closed
relates to UXPROD-1813 Honorific on user record Closed
Requires
is required by UICHKOUT-699 Add preferred name to check out UI Closed
Epic Link: Users App
Development Team: Spitfire
PO Rank: 18
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Periodically (frequency will vary by country/culture), a patron will have a preferred name ("nick name") that differs from their first name. Some patrons will want to specify a preferred pronoun (https://en.wikipedia.org/wiki/Third-person_pronoun#Preferred_pronouns), as well.

These patrons would like to be addressed according to the above name and/or pronouns in verbal and written communications and FOLIO doesn't currently support the collection or use of these name preference fields.

Use cases:

  1. Circ staff should call patron by preferred names and pronouns when interacting during check in or check out at circ desk
  2. Patron notices should refer to patron by preferred names and pronouns
  3. Other?

Current thinking on design: https://drive.google.com/file/d/1ZUNHUrCouLXV-P_F04EY_QVT9m3iMMqH/view?usp=sharing

This feature was raised at the June 2019 FOLIO face-to-face meeting in DC: https://docs.google.com/document/d/14mqzLFvKmuctNCQFlXJamuXDdKSZZX1rN5kMI4v_8aY/edit



 Comments   
Comment by David Bottorff [ 09/Jul/19 ]

Chicago could wait up to a year.

Comment by Brooks Travis [ 19/Feb/20 ]

Sorry to be late to this, but I think this needs to be prioritized for completion ASAP. A potential workaround would be custom fields with some ability to use logic in notification templates to determine which token to use in a particular situation. We don't need FOLIO deadnaming folks in notifications and the patron empowerment UIs, and it would be helpful to our staff to have indicators for preferred name and pronouns in the staff UI.

Comment by Brooks Travis [ 19/Feb/20 ]

We have a significant number of community patrons who won't be in our ERP/IdM feed(s), and we need the ability to record and use their preferred names in the staff UI, PE, and notices. It was somewhat excusable that this wasn't a feature in our current ILS, but there's no real excuse for it in FOLIO. I would make the case for creating something like an “Effective Display Name”, similar to the computed fields in Inventory, along with setting that allows you to template it, a la tokens in notification templates.

Comment by Cate Boerema (Inactive) [ 06/May/20 ]

We have a significant number of community patrons who won't be in our ERP/IdM feed(s), and we need the ability to record and use their preferred names in the staff UI, PE, and notices

Hi Brooks Travis, in the case of community patrons, could you record the preferred name in the existing First name field? For patrons that exist in the ERM/IDP, could you direct them to have their name changed in that system? I'm just trying to understand the constraints here.

Unfortunately, calculated "effective" fields typically require a significant amount of development effort. It would be more straightforward to allow the capture of a preferred name (via a dedicated or custom field) and the ability to tokenize it for use in patron notices. Getting the preferred name to display throughout the FOLIO UI would be more complex.

Comment by David Bottorff [ 11/Mar/21 ]

Was a separate Jira ever spun off to allow display of the preferred name field in the checkout app? If that could be added in addition to the first name field, at a minimum, it would seem easier than requiring logic that displays it instead of the first name field. But having preferred name display only in the user record is relatively useless from a customer service perspective

Comment by patty.wanninger [ 11/Mar/21 ]

I am drafting those stories, David Bottorff. The User Management SIG wants the last name, preferred first name to appear in Checkout and anywhere else a staff person is presented with a patron's name. The "legal" first name would only appear in the user record. I'll append the number here after I create the ticket.

 

Comment by David Bottorff [ 11/Mar/21 ]

Great, thanks Patty!

Comment by David Bottorff [ 19/Mar/21 ]

patty.wanninger As part of drafting the stories around preferred name, it just occurred to me that we would want these released via APIs as well, so that discovery layer, self checkout (sip2, etc.) could leverage the preferred name field. Just as or even more important than the staff UI, since it's what the patrons will actually see!

Comment by patty.wanninger [ 19/Mar/21 ]

Good point, David Bottorff. I wonder if we need the concept of "effective patron name" so it would be everywhere.

Comment by David Bottorff [ 25/Mar/21 ]

That’s an interesting idea, ,patty.wanninger, and might provide greater long term flexibility for populating the effective name string wherever it needs to be. 

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