Bug 24730 - Allow patrons to cancel waiting holds in OPAC
Summary: Allow patrons to cancel waiting holds in OPAC
Status: RESOLVED DUPLICATE of bug 22456
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-25 17:37 UTC by Christopher Brannon
Modified: 2020-03-15 22:15 UTC (History)
4 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 2020-02-25 17:37:20 UTC
Currently, patrons cannot cancel a hold that is triggered (waiting).  It would be great if a patron had this ability.  Staff currently do, but not the patron.  Not sure why this is.

It would also be great if there were options for e-mail to staff when a hold has been cancelled, and an alert on the staff home page, along with the suggestion notifications and patron update requests.
Comment 1 Lisette Scheer 2020-02-25 20:07:37 UTC
(In reply to Christopher Brannon from comment #0)
> and an alert on the staff home page, along with the
> suggestion notifications and patron update requests.
 
Especially if it only counted the number at your branch so it was easy to see if you needed to go pull anything. 


If we did this, we might wanted to give them a separate status until they were scanned in again. If we add this we might want to do the same for staff cancelled holds.
Comment 2 Katrin Fischer 2020-03-15 22:15:32 UTC
I think it was deactivated for this reason: there was no way to tell which items to pull from the pickup shelf as staff will not be notified. I like both ideas of a new status and an email. I think email only would not work so well, we should have something on the dashboard too.

Behaviour should also be optional.

That said... this is a duplicate of bug 22456. It's common to let the 'older' bug survive.

*** This bug has been marked as a duplicate of bug 22456 ***