serials org unit selector broken

[James Fournie]

In current master and demo.evergreencatalog.com as of April 16,2019

The org unit selector for subscriptions is broken.

1. It is really wide and overlaps the "No subscriptions are owned by this library" box

2. When I select something from the list, ie: BR1 from the default org-tree, and click New Subscription, the resulting subscription info that appears below is at the CONS level even though it says "Subscriptions owned by or below" I wouldn't expect that

[Chrisy Schroth (cschroth)]

Comment 1. Yes, the Org unit selector overlaps the No subscriptions are owned message, but I am not sure that is a problem.

Comment 2. Yes, when you select a choice on the Org tree and click New subscription, the resulting subscription does not necessarily appear at the level you selected on the Org tree (but it might).

That said, it isn't defaulting to the top of the Org tree, i.e., select BR1 and it defaults to CONS as the top of the Org tree. It's defaulting to your login branch. I had the same result as above when testing on Blake's test server during this Feedback Fest (2/11/2021). I believe that demo login puts you at the CONS level. When I selected CONS and clicked New subscription, it created it as CONS.

On my library's own system (3-4-5), I always select the top of the Org tree for our subscriptions, but it always creates the new subscriptions at my branch level and I have to change it to the "Consortium" level.

I agree, it isn't what I would expect. I would expect that choosing an Org unit and selecting New subscription, it would create said subscription at the level I had just selected, not my home branch.

[Erica Rohlfs (erohlfs)]

Confirmed in version 3.7

1. I agree that the "Subscriptions owned by or below" box is too long. I also find the "No subscriptions are owned by this library" overlap problematic, especially when attempting to select a different org unit (image attached).

2. When I select "Manage Subscriptions" the "Subscriptions owned by or below" is scoping to the last org unit that I searched. So, if I have a subscription at BR1; I am logged in at BR3; my last search was for BR1; I will see the BR1 subscription; I select "New Subscription" Evergreen automatically scopes to BR3 for the new subscriptions, and I can still view the BR1 subscription. I, personally, think it makes the screen busy. However, I can see where others may find it helpful to view another location's subscription while building a new one.

Also noting that, since I'm logged in at an Admin level, I don't know how much permissions will affect what others will see when searching subscriptions.

[Beth Willis (willis-a)]

Confirming that this is still an issue in 3.9