51 results found
-
Allow option for Bounced email note in Polaris to be a blocking note
Allow the option for libraries to have the automated bounced note added to Polaris client patron record when email is hard bounced to be a blocking note. The blocking note alerts staff to verify the email information when the patron is standing in front of them.
5 votes -
Design a way to unblock a previously Hard Bounced email address
Once an email address has Hard Bounced, there is no way to unblock it and continue sending notices by email. We have had an example where a patron's email address Hard Bounced, preventing further notices from being sent to it. We have since confirmed that the email address is valid and can receive email but there is no way for us to unblock the address in LX Starter to try to resume sending email notices to the patron.
We have tried putting in a new email address and then re-adding the email address that previously bounced and LX Starter still…
13 votes -
Add "Reason", "Additional Info", and "Charging Library/Branch" Merge Tags to Manual Bills
Please add essential merge tags—"Reason", "Additional Information", and "Charging Library/Branch"—to the Manual Bill feature in LX Starter for Polaris libraries. These tags are fundamental to our billing processes and are conspicuously absent, impeding our ability to relay comprehensive billing details to patrons as is standard in Polaris' Manual Bill, as per the documentation in Polaris Staff Client Help - Bill a charge manually to a patron account (https://documentation.iii.com/polaris/7.5/Default.htm#PolarisStaffHelp/Patron_Services/PPuseacct/BillChargeManu.htm)
It's also come to our attention that Sierra libraries are encountering similar issues with missing merge tags, as highlighted in the idea titled "Library Name, Library Address, Branch Name, Branch…
14 votes -
library_name, library_address, branch_name & branch_address available in all Notices
I was informed by support that the new Fines, Bills & Fines, and Manual Fines available in the Sierra version of LX Starter do not allow the use of the merge tags "libraryname, libraryaddress, branchname and branchaddress." There might be other merge tags also not available in these notices. Support said, "the new notice types differ from the original ones in that they do not support the libraryname and libraryaddress merge tags. The product team decided to change the merge tag design when implementing the new notice types. This is an intentional design decision…
5 votes -
Branch Phone Number Merge Tag
If possible, I would like to see a merge tag for a branch's phone number. Right now, I have a link to our locations page with the contact info, but it would be nice to be able to put the branch phone number on the notice so patrons don't have to go to a different page to get it.
8 votes -
Allow us to change system roles
We cannot currently change the system role for a user, it would be much quicker to be able to modify the account than to remove them, log out, log in and then readd them with the new role.
10 votes -
Allow "admin" level users to send password reset links.
They can create and remove accounts but if someone they created doesn't click the link in time they need a super admin to resend that email.
9 votes -
Increase Notices Subject Line 78 characters to 100 characters
Increasing LX Stater Notice Subject Line from the new 78 characters limitation to 100 characters. The added characters in the Subject Line will benefit other languages than English that utilize more characters for the same message.
8 votes -
Regionalize alphanumeric date format in multilingual notices
Currently, LX Starter uses a single date format "across all notice emails". However, libraries sending multilingual notices may require alphanumeric dates which are tailored to the correct regional format on a per-language basis.
In Canada, for example, dates are rendered in French as "le 11 septembre 2023" and in English as "September 11, 2023" rather than "September 11th, 2023" as currently configurable in LX Starter.
While it is possible to use the "yyyy-mm-dd" numeric format as a workaround, LX Starter also suppresses the month's leading zero (i.e., "2023-9-08") which also conflicts with the bilingual numeric date format prescribed for use…
10 votes -
Ability to create folders in Design Blocks creation
Our library offers multiple languages, it would be efficient and a better UX experience to create folders that the user can then go in and create blocks tailored to it.
For organization, it would make sense to create a folder- ex. Spanish blocks > add/create all spanish content blocks.
The design blocks doesnt have a search function, so I have to go through and find what it is I'm looking for.
11 votes -
Activity Log Sorting
This is a very minor cosmetic request, but I'd appreciate it if the 'Show x per page' drop down in the Notice Activity Logs could appear at the top of the page instead of or in addition to the bottom.
We have enough bounced messages daily that we inevitably have to select 'show 50 per page' or 'show 100 per page,' & it would be nice to not have to first scroll to the bottom of the page to set that view option.
6 votes -
Patron choice for full account visibility with each notice sent
We have received feedback from patrons regarding post-introduction of LX Starter, and one common complaint is that the new emails do not display the complete details of all items currently checked out on their account. While this change appeared logical to most patrons, as they only receive notifications for items requiring action, some individuals are still dissatisfied that we no longer send the full account information with each notification. To address this issue, implementing a feature in 'My Account' that allows patrons to toggle between receiving complete account details or streamlined notifications would be a valuable addition, helping to minimize…
16 votes -
Include a Sandbox or Testing option for editing template designs
Include a Save As option, or some kind of sandbox/testing area in Template Design so users can play around with the notice design and save different versions before publishing.
16 votes -
Use the same patron record field for email address(es) as defined in Admin Corner
Since Sierra permits libraries to define an alternative variable-length field tag to reference for the patron email address – see attached Admin Corner screenshot – LX Starter should either follow the same customization or at least permit its redundant definition in the LX Starter configuration.
As much as we would like to switich to LX Starter for notices, we cannot move forward until the product supports this same customization.
To be clear, we DO still store conventional patron email addresses in the z - Email field, but if the patron also/instead wishes to receive SMS notices via an SMS-as-email service,…
3 votes -
5 votes
-
Include MANY more patron fields as Merge Tags
Looking through the available merge tags, I see very few fields from the patron record represented: First name, last name and patron barcode. When I attended webinars on LX Starter many months ago, I could swear the audience was told that all fields exposed to the print templates interface would likewise be available in LX Starter.
Having read the Idea Exchange post https://ideas.iii.com/forums/951985-lx-starter/suggestions/46813306-take-a-good-hard-look-at-patrons-data-privacy-in, it is clear that many of these patron record fields are being passed through to LX Starter, so please make them available for merging and/or to drive conditional logic (which is a whole 'nother suggestion).
11 votes -
Use library email addresses for email testing.
When testing the email workflow in LX Starter, the emails are currently sent from vega@iiivega.com. Instead, it would be better to send test emails from the actual email addresses configured for the library.
This would more fully validate the end-to-end email process and catch any issues before LX Starter is live, as reliable email delivery is critical.
Benefits:
- Tests the full email process from the library's email address
- Catches email issues before product launch
- Validates reliability of email workflow before sending emails to patrons.
Suggested Implementation:
- Update the LX Starter email test feature to send from the configured library…
19 votes -
Plain Text option in LX Starter
Allow customers an option to keep plain text email notices in LX Starter.
Polaris ILS has a Y/N option in the patron record for "email notices in plain text".
I would like LX Starter to check and honor this option in the patron record and format email notices according to this preference.(snip of patron registration/OPAC self registration view attached)
10 votes -
Allow for multiple "audiences" so that we can use different language when communicating with different patron types.
Our library uses different language when communicating with faculty versus students, and we would like the functionality to break up the audience into groups based on patron type. Ideally, we would then be able to have notices that are specific to each audience group.
5 votes -
Display sent to email address in notice history
In Activity history in the LX Starter dashboard, also display which email address a notice was sent to.
It would be helpful to see which email address a notice was sent to. The patron may have recently changed their email address and troubleshooting notices would be easier if you could see this history.
11 votes
- Don't see your idea?