112 results found
-
Split High Item Count Communications Across Multiple Notices
Back in 2024, I had posted an enhancement suggestion requesting that LX Starter be more accommodating to libraries with high allowances for holds & checkouts. We found that patrons with a large number of items checked out that fell due on the same day did not receive the expected overdue notices for those items.
We learned from feedback on the suggestion that has since been closed that LX Starter's email server has a limit of sending emails that are 256KB in size. When emails contain a large number of items the size can quickly exceed this limit. For example, a…
5 votes -
Improve notice Performance link click data
Now that we are adding some additional marketing content to Hold Pickup Notices, it would be helpful to improve the data on the Performance tab for the notice. Currently, there is a massive list of links with the number of people and clicks next to each. This list seems to be for all time so it is difficult to gauge the effectiveness of a specific version of the notice template. Since we are updating notices monthly it would be helpful to be able to filter the data to see clicks from a specific time period (to get information about engagement…
5 votes -
Social Media Icons
A few suggestions:
1) Allow customizable colors using the swatch in 'Icon Type' so we can better match our theme
2) Remove the Tinder icon
3) Add a Podcast icon5 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,…
5 votes -
Add 'Text' Content Block
Current content block options for text include Heading or Paragraph. Paragraph blocks trigger design issues when used in a dynamic row, so in order to add a new merge tag, staff need to copy an existing Text block. Viewing an LX Starter training video, it looks like the Sequences tool once supported a Text content block. It would be helpful to have this option again in case all existing Text blocks are accidentally deleted from a notice template!
4 votes -
Limit Patron First Name merge tag to first name only (exclude middle name)
For Sierra users, LX Starter's current Patron First Name merge tag includes both first and middle names, as stored in Sierra as ID 80101 and ID 80103. I'd prefer the merge tag only include first name (ID 80101).
While middle names are important data points in Sierra's patron records, including middle names in modern patron-facing communications is unnatural in our region.
4 votes -
Force clear scheduled notice
Occasionally, an notice gets stuck in "scheduled" status in LX Starter even though, if you open the individual notice, you can see that it actually was sent. This issue was common prior to November 2024. Innovative made a change since then that seems to have drastically reduced the frequency of this problem, but when this does happen, it would be nice to have the functionality to be able to manually reassign the notice to one of the other notice categories (failed to send, delivered, etc.). Our library has 1,635 notices stuck in Scheduled status, and loading all those records slows…
4 votes -
Better invite for staff that is customizable by customer
Particularly important to consortia who have many staff to onboard...
It would be great to customize the staff login welcome with links to documentation, local contacts and urls.
4 votes -
Addition of Block Notice Type
Our library makes considerable use of the Manual Block field in Sierra. Beyond the Collection block, which patrons are more than made aware of through our initial notification process & then later, by our materials recovery partner, Unique Management, we have Manual Blocks for things like lost cards, bad addresses, etc.
Manual Blocks are designed to flag accounts & prevent circulation activity for any number of reasons. But since their introduction, service has evolved, where much of it is remote &/or relies on third party vendors, many of which may not be configured to recognize that a Manual Block is…
3 votes -
Ability to create more than 5 Language Templates
Currently there is a max of five different language templates that can be created in LX Starter. For some libraries, our in particular, we serve a district with seven official languages. With only five available language templates we are unable to serve all of patrons.
2 votes -
Improve notice Performance link click data
Now that we are adding some additional marketing content to Hold Pickup Notices, it would be helpful to improve the data on the Performance tab for the notice. Currently, there is a massive list of links with the number of people and clicks next to each. This list seems to be for all time so it is difficult to guage the affectiveness of a specific version of the notice template. Since we are updating notices monthly it would be helpful to be able to filter the data to see clicks from a specific time period (to get information about engagement…
2 votes -
Addition of Block Notice Type
Our library makes considerable use of the Manual Block field in Sierra. Beyond the Collection block, which patrons are more than made aware of through our initial notification process & then later, by our materials recovery partner, Unique Management, we have Manual Blocks for things like lost cards, bad addresses, etc.
Manual Blocks are designed to flag accounts & prevent circulation activity for any number of reasons. But since their introduction, service has evolved, where much of it is remote &/or relies on third party vendors, many of which may not be configured to recognize that a Manual Block is…
1 vote
- Don't see your idea?