https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166
Andrew Fuerste-Henry <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Andrew Fuerste-Henry <[email protected]> --- 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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
