Add a library specific filter to the site search (e.g. /business, /health, /rose....)

[mjander2]

Is your feature request related to new functionality not yet included in the product? Please describe.
The site search tab on the blue nav bar searches all libraries by default. This often returns results that are not relevant to what the user is looking for. The filter on the right will let you search by page/database/exhibition/person, but not filter to specific libraries. A filter to /business /health, etc would more likely return results a user is expecting.

Is your feature request related to a problem or a change to existing functionality? Please describe.
When individuals search the site, they get everything instead of something relevant to their search. (e.g. a search for faculty is a big gibberish of results. Sure, they should use the drop down and find things that way, but for folks who use site search, this is more macro than they expect

Describe the solution you'd like
A default to search by the library per page via the top search tab, or a filter on the right with the other filters.

Describe alternatives you've considered
Tell users to navigate via the nav bar, or browse further.

How will this impact users?
Users who prefer to use site search vs browse will benefit from this change .

Additional context
Add any other context or screenshots about the feature request here.

[CB987]

One potential issue I see with this is that a lot of the content is not within a specific library. Anything that's in tools/ or archives/ or staff/... will not show up if it's filtered to just what's under a specific library. However.
So right now the facets come from https://dev.libraries.emory.edu/admin/config/search/facets, under which you can find search_api:views_page__main_libraries_search__main_search which only includes the content_type facet, which is what produces the person, page, exhibit, etc., in the facet results because they are specifically defined content types. We can add a facet, but getting it to pick either the location of a result (not defined on most pages, based on looking at the content list) or grab something out of the url might be trickier.

[lovinscari]

Update ticket regarding the changes that would be needed with metadata.

[maxdmayhew]

This would require most content to be tagged, so a lot of work for content editors.

[lovinscari]

@cwbragg = We will need to review the tags that are needed to get the content ready. This will require a discussion with @rotated8.