Settings and activity
485 results found
-
6 votes
Kathryn Brew
supported this idea
·
-
7 votes
Kathryn Brew
supported this idea
·
-
3 votes
Kathryn Brew
supported this idea
·
-
8 votes
An error occurred while saving the comment
Kathryn Brew
supported this idea
·
-
22 votes
Kathryn Brew
supported this idea
·
-
2 votes
Kathryn Brew
shared this idea
·
-
6 votes
Kathryn Brew
supported this idea
·
-
7 votes
Kathryn Brew
supported this idea
·
-
8 votes
Kathryn Brew
supported this idea
·
An error occurred while saving the comment
Kathryn Brew
commented
Sierra also has a linked patron feature. I assume each one works slightly differently, which is why it is hard to integrate, but this has caused significant confusion with staff. At the least, the patron-facing linked patrons in Vega Discover and Vega Mobile should be the same. If the ILS could be a single source of information, everything could work together nicely. Since Clarivate owns Vega and the two main ILSs used by Vega customers, developing the Vega-like linked patron feature in Sierra and Polaris could replace/enhance the current ILS linking features and the need to have them separately in Vega Discover and Mobile.
-
9 votes
Kathryn Brew
supported this idea
·
-
6 votes
An error occurred while saving the comment
Kathryn Brew
commented
I would prefer a restoration of the ability for logged-out users to create temporary bookmark lists, but if not possible, or in the meantime until restored, yes please modify the bookmark feature to say that you must log in to view them.
Kathryn Brew
supported this idea
·
-
2 votes
Kathryn Brew
supported this idea
·
An error occurred while saving the comment
Kathryn Brew
commented
In our library system, it sounds like the equivalent fields are home library and p type (we are on Sierra).The mobile app uses Home Library to load the template, but we use P Type on the back end to designate which library someone belongs to for OverDrive and similar services. We have stat codes but use them for something else.
So what would be most helpful is letting the organization choose which patron field(s) to use for default location-based stuff.
-
3 votes
Kathryn Brew
supported this idea
·
-
8 votes
Please watch the roadmap; this is work we are planning on doing.
https://portal.productboard.com/iii/15-vega-product-portal/c/676-wish-lists-and-vega-bookmarks-integration
Best,
Angela Nolet
Sr. Product Manager
Kathryn Brew
supported this idea
·
-
15 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Kathryn Brew
supported this idea
·
-
27 votes
Kathryn Brew
supported this idea
·
-
26 votes
Kathryn Brew
supported this idea
·
-
28 votes
Kathryn Brew
supported this idea
·
-
5 votes
Kathryn Brew
supported this idea
·
-
3 votes
Kathryn Brew
supported this idea
·
I've also run into this. Now patrons see collections like "zzz Test for PPLD."
In addition - we have a custom Vega URL but not all of the collection sites have custom URLs created yet (they don't automatically work) because we haven't been actively using them or promoting them to the public yet. If a patron is on our custom domain and chooses one of these default collections, it tries to load a url that doesn't exist. Even if they go back to our main site and click log in again, it will immediately try to load that default collection site and the patron gets stuck being redirected to our old catalog which tries to redirect back to Discover and on and on. They don't have a way back to edit the default collection site unless they know to replace the base url with the iiivega one, which they never would.