Bug 35712 - Make clear in historical data when a checkout fills a hold
Summary: Make clear in historical data when a checkout fills a hold
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-05 14:50 UTC by Andrew Fuerste-Henry
Modified: 2025-09-04 12:55 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2024-01-05 14:50:19 UTC
There is not currently a direct data linkage between a filled hold in old_reserves and the checkout that filled it in (old_)issues. It'd be helpful if we could put the issue_id into the old_reserves table to make that explicit.
Comment 1 Steve, OSLRI, USA 2024-11-12 14:10:34 UTC
On a similar note, it would be helpful to add issue_id and reserves_id to the statistics table.  (I've found the timestamps across statistics, issues, reserves and action_logs don't match up neatly.)
Comment 2 Andrew Fuerste-Henry 2025-09-04 12:42:20 UTC
(In reply to Steve, OSLRI, USA from comment #1)
> On a similar note, it would be helpful to add issue_id and reserves_id to
> the statistics table.  (I've found the timestamps across statistics, issues,
> reserves and action_logs don't match up neatly.)

And to the pseudonymized_transactions table, too.