Bug 33301 - Request for adding a facility to remember the previous item location and switch back to it upon check-in
Summary: Request for adding a facility to remember the previous item location and swit...
Status: RESOLVED DUPLICATE of bug 30901
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-22 10:04 UTC by T. Jogi Raju
Modified: 2023-11-29 14:25 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description T. Jogi Raju 2023-03-22 10:04:06 UTC
For example an item with location code 'GEN' is sent for binding and the current location is now 'SFB' (Sent for binding) and when that item comes back to library from bindery, it's location should automatically be switched back to 'GEN' upon check-in. Since items with different location codes form the list of items being sent for binding, remembering the previous location will help Koha system to automatically set the locations back to the respective original locations.
Comment 1 Katrin Fischer 2023-03-22 10:51:08 UTC
If GEN is always correct, you could also use UpdateItemLocationOnCheckin, but I guess the problem is, it's not always GEN...

I think the hard part here would be to make it configurable when Koha needs to remember a previous location and when it does not. Then we'd also need to get this right with PROC and CART locations.

Instead of using a location for binding maybe you could use a not for loan value (away for binding). Then you can reset that to available on checkin autmatically, using UpdateNotForLoanStatusOnCheckin.
Comment 2 Andrew Fuerste-Henry 2023-03-22 17:22:39 UTC
This is technically possible, though I'd love to see a more official and codified process. The database includes items.permanent_location, but Koha really only expects you to use to store the item's actual location while it's set to either a temporary status set when the item is first cataloged (defined in NewItemsDefaultLocation) or "CART" for cart_to_shelf cron. By default, any edit to items.location outside of cataloging a new item or setting an item to CART at checkin will *also* update permanent_location, thereby messing up what you're trying to do. But you can make location and permanent_location independently editable and then make items change from their temporary location to their permanent location at checkin.

To do so:
- Create a new 952 subfield, editable, managed within the Items tab, set to use the LOC authorised value. You'll have to repeat this setup in each framework in which you have items where you want to use a temporary shelving location.
- Go to Koha To MARC Mapping in administration and connect the subfield you just created to items.permanent_location
- go to system preferences set UpdateItemLocationOnCheckin to update all items toe their permanent shelving location at checkin (https://koha-community.org/manual/latest/en/html/circulationpreferences.html#updateitemlocationoncheckin)
- Pull up an item record and see that the edit screen shows both location and permanent location. Confirm that you can edit either without changing the other.
- Check in an item where the two values don't match, confirm it updates to the permanent_location
Comment 3 Andrew Fuerste-Henry 2023-03-22 17:25:36 UTC
But see bug 31187 for how this workflow doesn't currently allow for setting a temporary shelving location for multiple items in a batch.
Comment 4 Andrew Fuerste-Henry 2023-03-22 17:36:20 UTC
Thinking of ways to make this simpler, it'd be a great first step to introduce a method by which to indicate which shelving locations should be considered "temporary" in the style of the shelving cart. Maybe a system preference where one enters a list of shelving locations, and Koha remembers that any edit to set an item to one of those locations should set items.location without changing items.permanent_location.
Comment 5 Andrew Fuerste-Henry 2023-11-29 14:25:58 UTC

*** This bug has been marked as a duplicate of bug 30901 ***