Settings and activity
125 results found
-
13 votes
An error occurred while saving the comment -
10 votes
An error occurred while saving the comment 
Eric Young
commented
I think this is less critical than MFA and if implemented it should allow for the customer to specify the masking criteria and outcome. Such as how many digits to display and which roles, if any, can unmask the full barcode. In our Polaris system for example, we only show the last 5 digits of a barcode to the patron in the PowerPAC, but with Vega the entire barcode is revealed.
Eric Young
supported this idea
·
-
15 votes
An error occurred while saving the comment Eric Young
commented
Totally support this idea!
Eric Young
supported this idea
·
-
47 votesEric Young
supported this idea
·
An error occurred while saving the comment Eric Young
commented
Yes, please! The display of information is from the MARC record is likely different for every library. It would be great if Vega staff offered a BibFrame view of the MARC data and allowed the library staff/vega admin to determine which data should be displayed and at what level it should be displayed.
-
82 votes
An error occurred while saving the comment Eric Young
commented
I fully support the integration of SMS signup directly within Vega. It would simplify user experience by keeping everything in one place, without redirecting them to the Polaris PowerPAC.
In addition to SMS signup, there are other important datapoints/features missing in Vega's Patron Profile screen that would benefit our patrons, as they have these values now in PowerPAC:
Card Type: Patrons need to know their card type to understand what services or borrowing limits they have access to. i.e. Full privileges or limited access, etc.
Date of Original Registration: This helps patrons see how long they’ve been with the library, which can be important for personal records or nostalgia.
Current Messages: Important alerts like "outstanding fees" should be visible to help patrons stay informed with details about their account.
Last Activity Date: Seeing their last login or activity helps patrons manage their engagement and keep track of their account usage.
Alternate Email Address: Some patrons prefer using different emails for library notifications to keep their inbox organized.
e-Receipt Preferences: Patrons want to choose how they receive receipts—whether by SMS, email, or not at all.
Email Reminder Notices: Opting into reminders for almost overdue items or expiring accounts helps patrons stay informed.
Username Setting: Allowing patrons to create a username would make logging in easier and more personalized.
Adding these features would greatly improve the user experience in Vega, making it more user-friendly and aligned with modern expectations. Starting with SMS signup would be a fantastic first step.
Eric Young
supported this idea
·
-
23 votes
An error occurred while saving the comment Eric Young
commented
Yes, 100% agree that "0 of X copies" is preferred.
Eric Young
supported this idea
·
-
25 votes
An error occurred while saving the comment Eric Young
commented
Vega's strategy of utilizing kiosk and collection sites aligns well with addressing diverse needs of target audience. Having the ability to inherit settings from the main site, like branding, navigation, would simplify site management. A main site inheritance feature would ensure that any updates to the main site's appearance automatically reflect across all inheriting sites, making admin tasks more efficient.
Eric Young
supported this idea
·
-
69 votes
An error occurred while saving the comment Eric Young
commented
I would like to add that Leap is a staff tool and should not be included with this logic. Also, the block should be configurable by the library under SA access.
Eric Young
supported this idea
·
-
13 votesEric Young
supported this idea
·
-
10 votesEric Young
supported this idea
·
An error occurred while saving the comment Eric Young
commented
Also increase the barcode itself in portrait view, both Android and Apple. Please!
-
24 votesEric Young
supported this idea
·
-
17 votes
An error occurred while saving the comment Eric Young
commented
This seems "easy" from an API standpoint at a high level. Notice queue comes into LX Starter, then an API call is sent to retrieve all items out and on hold, etc, adds those details to the notice and send...
I know, easier said than done but it is doable... please 🙏
Eric Young
supported this idea
·
-
14 votes
An error occurred while saving the comment Eric Young
commented
The inclusion of these merge tags is not merely an enhancement but a necessity for the feature to be considered complete and functional. Please also see and support the need for other missing merge tags.
Eric Young
supported this idea
·
-
31 votesEric Young
shared this idea
·
-
14 votesEric Young
supported this idea
·
-
53 votes
An error occurred while saving the comment Eric Young
commented
We need this before we move forward with Showcases.
Eric Young
supported this idea
·
-
37 votes
An error occurred while saving the comment Eric Young
commented
Following the recent implementation of LX Starter, we've identified a crucial need for a Non-Blocking Note to be added whenever LX Starter updates a patron's notice preference due to a spam marking. With our first batch of 6.8k messages, one was marked as spam, and without this note, it's extremely challenging for our staff to identify such modifications in the ILS. This feature would be in line with the existing system where a note is added for hard bounces.
For clarity, we propose the note to read: "Email address: xxxx@xxxxx.com was marked as spam on {MM-DD-YYYY at HH:MM pm/am}. Please update."
Thank you for considering this enhancement.
An error occurred while saving the comment Eric Young
commented
The added notes in the ILS will be extremely helpful as we don't plan on allowing staff to access LX Starter and having a full picture of what is happening with notices at the patron level in the ILS is key for staff success.
Eric Young
supported this idea
·
-
17 votesEric Young
shared this idea
·
-
11 votesEric Young
supported this idea
·
-
16 votesEric Young
supported this idea
·
I strongly support requiring Multi-Factor Authentication (MFA) for all users, regardless of role, as a critical step in strengthening overall security. Instead of creating a standalone MFA solution specifically for LX Starter, a more efficient approach would be to allow customers to configure Single Sign-On (SSO) with MFA through their existing identity management systems, such as Microsoft Entra ID or Google. This strategy enables customers to use their own trusted systems for MFA validation, consolidating authentication within a single, familiar platform. By reducing the need for multiple authentication sources, this approach simplifies security management, minimizes friction for users, and enhances control over access.