Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
Shawn P. Farrell
shared this idea
This idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Tracy Babiasz
commented
Yes! I'm not even sure why I need to know the number of items that were notified. At least not on a regular basis. I'm much more interested in the number of notices that were generated, often in troubleshooting notice production issues. The other use instance would be comparing different days or times (which, I suppose could also be a number of items being held comparison). There are occasions for wanting to know about the number of holds "popped" and several methods for determining that. I've often wanted to pull up notice history and just get a number of notices, but I've rarely been interested in the number of items that were on them.
-
Nicole Castellano
commented
Having handled notices for our member libraries, there can sometimes be a very big difference between our recorded numbers and what is printed since the item count doesn't always match the notices. This could help clear up some confusion.
-
Alexis Camarda
commented
We handle notices for numerous member libraries and provide them with a monthly tally of how many were printed. It has always puzzled me that Sierra does not accurately count the actual number of notices. I frequently observe 10 (or more!) notices being printed while Sierra logs it as only 1 or 2. Each notice, whether printed or emailed, should be accurately counted to maintain statistical integrity.