Bug 21779

Summary: Holds history doesn't show where hold placed
Product: Koha Reporter: SiobhanC <siobhancottam>
Component: Transaction logsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: david.roberts, katrin.fischer, kebliss, smhodson123extra
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description SiobhanC 2018-11-07 09:46:16 UTC
The Holds history tab doesn't show the same information as the modification log e.g. if the reservation was placed in the OPAC or staff client. 

It is possible to find this information from the log viewer, but not from a patron record modification log as this doesn't show holds at all. This is time-consuming to find the relevant hold if you don't already know the approximate date when the hold was placed. The system log uses the reserve ID as the Object, which is presumably why it doesn't show in the Patron log where their borrowernumber is the Object no.
Comment 1 Katrin Fischer 2019-03-11 21:25:43 UTC
The log viewer uses the action_logs table, the holds history uses data from reserves and old_reserves. The action_logs table has the column 'interface' which can be used to determine where the hold was placed. This information is not available form the *reserves tables.

Strangely, it doesn't look like we are logging the reserve_id - so there is no safe way to tell which line in action_logs corresponds to an entry in *reserves :(
Comment 2 Katrin Fischer 2019-03-11 21:27:36 UTC
(In reply to Katrin Fischer from comment #1)
> The log viewer uses the action_logs table, the holds history uses data from
> reserves and old_reserves. The action_logs table has the column 'interface'
> which can be used to determine where the hold was placed. This information
> is not available form the *reserves tables.
> 
> Strangely, it doesn't look like we are logging the reserve_id - so there is
> no safe way to tell which line in action_logs corresponds to an entry in
> *reserves :(

I was wrong, I was looking at old incomplete entires - reserve_id is logged now.
Comment 3 David Roberts 2019-06-30 23:40:47 UTC
It appears that (at 17.11 at least, I haven't yet tested at other versions) the action_logs table records holds created as being created the opac, even when they were created on the staff client.
Comment 4 Suzanne 2023-09-26 20:06:16 UTC
I agree that it would be nice to have the details found in the patron's hold history. It is quite a runaround to get the information otherwise. This is something we use frequently when there are missing holds or questions about what happened. Thanks.