Settings and activity
171 results found
-
27 votes
An error occurred while saving the comment 
Eric Young
supported this idea
·
-
6 votes
An error occurred while saving the comment Eric Young
commented
We have confirmed this behavior during testing. When Vega Mobile is launched on iOS, any audio playing from another app such as Apple Music, Freegal Music, or Spotify stops immediately. On Android, background audio continues without interruption.
This difference is due to how iOS handles audio sessions. To achieve consistency across platforms, the iOS app would need to be configured to allow mixing with other audio so that background playback continues unless the user starts audio within Vega Mobile. See https://developer.apple.com/documentation/avfaudio/avaudiosession for more details.
Improving this would create a better experience for patrons who listen to music or audiobooks while browsing library services. We fully support this enhancement and encourage prioritizing it for future releases.
Eric Young
supported this idea
·
-
26 votesEric Young
supported this idea
·
-
10 votesEric Young
supported this idea
·
-
17 votes
An error occurred while saving the comment Eric Young
commented
Would love to be able to group IDs like patron codes, orgs, material types, TOMs, status and so much more. Some would simply be grouped as "Reporting" or "Non-Reporting", other groupings would be freetext.
Eric Young
supported this idea
·
-
52 votes
An error occurred while saving the comment Eric Young
commented
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.
Eric Young
supported this idea
·
-
36 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
·
-
38 votesEric Young
supported this idea
·
-
42 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
·
-
48 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
·
-
11 votesEric Young
supported this idea
·
-
23 votesEric Young
supported this idea
·
-
38 votesEric Young
supported this idea
·
-
31 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
·
-
10 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.
I want this with permission controls on who can toggle into this awesome power/advanced editor.