Restrict Location Code Edits to Locations in Scope (especially in Rapid Update)
There is currently a setting allowing us to prevent logins from editing records with a location code outside of their current scope. However, users are able to edit records in their scope to have location codes outside of their scope, which then blocks them from being able to edit the records again. This happens accidentally sometimes, and is particularly a problem in Rapid Update. It would be great if item location dropdowns in Rapid Update, and possibly the item record as well, only showed locations in the user's scope in order to prevent this problem. Alternately, the system could prevent saving the record if the selected location is outside the scope, or at least warn the user when this is happening. If it only showed locations in the scope, however, that would have the added benefit of making it easier for users to find their location codes, instead of seeing the full list of all location codes.
Sam Cook
shared this idea
In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Jeremy Goldstein
commented
Our annoying version of this problem is that most of our libraries use a macro for tabbing to the status field, typing a w for withdrawn, and saving the record.
If their cursor is in the wrong location when they trigger the macro what winds up happening more often then not is 'w' is typed into the location field instead and the item winds up in the scope of our long suffering Watertown library. We probably wind up fixing a dozen out of scope items a week from this.