[Koha-bugs] [Bug 7817] Items Permanent location (shelving location) is set to NULL when item is edited

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Jun 19 05:01:24 CEST 2014


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7817

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #9 from David Cook <dcook at prosentient.com.au> ---
(In reply to Olli-Antti Kivilahti from comment #8)
> I would like to know why such a serious issue hasn't been fixed to master?
> Clearly this problem has been identified years ago and somebody must have
> fixed it (because atleast the creator of  ReturnToShelvingCart uses this
> feature), but the fix never made it here???
> Why?
> 
> I was able to fix the ~4500 missing permanent_locations from our
> installation specific identifier in the items.itemcallnumber. But others are
> not so lucky.

I imagine this issue hasn't been fixed, because it requires a specific
configuration and someone to notice a problem.

I believe that for this issue to occur you would need the following config:

0) Set the Shelving Location for an item during 'Add item' (this will populate
'item.location' and 'item.permanent_location' with the LOC authorized value for
the shelving location

AND 
-

1a) 'NewItemsDefaultLocation' set to 'PROC' and 'InProcessingToShelvingCart'
set to 'ON'

OR 

1b) 'ReturnToShelvingCart' set to 'ON'

-
AND

2) Edit the item before checking it (since editing the item will clear
'item.permanent_location' due to a missing Koha => MARC mapping 

THEN

Run 'cart_to_shelf.pl'

--

At Prosentient, none of our libraries use any of these system preferences, so
it hasn't been an issue. 

As for other libraries/vendors, I suspect that there could be any number of
reasons for a fix not making it here. Either people don't use these
preferences, they haven't noticed the problem, or they've created a custom
solution that they don't think is appropriate for the community.

--

I haven't looked at the code (and I probably won't since it doesn't affect any
of my libraries at present), but there's an explanation.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list