Settings and activity
222 results found
-
63 votes
Alison Pruntel
supported this idea
·
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment Alison Pruntel
commented
I guess I should have realized https://ideas.iii.com/forums/951979-vega-mobile/suggestions/46831621-list-reading-checkout-history-as-an-option-under-p is basically the same thing?
Alison Pruntel
shared this idea
·
-
25 votesAlison Pruntel
supported this idea
·
-
7 votesAlison Pruntel
supported this idea
·
-
17 votesAlison Pruntel
supported this idea
·
-
7 votesAlison Pruntel
supported this idea
·
-
20 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
Alison Pruntel
supported this idea
·
-
10 votesAlison Pruntel
supported this idea
·
-
16 votesAlison Pruntel
supported this idea
·
-
6 votesAlison Pruntel
supported this idea
·
-
11 votesAlison Pruntel
supported this idea
·
-
10 votesAlison Pruntel
supported this idea
·
-
7 votesAlison Pruntel
supported this idea
·
-
3 votesAlison Pruntel
supported this idea
·
-
2 votesAlison Pruntel
supported this idea
·
-
14 votes
An error occurred while saving the comment Alison Pruntel
commented
This is important for libraries/customers to understand when looking at/comparing the methods we use to communicate with patrons. Are more patrons getting notifications now through the app or is e-mail still the primary option? Does it make sense to worry about ad-hoc notifications if no one is signed up for them? This would seem to be a basic data point that the mobile app should provide libraries.
It would also be great if Solus could tell us the response rate, similar to what we get for LX Starter (delivery rate, fail rate, open rate, etc.).
Alison Pruntel
supported this idea
·
-
3 votesAlison Pruntel
supported this idea
·
-
17 votes
An error occurred while saving the comment Alison Pruntel
commented
Adding another comment (so it doesn't get closed for inactivity), as we just ran into this again with a showcase we're putting together for a photography program - https://fauqp.na.iiivega.com/library-list/list/e3f149ad-bf48-45db-af92-76422bd41bdf. It includes a lot of "how to" books but staff also included Bunny Williams on Garden Style, which I was confused about. I asked staff and was met with the reasoning, "I included photo-rich books that have local interest. There’s only so many “how to take photo” books that are interesting enough to add." Well, without that context, you may think it's a mistake it's in the photography showcase. If we could have a field where we could type in a description of the showcase, that would really help in cases like this.
An error occurred while saving the comment Alison Pruntel
commented
I would like to add on to this idea... it would be nice if you could add a comment to go with each item you bookmark...so WHY you bookmarked it. This is what we'd want if we were making a broad showcase like Staff Picks. So there would be a description of the showcase itself and then each item would have a blurb from the staff member, why they chose it. I think it would also help when patrons bookmark items. Often they don't create a list, may just have "For Later" and then can't remember why they bookmarked something (i.e., friend recommended, etc.). Related, the showcase creator...aside from the Nickname, it would be nice if there was a bio or description you could include.
Alison Pruntel
supported this idea
·
-
38 votes
An error occurred while saving the comment Alison Pruntel
commented
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.
Alison Pruntel
supported this idea
·
-
9 votesAlison Pruntel
shared this idea
·
We randomly get asked about this and actually yesterday (8/20/26), our director received a long (winded) letter asking when this feature would be available. The longtime patron is wondering why he is forced to go back to the Classic WebPAC catalog to be able to access this feature (you can export a text file, also not great but it's something). This turns into asking why we are forcing people to use Vega and bury the Classic Catalog, when the Classic "works." He wants to export (csv) and then be able to annotate with notes. Patrons often turn to Good Reads because that platform provides this function.