10 results found
-
Auto update member code from Junior to Adult when they turn 18
Having member codes change automatically based off patron age, changing junior to adult when they turn 18.
7 votes -
When patron barcode changes, auto-update with Libby
Currently when a patron replaces their library card and gets a new barcode, staff have to manually reconnect them with their Libby account, which is connected to their old card number. This update should be automated so that patrons who lose their library cards don't also lose access to Libby or other eResources. I'm not sure if this would require an update to the API (?)
18 votes -
Send out account expiration reminders as part of the eContent integration.
There can be accounts that are expired and are still able to check out ebooks. Expired accounts are no longer valid and should be blocking at least in the integration function between the ebook vendor and Polaris.
If this isn't possible, can the checkout action trigger an email notice to the customer to have their library account renewed or reviewed.
This should happen each day an integrated eContent transaction occurs.
Keeping the account up to date will prevent the account from being closed or purged.4 votes -
Separating "Ready for Pick Up" and "Renewal" text notifications
It would be nice if we could separate the "holds ready for pick up" texts from the "renew" texts and be able to choose if you want one or the other or both. Customers would love to get a text for when their holds come in, but for some, the renewal texts are too much, and the pick up texts get lost in the volume. Then also, have the option to get renewals and/or pick up notices in their email.
4 votes -
Patron reminder for upcoming address check
Have a reminder for patrons via TXT, email, telephony, mail-whatever their preference is, to remind them about their upcoming address check. Many patrons do not bring something with their current address with them when they come to the library to grab a book. This could be helpful for both staff and the patrons.
4 votes -
reading history
Reading history improvements, allow for more then 9,999 and allow reading history to be searchable on staff and patron side.
8 votes -
Registration/Renewal period based on patron code
We would like to be able to edit the default registration/renewal period based on the patron code rather than just based on the branch. We have certain patron codes that should renew for 1 year instead of our default of 3 years, but they don't have a unique branch in Polaris so we have to change the registration period each time we create a patron, and we have to change the renewal period each time we renew them, leaving more room for error if those steps are missed.
17 votes -
Show warning dialog before deleting reading history
In the patron registration form in LEAP there is a reading history checkbox. If the patron has a reading history, clearing the checkbox and saving the record deletes that reading history permanently, and there is no warning to staff about what clearing the checkbox actually does. On clearing the checkbox, please add a warning dialog that says, "This patron's reading history will be permanently deleted. Please confirm that you want to delete it." [OK][Cancel] with focus on Cancel. This way staff will have to confirm overtly that they want to delete patron data and will be less likely to make…
26 votes -
Automate lost card number request via email option in PAC
Automate lost barcode number requests. The simple way to achieve this is to offer this option below "Forgot your password" on the PAC login screen. The user clicks this and is asked to enter in the email address connected to the account in addition to first and last name. The patron associated with that name and email address would receive an email with the barcode. If the patron does not have an email on the account, or the wrong email address is entered, the user receives an error message.
Idea Value
This would save staff time in person and on…9 votes -
Remove Branch Requirement from Patron Bulk Change
Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.
This was previously submitted in the old enhancement process:
"Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can…
11 votes
- Don't see your idea?