[Bug 39166] New: 'Transfers to send' report only appears if StockRotation syspref is enabled but contains information about other types of transfers
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Bug ID: 39166 Summary: 'Transfers to send' report only appears if StockRotation syspref is enabled but contains information about other types of transfers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs@lists.koha-community.org Reporter: caroline.cyr-la-rose@inlibro.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com The link to the 'Transfers to send' report is determined by the StockRotation syspref. However, I was playing with various types of transfers and noticed that the report actually contains other types of transfers (but not all). Should we remove the if StockRotation condition? To recreate: 1. Manually transfer an item to another library 1.1. Go to Circulation > Transfer 1.2. Choose another library (e.g. Liberty) 1.3. Enter a barcode for an item from Centerville (e.g. 39999000000771) 1.4. Click 'Transfer' 2. Place a hold for a Centerville item to be sent to another library 2.1. Search for Shakespeare grammar 2.2. Click 'Place hold' 2.3. Search for a non-Centerville patron (e.g. Henry Acevedo) 2.4. In 'Pickup at' choose Midway 2.5. Click 'Place hold' 3. Create a rotating collection 3.1. Go to Tools > Rotating collections 3.2. Click 'New collection' 3.3. Enter a title (e.g. Local authors) 3.4. Click 'Submit' 3.5. Click 'Return to rotating collections home' 4. Add items to the rotating collection 4.1. Click 'Actions' > 'Manage items' 4.2. Enter a couple of barcodes for items from Centerville and click 'Submit' after each - 39999000002195 - 39999000006933 - 39999000000719 5. Transfer collection 5.1. Click 'Transfer' 5.2. Choose a library (e.g. Springfield) 5.3. Click 'Transfer collection' 6. Go to Circulation --> There is no 'Transfers to send' report even though I do have 5 transfers to send 7. Enable StockRotation system preference 7.1. Go to Administration > System preferences 7.2. Search for StockRotation 7.3. Enable StockRotation 7.4. Click 'Save all Circulation preferences' 8. Go to Circulation --> There is the 'Transfers to send' report 9. Click 'Transfers to send' --> Transfers for the rotating collections are present, but not the manual transfer or the hold -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=37236 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Juliet Heltibridle <jheltibridle@rcplib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jheltibridle@rcplib.org --- Comment #1 from Juliet Heltibridle <jheltibridle@rcplib.org> --- 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? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 carthur@slolibrary.org <carthur@slolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carthur@slolibrary.org --- Comment #2 from carthur@slolibrary.org <carthur@slolibrary.org> --- +1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com --- Comment #3 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- 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.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Sally Lodico <Slodico@knoxlib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Slodico@knoxlib.org --- Comment #4 from Sally Lodico <Slodico@knoxlib.org> --- We use the Stock Rotation module, but the Transfers to Send tool was so unusable that I hid it from staff and replaced it with a report. If this is to be made available for other types of transit requests, I have a couple of suggestions to make it more useful. 1.) Don't break the list up into individual lists of where the items are to be sent. That doesn't help the staff that need to pull them off the shelves and shipped out. Create a single shelf order list that can be sorted and printed, like the holds queue. 2.) Don't include items that aren't available. The current version includes items that are lost, in repair, on hold at a different library, etc., but it doesn't tell the staff looking for those items that they're not likely to find them. It does include the due dates when when items are checked out but why bother listing them at all? It just makes the list longer than it needs to be. The Stock Rotation module has already changed the owning library and Koha will direct the items to their new homes the next time they're checked in without the pending transit request. Julie -- Yes, it will show you items that should have been shipped out, but weren't. I found a number of items in "Transits to send" that had been on the holds queue, but now have a lost or damaged status and weren't sent. In the process of setting the status the item had been attached to the hold request, so Koha stopped trying to fill it, leaving the patron high and dry. Another report made it simple to find these and revert the transit from the title's holds list to have Koha find the next available copy instead. Before turning on Stock Rotation and "Transits to send" I had no idea that was happening and needed be dealt with. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org