Patron Notices (UXPROD-18)

[UXPROD-1831] Tokens - Add additional USER fields to patron notices Created: 27/Jun/19  Updated: 17/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Patron Notices

Type: New Feature Priority: P3
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 1
Labels: IC_review, LC-priority3, loc, notice_tokens, patron_notice, requires-discussion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-3767 Add "Discovery display name" as notic... Closed
defines UXPROD-3769 Add "Preferred first name" as notice ... Closed
Relates
relates to MODUSERS-196 BE - Preferred name field on user record Closed
relates to UIU-1649 Preferred first name field on user re... Closed
relates to UXPROD-1830 Add additional USER tokens to staff s... Draft
Epic Link: Patron Notices
Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Volaris
Kiwi Planning Points (DO NOT CHANGE): 6
PO Rank: 15
PO Ranking Note: Additional fields not yet available on user record.
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose/Problem:
User token options for patron notices include first name, last name, middle name and barcode. FOLIO number, external system ID, and username, are available today (6/26) on the user record. Additional fields are expected to be added to the user record, such as honorific, suffix, and other identifiers. Those should also be included as token options when they are available.



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

Chicago can wait up to a year.

Comment by Molly Driscoll [ 30/Nov/21 ]

julie.bickle do we have a timeline for development of this feature? It's being requested by more and more libraries that would like to leverage the preferred first name token on records where it is present. 

Comment by julie.bickle [ 01/Dec/21 ]

Molly Driscoll I aim to have my features around tokens groomed before my Xmas break. 

Comment by Molly Driscoll [ 01/Dec/21 ]

Thank you, julie.bickle!

Comment by Khalilah Gambrell [ 08/Sep/23 ]

Hey Anne Ekblad and Stephanie Buck is this issue still a LC priority 3?

Comment by Anne Ekblad [ 08/Sep/23 ]

Hi, Tim Auger and Irina Pokhylets. What are your thoughts related to Khalilah Gambrell question? cc Stephanie Buck and julie.bickle

Comment by Marie Widigson [ 10/Oct/23 ]

Not sure if an anonymous user ID is also part of this Jira? If so, it's a very high priority for Chalmers.

Comment by Irina Pokhylets [ 17/Jan/24 ]

Hi,
Anne Ekblad, sorry for the late response.  

Regarding LC priority 3, it depends on whether LoC requires tokens: FOLIO number, external system ID, and username for patron notices. Because tokens for first name, last name, middle name and barcode already exist. Other fields, described in the ticket, have not yet been added to the used record.

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