Primo VE: Public names for Libraries and Locations
It would often be helpful if patron-facing names of libraries and locations were different from the staff-facing names in Alma, e.g., staff users may need to know exactly which of several "Closed stack" is in play, while this is irrelevant information for end users. So public names of Libraries and Locations should be editable through the Discovery Labels code table
-
Manu Schwendener commented
_Alma_ NERS 7047 and Primo NERS 6655, voting open now.
-
Manu Schwendener commented
Also allow different names in different languages.
-
Mary Huissen commented
Yes. We'd like to shorten names for libraries in Primo under the "Library" facet (not Location) without this changing the official names in notices generated by Alma
-
You are absolutely right. There should be differentiation between the official names in the letters from Alma to catchy names for the readers
-
Manu Schwendener commented
_Alma_ NERS 7047, voting open now.
-
Manu Schwendener commented
NERS 6655, voting open now.
-
Manu Schwendener commented
-
François Renaville commented
Agreed! External names for libraries would be really convenient.
-
Knut A Bøckman commented
Lesli, you're absolutely correct about the location "external name", of course. Thanks for helping! :)
I'll modify the idea to allow the same for libraries and, most importantly, to let such external names be available to the Discovery-Admin role, e.g. in Discovery Labels table. -
Lesli M Moore commented
Maybe I'm confused, but isn't this already supported by "external name" in location configuration?