Bug 13978 - Add cancellation link to hold notification e-mails
Summary: Add cancellation link to hold notification e-mails
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-09 15:21 UTC by Christopher Brannon
Modified: 2020-06-26 21:09 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2015-04-09 15:21:00 UTC
It would be great if hold notification e-mails could include a button to click if a patron doesn't need the item any longer.  They could click the button to cancel the hold and notify the holding library.  All without logging into their account.

Christopher
Comment 1 Lisette Scheer 2018-09-12 17:04:40 UTC
This would be nice. We have people who try to e-mail us back, but the e-mail used is not checked regularly (we have a line in our notices that it isn't but people still try.) If they could cancel it the way Christopher described, that would be great. 
Lisette
Comment 2 Katrin Fischer 2020-01-06 15:48:19 UTC
I think achieving this without having to log in first is the harder bit, because you want a link that cannot be guessed and misused by someone else. You'd need a token or similar that only the email recipient and Koha know. A link into the catalog would be easier.
Comment 3 Christopher Brannon 2020-06-26 21:09:52 UTC
(In reply to Katrin Fischer from comment #2)
> I think achieving this without having to log in first is the harder bit,
> because you want a link that cannot be guessed and misused by someone else.
> You'd need a token or similar that only the email recipient and Koha know. A
> link into the catalog would be easier.

Maybe the token could be based on the reservation ID, or that and the borrower ID?