Navigation between consortia member instances of Discover
In a consortia, especially one with many member libraries that share patrons, it is important for users to be able to move from the main/parent domain instance of Discover to one of the individual library sites and also to be able to navigate between member library sites. This is functionality currently available in the Polaris PAC and heavily used.
-
Eric Lozauskas commented
Yes, ideally if there were a checkbox option for each collection site called "Include in Library Navigation" that would add that collection site to a dropdown list for toggling between multiple collection sites, that would be awesome. Thanks for the consideration!
-
Emily Laws commented
Our library patrons expect the ability to navigate between the main domain and individual library sites. This basic function is a primary reason our consortia decided to use Vega Discover, as it is widely used in the Polaris catalog.
-
Mary Alice Bodden commented
Our library patrons need to be able to navigate between needs to be able to member libraries . This is functionality currently available in the Polaris PAC and heavily used. It doesn't make sense to take away something that is heavily used by patrons move to Discover
-
Sarah Cournoyer commented
We share users with our neighboring consortia member libraries. Each library has unique features on their landing page of the catalog and want to be able to move between them. We aren't different branches of the same library and Discover needs to assist our patrons in navigating between our member libraries.