Settings and activity
195 results found
-
21 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo
supported this idea
·
-
24 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment -
17 votes
An error occurred while saving the comment Nicole Turzillo
commented
Our consortium's policy includes purging patron records with no circulation activity over a specified period. Given that several vendors use the REST API to authenticate patrons, and many libraries have patrons who primarily use online services, there is a need for the Patron Validate process to update the CIRCACTIVE field. This would ensure that these online-only users are correctly identified as active.
Nicole Turzillo
supported this idea
·
-
26 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Nicole Turzillo
commented
Given our current practice of using the Highest Level Overdue to block after billing, and the need to preserve the current overdue-to-bill interval across our 500+ loan rules, this new block must operate within those existing parameters. This would provide an additional incentive for returning overdue items before they are billed.
Nicole Turzillo
supported this idea
·
-
14 votes
An error occurred while saving the comment Nicole Turzillo
commented
Patrons may perceive repeated carousel images as a mistake, leading to a confusing experience. Providing the ability to customize the images for hybrid or recurring/series events would create a more polished presentation and allow for better highlighting of diverse programming.
Nicole Turzillo
supported this idea
·
-
22 votesUNDER REVIEW ·
AdminAngela Nolet
(Senior Product Manager, Innovative Interfaces, Innovative)
responded
An error occurred while saving the comment Nicole Turzillo
commented
Implementing either of these options would provide a logical safeguard against accidental registration data loss.
Nicole Turzillo
supported this idea
·
-
13 votes
An error occurred while saving the comment Nicole Turzillo
commented
For managing complex event series that may require different spaces, the capability to utilize multiple rooms feels like a core feature that should be inherent in Vega Program.
Nicole Turzillo
supported this idea
·
-
16 votes
An error occurred while saving the comment Nicole Turzillo
commented
Patrons currently utilize Preferred Search Alerts in WebPac/Encore and expect this feature to be available in Vega.
Nicole Turzillo
supported this idea
·
-
9 votes
An error occurred while saving the comment Nicole Turzillo
commented
Patron-type event registration is essential for libraries in large consortia, especially when neighboring libraries have shared, exclusive programming. This was a feature of Sierra Program Registration and is an expected capability in Vega Program.
Nicole Turzillo
supported this idea
·
-
35 votes
An error occurred while saving the comment Nicole Turzillo
commented
Our consortium relies on stat group reporting; this enhancement would allow us to obtain specific circulation statistics.
Nicole Turzillo
supported this idea
·
-
16 votesNicole Turzillo
supported this idea
·
-
9 votesNicole Turzillo
supported this idea
·
-
9 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Nicole Turzillo
supported this idea
·
-
5 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Nicole Turzillo
supported this idea
·
-
14 votesNicole Turzillo
supported this idea
·
-
8 votesNicole Turzillo
supported this idea
·
-
6 votesNicole Turzillo
supported this idea
·
-
14 votes
An error occurred while saving the comment Nicole Turzillo
commented
Using Mobile Worklists for In-House Use counts doesn't make sense if the count can't be recorded in the user's stat group.
Nicole Turzillo
supported this idea
·
-
4 votesNicole Turzillo
supported this idea
·
-
5 votesNicole Turzillo
supported this idea
·
Just like Jeremy's consortium, we have vendors that use a single key for multiple libraries. Consequently, while the API endpoints will need a stat group parameter for data separation, it would be a significant improvement in usability if the stat group could be assigned as a default to the key.