| Summary: | Holds history doesn't show where hold placed | ||
|---|---|---|---|
| Product: | Koha | Reporter: | SiobhanC <siobhancottam> | 
| Component: | Transaction logs | Assignee: | Bugs List <koha-bugs> | 
| Status: | NEW --- | QA Contact: | Testopia <testopia> | 
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | david.roberts, kebliss, smhodson123extra | 
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 | 
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
| 
 
        
          Description
        
        
          SiobhanC
        
        
        
        
          2018-11-07 09:46:16 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 :( (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. 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. 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.  |