Settings and activity
231 results found
-
38 votes
An error occurred while saving the comment
Alison Pruntel
supported this idea
·
-
56 votes
Alison Pruntel
shared this idea
·
An error occurred while saving the comment
Alison Pruntel
commented
This is one of the options for the Vega Discover MEEP (haven't voted yet), and the committee was shown it is doable for Polaris because the title, author, etc., is retained after the record is deleted. The Polaris customers will be able to see that it's been deleted but at least they can see the title/author (no cover, etc.), but Sierra users will be out of luck, the whole thing will be removed. I can see that driving someone crazy, if they know they read something and it disappears once we weed it from the collection.
-
7 votes
Alison Pruntel
shared this idea
·
-
51 votes
An error occurred while saving the comment
Alison Pruntel
commented
This has been an ongoing issue for our power patrons and staff. When using the Classic WebPAC, you can filter your search results to exclude titles in your reading history, saving you time. Unfortunately, Vega does not do that, and it's especially frustrating for people who read a lot of series. This particular defect is one that I believe is holding back some of our die-hard users of the WebPAC from converting to Vega users. Please note that this was also an idea under the vague title "filter for previously read materials" that had no details, etc. (I think an III employee "shared it" from the old idea system) - https://ideas.iii.com/forums/951766-vega-discover/suggestions/46646161-filter-for-previously-read-materials.
Alison Pruntel
supported this idea
·
-
27 votes
https://portal.productboard.com/iii/15-vega-product-portal/c/685-syndetics-unbound-features-for-consortias-50-complete
Alison Pruntel
supported this idea
·
-
19 votes
An error occurred while saving the comment
Alison Pruntel
commented
You should be able to enable/disable depending on the collection. If you're trying to test out a new collection (creating custom header, etc.), you don't want this available for users to select.
Alison Pruntel
supported this idea
·
-
16 votes
Alison Pruntel
supported this idea
·
-
13 votes
An error occurred while saving the comment
Alison Pruntel
commented
I wish the Your Next Read showcase was more flexible - use bookmarks, saved searches or reading history, OR set it so the fallback (if no bookmarks, etc.) is whatever we chose/set, just like the 2nd showcase field.
I don't know if having something based on your reading history will be appreciated by people wondering about privacy protections. Also, if you're a parent and check out a bunch of kids books, you may not want to just get suggestions for that age level.
Alison Pruntel
supported this idea
·
-
7 votes
Alison Pruntel
supported this idea
·
-
12 votes
Alison Pruntel
supported this idea
·
-
31 votes
Alison Pruntel
supported this idea
·
-
8 votes
An error occurred while saving the comment
Alison Pruntel
commented
As noted in another related idea, the current version of Vega Patron registration for us Sierra libraries is really not of any use.
Alison Pruntel
supported this idea
·
-
25 votes
An error occurred while saving the comment
Alison Pruntel
commented
We don't have this in Sierra (online registration), would be nice to have what you have in LEAP/PAC.
Alison Pruntel
supported this idea
·
-
14 votes
Alison Pruntel
supported this idea
·
-
7 votes
An error occurred while saving the comment
Alison Pruntel
commented
The Vega Patron registration as-is is of no use to us, are stuck with the old WebPAC registration. I don't think this was tested with a Sierra library.
Alison Pruntel
supported this idea
·
-
15 votes
Alison Pruntel
supported this idea
·
-
30 votes
Alison Pruntel
supported this idea
·
-
9 votes
Alison Pruntel
supported this idea
·
-
22 votes
Alison Pruntel
supported this idea
·
-
8 votes
Alison Pruntel
supported this idea
·
This would be wonderful - we have a lot of showcases and though staff are supposed to "weed" them annually, that isn't happening. Metadata could include the barcode or username/email of the staff member who created, ability to add an end/retirement date, etc.