Bug 36064 introduced a new alert, which is fantastic. However, it is displaying and linking to ALL cancelled holds, not just for your branch. This is inconsistent with the behavior of other alerts. We either need a second line for just the branch, just like the material requests, or we need it to be consistent with patron modifications. It does not make sense to make all branches aware of all cancellations when some of those items are at other branches.
System-wide, we regularly have over 3500 items on our "Holds awaiting pickup" list. Displaying all of them rather than the ones relevant to the user's logged in branch is so slow that my first thought was that Koha had crashed. It hadn't, it just took a very long time to load the page--about 90 seconds. I used CSS to hide it so none of the circulation staff would panic if they tried to use it.
(In reply to Sally Lodico from comment #1) > System-wide, we regularly have over 3500 items on our "Holds awaiting > pickup" list. Displaying all of them rather than the ones relevant to the > user's logged in branch is so slow that my first thought was that Koha had > crashed. It hadn't, it just took a very long time to load the page--about 90 > seconds. > > I used CSS to hide it so none of the circulation staff would panic if they > tried to use it. I'm probably going to do the same thing. George and I went over a jQuery version of this that is specific to the branch, which is what inspired this feature. Why they went in this direction, I am not sure. I am going to hide ours as well and keep our custom version live.