statistics.location currently uses items.location at the time an item is checked out. This means that for a library using the CART and PROC locations, accurate data about an item's permanent location at the time of check-out can only be gathered through a report linking to the item record. It would be more efficient for items that are using the PROC and CART locations if the statistics table also included the item's permanent location or if there were a system preference that allowed users to specify whether they want statisitcs.location to use an item's items.location or items.permanent_location at the time of check-out.
+1
Agreed.
If we're recording it in statistics we should add it to pseudonymized transactions, too.
Agreed!
Would a switch/change to use permanent_location be enough or are both locations needed?
items.permanent_location is not populated at libraries where the cart-to-shelf function is not used, so I think it would be best as a system preference, giving the library the choice of which one to use. That being said, if both were populated in statistics, that would cover the issue equally well.
(In reply to George Williams (NEKLS) from comment #6) > items.permanent_location is not populated at libraries where the > cart-to-shelf function is not used, so I think it would be best as a system > preference, giving the library the choice of which one to use. That being > said, if both were populated in statistics, that would cover the issue > equally well. +1
+1 Adding items.permanent_location to statistics would resolve this problem.