Comment 5 for bug 1815815

I've rebased and pushed an updated version of the above branch. I haven't addressed Jeff's concerns, but I think we can do some of that. I think we can definitely provide ways to suppress the new dropdown, either entirely or just in certain cases (such as when there are no library groups to choose from given the context). And a way to suppress the depth selector seems reasonable, but I disagree that the equivalent functionality exists today.

The problem with providing just one dropdown and folding library groups into it, as I see it, is that we need a context org unit in order to identify context-based groups. IOW, they're dependent objects. One option I considered but discarded was embedding groups either under or directly above all the org units that are relevant. The most obvious problem with that is all the duplication it would create.

With that in mind, the fact that location groups are also dependent objects of org units (though, in general, in the other direction with regard to scope restriction) it seems useful to put them in the secondary dropdown as well.

Does anyone have more thoughts on how to come to a good UX compromise?

Thanks!