Preferred Name should be the prominent display name

Bug #1924185 reported by Christine Burns
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.5
Fix Released
Medium
Unassigned
3.6
Fix Released
Medium
Unassigned

Bug Description

Wishlist request

EG 3.5+

If patron preferred name values are entered these should be prominently displayed in the patron summary.

Currently the patron preferred name appears in smaller font under the legal name.

If patron preferred name values are entered these values should be used as the main display name in patron summary.

Revision history for this message
Christine Burns (christine-burns) wrote :
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Agreed -- preferred name is what we need prominent for customer service work.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Shula Link (slink-g) wrote :

Agreed; preferred name should be the default for most staff interactions.

Changed in evergreen:
importance: Undecided → Medium
tags: added: patron
description: updated
Revision history for this message
Terran McCanna (tmccanna) wrote :
Revision history for this message
Elaine Hardy (ehardy) wrote :

I think it should also display prominently in the user account to assure the patron that the preferred name is dominant else where.

Changed in evergreen:
assignee: nobody → Jeff Davis (jdavis-sitka)
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Working branch user/jeffdavis/lp1924185-prominent-preferred-name has two relevant commits:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeffdavis/lp1924185-prominent-preferred-name

The first commit uses the preferred name (when available) as the prominent display name in the patron summary, and moves the official/legal name to an "Official Name" field just below the ID fields. We could go further and hide the official name field by default, since staff don't need it for most transactions and patrons may not wish their legal name to be plainly visible.

The second commit uses preferred name rather than legal name in the top nav bar when logged into the Bootstrap OPAC, and puts the preferred name before the legal name in My Account preferences in both Bootstrap and TPAC.

Changed in evergreen:
assignee: Jeff Davis (jdavis-sitka) → nobody
tags: added: pullrequest
Changed in evergreen:
milestone: none → 3.7.1
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

I've targeted this to the next round of point releases, since our libraries who use the preferred name field consider the current behavior to be a bug.

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

I tested this on our 3.7 test server and it works as expected in both the patron edit and My Account in the TPAC. (We are not currently using Bootstrap so I have not tested it there.) We're planning to start using this fix on our live servers later this month.

I'm not signing off because I'm from the same organization as Jeff and the patch should be tested by someone outside of Sitka.

Michele Morgan (mmorgan)
Changed in evergreen:
assignee: nobody → Michele Morgan (mmorgan)
Revision history for this message
Michele Morgan (mmorgan) wrote :
tags: added: signedoff
Changed in evergreen:
assignee: Michele Morgan (mmorgan) → nobody
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Thanks, Jeff, Jennifer, and Michele! Pushed both commits to rel_3_6, rel_3_7, and master. And the first commit only to rel_3_5, since the second commit includes some bootstrap opac-specific stuff.

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.