Bug 13125 - Total Holds does not tally holds / items.reserves is not populated
Summary: Total Holds does not tally holds / items.reserves is not populated
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
: 12530 (view as bug list)
Depends on:
Reported: 2014-10-22 03:00 UTC by Danielle Elder
Modified: 2020-06-03 10:14 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Note You need to log in before you can comment on or make changes to this bug.
Description Danielle Elder 2014-10-22 03:00:22 UTC
The items.reserves field in Koha is not working. It does not tally the total number of holds. I have checked several libraries with books that are usually on hold an all do not have any holds in the total ... at all.
Comment 1 Owen Leonard 2016-07-21 18:47:27 UTC
(In reply to Danielle Elder from comment #0)
> The items.reserves field in Koha is not working.

Did this ever work? This sounds like it is an enhancement request, although I wouldn't think an item-level count of holds would be useful unless you also required item-level holds all the time.
Comment 2 Katrin Fischer 2016-07-21 21:55:26 UTC
Hm, maybe we could use it to count how many holds a specific item has filled - it might be interesting to see.
Comment 3 Barton Chittenden 2018-11-27 19:14:11 UTC
items.reserves shows on the koha-to-marc mapping, and is also documented in https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx)

For the sake of supportability, I would like to see this either fully implemented or removed.
Comment 4 Katrin Fischer 2019-02-10 22:10:01 UTC
*** Bug 12530 has been marked as a duplicate of this bug. ***
Comment 5 Christopher Brannon 2020-01-27 15:36:04 UTC
I would like to see this implemented.  Doesn't make sense to keep running totals of checkouts and renewals and not reserves.

I guess we need to start with, what counts?

Personally, I want to know every hold, whether cancelled or filled.  Some might want only filled, and others might say only those that have been picked up.  I say all combinations should be a preference, but all should be an option for the tally.

Logistically, it would be easiest to add to the tally at the time of creation for all holds placed.  But for only filled holds or picked up holds to be tallied, that would probably need to be added at the time of fulfillment, or at time of pickup, and not at the time of creation.