Bug 14593

Summary: Send notifications for pending moderation staff actions
Product: Koha Reporter: Oliver Behnke <oliver.behnke>
Component: Staff interfaceAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: gmcharlt, katrin.fischer
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19412
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5770
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Oliver Behnke 2015-07-23 13:06:32 UTC
There should be an option to enable notices to the library staff whenever certain workflow actions are pending. These include at least all moderated entities like pending comment or tags, as well as new purchase suggestions.

All of these are currently displayed on the staff client dashboard (should also be made more prominent) but it would be great to have the option to send, say, an email to all library staff (i.e. a certain patron category?) or to an optional pre-configured address (could be a mailing list) with an update on all pending actions, preferably with types, counts and links to the relevant staff pages.

The use case for this are small libraries that primarily use a self-service model and hence don't have their staff continuously monitoring the dashboard for new TODOs. Notifying them about pending actions would streamline the process significantly.

Thanks!
Comment 1 Katrin Fischer 2019-02-20 20:54:30 UTC
For purchase suggestions there is:
Bug 5770 - Email librarian when purchase suggestion made

I'd recommend splitting the other ideas (tags, comments) into specific bugs.
Comment 2 Oliver Behnke 2019-02-27 10:23:18 UTC
Ok, so now that purchase suggestions are covered (bug 5770) let's use this bug report for the lack of moderation notifications. Since tags and comments are both moderation tasks I reckon we should keep that feature request in one ticket (this one). I'll update the title accordingly.

Cheers