Patron Notices (UXPROD-18)

[UXPROD-3052] Use Notice Tokens in Subject Lines for Patron Notices Created: 26/Apr/21  Updated: 15/Aug/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: julie.bickle
Resolution: Unresolved Votes: 1
Labels: enettifee-reviewed, notice_tokens, patron_notice
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Patron Notices
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R3

 Description   

Current situation or problem: Libraries would like to be able to use tokens in subject lines for patron notices - for example, to insert the due date for an item, or to notify a patron that they have been charged a fine. Being able to put this information in a subject line makes it more likely that a quick scan of email by a patron will result in them seeing important information.

In scope

Out of scope

  • Making tokens available in the subject line that are not already available for us in the email body.

Use case(s)

  • Libraries send a courtesy notice to a patron with a subject line of "Reminder - your items are due on loan.dueDateTime". When the notice is sent, the due date is auto-populated.
  • Libraries send a lost item notice to a patron with a subject line of "Attention: your library loan of item.title is now considered lost and you have been billed feeCharge.amount". Including the amount in the subject line makes it more likely that a patron will react to the email and return the book.

Proposed solution/stories

Links to additional info

Questions

  • What would determine the values to use in a subject line if there are multiple items in the notice?
  • Are there some tokens that simply don't make sense to put in a subject line, or can we assume that all notice tokens are valid for a subject line?


 Comments   
Comment by Erin Nettifee [ 26/Apr/21 ]

Darcy Branchini julie.bickle - Darcy, I know we discussed this a bit over Slack a while ago. I haven't seen a feature go in, so I went ahead and created one to get at least the initial discussion captured. Thanks!

Comment by Erin Nettifee [ 11/Jul/22 ]

julie.bickle I went ahead and assigned this to you, it was still assigned to Darcy.

FWIW, when we are able to get to this point, ReShare developers have figured out how to do this. The default reshare pull slip notice has a token in the subject line. So it will be worth collaborating / looking at their code when that happens so people hopefully don't have to start from scratch.

Comment by julie.bickle [ 11/Apr/23 ]

Hey Erin Nettifee , a little while ago a colleague in Bavaria noticed that this feature actually already seems to work.
I had updated this Wiki page accordingly, but had forgotten that there was a feature about it.
Could you please confirm whether this feature is still needed, or whether there are requirements are that still not met?

Comment by Erin Nettifee [ 11/Apr/23 ]

Thanks julie.bickle - when I had discussed this need with Darcy, she had indicated it hadn't been implemented, which is why I submitted it.

I did some brief testing as we discussed over Slack. I do see tokens sometimes working and sometimes not (in the subject line), primarily I think because of the multiple loans logic.

It's likely to mean that we should not assume that all tokens could be used in a subject line, and so we need to indicate which ones would work and which ones wouldn't - maybe with an icon or graphic indicator.

Comment by Brooks Travis [ 25/Apr/23 ]

While it's probably not wise, you could use them if you include the #loans /loans construct in the subject line around the item information. I think we can probably close this as Duplicate. It apparently got handled somewhere.

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