Settings and activity
172 results found
-
45 votes
An error occurred while saving the comment 
Eric Young
supported this idea
·
-
28 votesEric Young
supported this idea
·
An error occurred while saving the comment Eric Young
commented
This feature is critical for maintaining system integrity and accountability. Without a detailed, searchable audit trail, we’re left guessing when something breaks or changes unexpectedly. Requiring admins to enter a short comment when saving a setting, such as a ticket number or reason, would add essential context. These notes should be stored and searchable alongside the change log. This would significantly improve traceability, support workflows, and align Polaris with modern administrative standards.
-
14 votesEric Young
supported this idea
·
-
11 votesEric Young
supported this idea
·
-
27 votesEric Young
supported this idea
·
-
37 votesEric Young
supported this idea
·
-
30 votes
An error occurred while saving the comment Eric Young
commented
Letting users expand the Find Tool to full screen would improve flexibility and user experience. Typically, apps use persistent or expandable search tools rather than modals.
Eric Young
supported this idea
·
-
46 votes
An error occurred while saving the comment Eric Young
commented
So many moving parts, it is easy to miss something as important as this and having the option would improve workflow for many!
Eric Young
supported this idea
·
-
14 votes
An error occurred while saving the comment Eric Young
commented
Adding eReceipts as an option in LX Starter with the ability to customize them would be a significant enhancement. It would allow libraries to provide a more professional and visually appealing experience for patrons. HTML-based eReceipts could include branding, logos, and structured layouts, making the communication clearer and more engaging. This feature would align with modern expectations for digital communication and improve the overall user experience.
Eric Young
supported this idea
·
-
10 votesEric Young
supported this idea
·
-
16 votes
We will be adding a permission to address the issue of users with general access being able to reach the PAPI keys. There are some other comments here that could be considered separate enhancements, so please open new ideas for changes beyond a PAPI Key Management permission.
An error occurred while saving the comment Eric Young
commented
It is sad to think the security related idea had been here for 3+ years and nothing...
This is just more proof that Idea Exchange needs improvements!
An error occurred while saving the comment Eric Young
commented
Yes please!
Eric Young
supported this idea
·
-
22 votesEric Young
supported this idea
·
-
38 votesEric Young
supported this idea
·
-
29 votesEric Young
supported this idea
·
-
13 votes
An error occurred while saving the comment Eric Young
commented
Yes, it is critical that PAPI offers the ability to improve what SIP2 offers. Currently PAPI does not include a field for generating receipt or communication text, i.e. the Print Line (AG) field or Screen Message (AF) from SIP2. These values are needed to ensure communications on devices and receipts are properly set even if we have to repopulate the desired text in a new policy/database table.
Eric Young
supported this idea
·
-
9 votes
An error occurred while saving the comment Eric Young
commented
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.
-
9 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
·
-
111 votes
An error occurred while saving the comment Eric Young
commented
Yes, this issue specifically affects our kiosk sites, where the initial concern was raised. While Innovative successfully resolved this issue for Collection Sites used by Consortia customers, the solution has not yet been applied to kiosk sites. Currently, we're exploring ways to customize our site code to remove cookies on kiosk sites, as they provide little value given the existing limitations. It would be ideal if Innovative could implement the same or a similar solution for kiosk sites, as they did for Collection Sites.
An error occurred while saving the comment Eric Young
commented
Will not use Kiosk sites without this corrective action. This is a must fix situation. Great write up, thx
Eric Young
supported this idea
·
-
43 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.
Transaction records only get someone so far and they don't identify what was changed. This is a much-needed improvement to Polaris, please escalate this to meet today's information standards.