Adding recent (current/past year) statistics to the items table
Hi All, We have had several requests recently for an easy way to access current/last year's circulation stats for items, without having to create reports totalling these numbers. The numbers here are used for weeding, state reporting, etc. Other systems have fields: 'Year to date circ' and 'last year circ' We have discussed several possible developments: - a new table to track these - adding a new field, or altering 'issues' to use JSON and storing circ/renewal counts by year - adding two new fields to the items table and use a cronjob to move 'current year' circ to 'last years circ' at the end of the year. We wanted to check in with the community to see if this is a request that others have or have seen, and how they handle these. Thanks for any info. Nick (kidclamp) -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>
I have schools using Koha here, and those are reports that my schools asked for. I built reports for them, but Guided Reports could probably take care of them too. On Fri, Apr 22, 2022 at 12:52 PM Nick Clemens <nick@bywatersolutions.com> wrote:
Hi All,
We have had several requests recently for an easy way to access current/last year's circulation stats for items, without having to create reports totalling these numbers. The numbers here are used for weeding, state reporting, etc.
Other systems have fields: 'Year to date circ' and 'last year circ'
We have discussed several possible developments: - a new table to track these - adding a new field, or altering 'issues' to use JSON and storing circ/renewal counts by year - adding two new fields to the items table and use a cronjob to move 'current year' circ to 'last years circ' at the end of the year.
We wanted to check in with the community to see if this is a request that others have or have seen, and how they handle these.
Thanks for any info. Nick (kidclamp)
-- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution> _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
-- Michael Hafen Washington County School District Technology Department Systems Analyst
Hi Nick and all, I am a little worried about having yet another 'source of truth' we'll need to keep in sync and update on every circulation action and added maintenance for moving it end of year etc. Maybe we could pull the data from the statistics table into a nice display or add a new built-in report to make querying this data easier? Katrin On 22.04.22 21:32, Michael Hafen (TECH) wrote:
I have schools using Koha here, and those are reports that my schools asked for. I built reports for them, but Guided Reports could probably take care of them too.
On Fri, Apr 22, 2022 at 12:52 PM Nick Clemens <nick@bywatersolutions.com> wrote:
Hi All,
We have had several requests recently for an easy way to access current/last year's circulation stats for items, without having to create reports totalling these numbers. The numbers here are used for weeding, state reporting, etc.
Other systems have fields: 'Year to date circ' and 'last year circ'
We have discussed several possible developments: - a new table to track these - adding a new field, or altering 'issues' to use JSON and storing circ/renewal counts by year - adding two new fields to the items table and use a cronjob to move 'current year' circ to 'last years circ' at the end of the year.
We wanted to check in with the community to see if this is a request that others have or have seen, and how they handle these.
Thanks for any info. Nick (kidclamp)
-- Nick Clemens ByWater Solutions bywatersolutions.com <http://bywatersolutions.com> Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution> _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
-- Michael Hafen Washington County School District Technology Department Systems Analyst
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :https://www.koha-community.org/ git :https://git.koha-community.org/ bugs :https://bugs.koha-community.org/
As a librarian I have to agree with Alvaro's comment. With so many Koha libraries out there, I can easily see there being lots of requests to have the data parsed just so. That said, if the request really is for something as simple as YTD checkouts (+/- renewals), then perhaps this could be added to the Reports page (reports-home.pl), joining the Item type count report, etc. Preferable in my view would be some kind of basic dashboard functionality. I know there are 3rd party options for this (for example <https://bywatersolutions.com/education/dazzling-dashboard-display-data>), but librarians are lazy & a native solution is more likely to be used :-) Just one librarian's opinion ... Cab Vinton, Director Plaistow Public Library Plaistow, NH
participants (4)
-
Cab Vinton -
Katrin Fischer -
Michael Hafen (TECH) -
Nick Clemens