Unable to link Circulation Limit Sets to Local System Owned Shelving Locations

Bug #2072502 reported by Courtney Brown
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

I'm attempting to create a circulation limit set for one of our library systems, to allow items with a Circulation Modifier of TECHNOLOGY shelved to their system owned Shelving Location of Juvenile Fiction Reading Rainbow circulate no more than 5 items. Since they already reference a limit set of 1 in another TECHNOLOGY circulation policy that has been linked to the circulation modifier, I've attempted to link the new TECHNOLOGY circ. limit to the shelving location. However, I've noticed that I'm unable to link Circulation Limit Sets to shelving locations not owned at the consortium level(Cardinal). When attempting to select the needed system level location from the dropdown menu, I notice that only shelving locations owned at the consortium level(Cardinal) are provided in the selection menu. I’ve attempted to log my workstation in as if I were at the system who owns the shelving location. However, I find that only the consortium owned locations are still available for selection. We are currently using Evergreen 3-11-1.

(Image Attached)

Revision history for this message
Courtney Brown (courtney.brown) wrote :
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

What version of Evergreen are you on?

In 3.11.1 I can see the expected shelving locations at the branch where my workstation is registered as well as at all of the branch's ancestors.

Possibly you're running into https://bugs.launchpad.net/evergreen/+bug/1956358 where the shelving locations don't display consistently?

tags: added: admin-pages circulation
Revision history for this message
Courtney Brown (courtney.brown) wrote :

Hi Jennifer,

Thank you for your response. We're using Evergreen 3-11-1. Sorry for leaving that out of my initial post.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.