Localize Collection Discovery for libraries of an Alma institution
For a given library in an Alma institution, the Alma collections associated to this library should only appear in the Collection Discovery page and on the records of items belonging to this collection, if the library is associated to the Primo view (in the "Primo view mapped into Alma libraries" mapping table).
In the current situation, all the collections of any library of the Alma institution are visible, even if the Primo view is limited to one or some libraries in the institution.
Marcus Jun commented
There is a similar Idea (specifically focused on Alma consortia with a Network Zone). https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38489206-primo-back-office-in-a-consortial-environment-ab
"Our university system is in a consortial configuration of Alma and Primo Back Office.
Currently, we cannot use Alma collections because one university's (local and institution-specific) collections display in all other Primo instances in our consortia. This is problematic and confusing because a collection at University A displays in University B's Primo as if it were University B's collection. But the collection is local and specific to University A only."
Tamara Marnell commented
Last year several institutions in my consortium opened cases to ask for this, because the collections displaying across institutions is a problem for multiple reasons.
1) The Collection Discovery interface retains the VID of the patron's home institution, giving the impression the collection is local, when it's not.
2) If items in the collection are not owned by the patron's home institution, they don't display at all. I don't know if titles available for resource sharing are hidden or shown, but I suspect from my tests they're hidden...which defeats the point of enabling the discovery of collections at other institutions.
At first the institutions who asked for a fix received comments that this Primo behavior was a defect and would be addressed by development. Then months later they received new comments that the collections are actually "working as intended."
So like Sean below, I sincerely hope this Idea gets enough votes to convince Ex Libris this is a bug, not a feature!
Brad Baxter commented
Floriane Pochon Levit commented
@m schwendener : Yes, I wasn't aware of this thank you, but we need this in both Primo flavors!
Sean Purcell commented
Yes! We agree! I was about to post a similar idea, but figured it would be better to ride on the coattails of this one. Please upvote! Here's another way of explaining this:
Collection Discovery: Make collection path links configureable to only show for the library that created that collection
We are a consortia of 26 Alma/Primo institutions in Georgia. One of our institutions has set up a number of local Alma collections and the collection path links for these resources show up just fine in this institution's Primo. Unfortunately they are also showing up in other institutions' Primo instances when the bib is shared by those institutions. For example, let's say that institution A sets up a local Alma collection. If institution B owns a title that is contained in Institution A's collection, when a patron at institution B searches for that book in their instance of Primo they will see institution A's collection path links in the details area. We've been told by Ex Libris support and Ex Libris development that Collection Discovery is not intended to be restricted to a single institution, thus the links show for the entire consortium. We believe this "feature" makes Collection Discovery unusable for consortia. Please vote on this to convince Ex Libris to make it so that collection path links can be configured to show only for the institution that created that collection.
m schwendener commented