https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22456
--- Comment #9 from Christopher Brannon <[email protected]> --- (In reply to Katrin Fischer from comment #8) > I like the idea of having it on the dashboard, but if we put them there, I'd > also like to see them on the holds awaiting pickup report somehow, because > this is where they probably are still :) > > I wonder database wise how we should deal with these. We could just show > 'cancelled in last... hours' - but then the library will be closed etc. and > it won't work as nicely and you will never see what your coworkers have > already taken care of... > > Some way to actually process them might be nice. Maybe a checkin could > remove them from the list? I like both ideas. Where ever it shows (new page via dashboard alerts/holds awaiting pickup), I think both cancelled and expired holds that do not have a datelastseen less than the cancellationdate and expirationdate (and the eventual patron_expiration_date in 22.05) should show as needing attention. This would eliminate the need for any new fields. I don't know if it would slow things down, but it might even be worth adding the logic to other places where that holds shows, with a badge or something, showing that this hold is expired/cancelled, and waiting to move on. Just depends on how much of a delay it would add to the process of the page, if it is checking this for all holds displayed on the page. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
