Comment 5 for bug 1534979

It would without any further change, but that's not what I was suggesting. Sorry if that wasn't clear.

My point was that if someone wants to develop some new code to provide the ability to "search everywhere, but know where the patron is" then I recommend using the existing depth mechanism, rather than inventing new settings, CGI parameters, etc, that are similar to but different from locg, phys_loc, preferred_location, and the site() search filter (among, likely, several other search-location-setting things).

Users used to be able to control the breadth of their search as well as the focus. Now they can't control the breadth, only the focus. Some attempt was made to bring back something like breadth control by always including a logged-in users "preferred library" in every search -- which is neither breadth control, nor straight-forward IMO.

It sounds like you want to bring back breadth control, which is what exposing the "depth" CGI param through an interface widget (new code) would do naturally.