https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962
Alexander Wagner <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from Alexander Wagner <[email protected]> --- First I'd second (Katrins comment)(https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962#c4) that collections are something different than locations. They may coincide, but they don't have to. Being pointed to this bug, I wonder if there is indeed yet another column required. The current mappings in `UpdateItemLocationOnCheckin` for some reason change both: `items.location` _and_ `items.permanent_location`. Just for `CART` and `PROC` they work on `items.location` only. I wonder why they don't work on `items.location` only all the time, especially as I have `_PERM_` referring to `items.permanent_location`. It could just clear `items.location` so the item is back at the permanent location. It might be, that there is only a way lacking to actually _set_ `items.location` and only `items.location` to the value required. Say, if I could set `items.location` to `DSP` (or whatever LOC value) one is already there, adding a rule that clears `DSP` upon item check in. Or alternatively, if items on display should stay on display even after a check in I'd leave this rule and at some point explicitly clear `item.location`. Both could also be done by some cron-job. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
