Summary: | 'Transfers to send' report only appears if StockRotation syspref is enabled but contains information about other types of transfers | ||
---|---|---|---|
Product: | Koha | Reporter: | Caroline Cyr La Rose <caroline.cyr-la-rose> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | andrew, carthur, gmcharlt, jheltibridle, kyle |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37236 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Caroline Cyr La Rose
2025-02-19 15:40:59 UTC
Our system does not use StockRotation. But we do send items to other branches for holds and to return them to their owning library. I can check Transfers to Receive and see that there are late items, which I can search for and see if maybe we forgot to check them in, or mark them as lost. I'd like to be able to do the opposite, and check to see if we have items that were supposed to be transferred out, but didn't get sent. Would this let me do that? +1 Transfers to Send is, very specifically, showing entries in the branchtransfers table that have a daterequested value but not a datesent value. In Caroline's examples: 1: A manual transfer is always created with a datesent value -- it has been sent from the moment it's created. 2: Placing the hold doesn't generate anything in branchtransfers. If we went a step further and checked the item in, Koha would generate a transfer but, like above, it would immediately have a datesent value. 5: Rotating collections actually does create transfers that don't yet have a datesent, so it makes sense this one shows up in Transfers to Send. To my knowledge, *only* rotating collections and stock rotation should be generating unsent transfers. What Juliet describes would be giving information about transfers that have been sent but not received, but from the point of view of the sending library. "Transfers that have been sent," rather than either "Transfers to send" or "Transfers to receive." That sounds like a distinct (and worthwhile) idea. It would make sense to show Transfers to Send to Rotating Collection users without requiring them to turn on Stock Rotation. Maybe the answer is to add a syspref to enable/disable Rotating Collections and then show Transfers To Send if *either* the Stock Rotation or Rotating Collection sysprefs are enabled. |