33 results found
-
Select which notices are sent to multiple e-mails
Currently, it seems that we can opt to have all e-mail notices sent to the primary e-mail on an account, or all e-mail notices sent to both the primary and alternative e-mails on the account. We would like to be able to choose at the notice level whether a notice is sent to the primary e-mail or to both. This would allow us to, for example, send billing notices to both e-mails, but receipts and renewal notices only to the primary e-mail.
1 vote -
Change it so that failed logins don't update last activity date
Right now in the Polaris SIP environment, if you attempt to get patron information using a 63 message, but you put in the WRONG password, the patron accounts LAST ACTIVITY DATE will STILL be updated.
We recently had a vendor that for some crazy reason, went through and was attempting a 63 message for all patron barcodes they had on file. This updated the last activity date for tens of thousands of patron accounts.
Although I suppose there could be some arguments for this behavior, it should not be the default. By default if an account login FAILS, for any…
24 votes -
Collection Agency Reporting by Item Library - Only block patron once
Collection Agency Set Up: Can we add the ability to filter out patrons who already have a collection block when we send by item library? Due to financial reporting requirements, we have to send by item library but find many of our patrons end up with more than one collection block which we then need to remove.
3 votes -
Prevent update of patron code for patrons in collection (Susan Millwater)
Since you can exclude patron codes that are submitted to collections, you shouldn't be allowed to update the patron code for a patron in collection. We've found that any updates to fines and fees will not be sent to collection management (UMS) and the collection block will not be removed for a patron in collection if they now have a patron code that is excluded from collection.
4 votes -
Allow Staff to Select City/Town When Multiple Locations Share the Same Postal Code
Currently, there are two options for handling postal codes, which I like to term: “Wild West” and “In Lock Down”. The postal codes are collected and managed within the Postal Code table in Administration>Explorer>Database Tables. Staff functionality is governed by the permission Patron registration: Modify postal address fields.
The Wild West option is to allow staff the permission to enter any address information provided by patrons, resulting in a table populated with a lot of incorrect city/town to postal code data. This way lies madness and continuous clean-up.On the other hand, removing the permission from staff logins, puts them…
6 votes -
Allow libraries to customize info displayed in Leap Patron Record header and properties
We need a way to bring perennial critical patron info to staff attention without creating blocks for customers or forcing staff to open the full patron registration. Having this info in the patron record header or properties would be ideal. For example: at our library, customer registered at branch is not critical info yet it is the most prominent value displayed in the header after name and card number, if we could designate UDF values to take it's place (such as bookmobile stop or language assist needed) or have space to reveal a designated UDF value under patron properties, it…
9 votes -
(SMS - Cirriusimpact) Allow for Almost Due / Auto-renew to patrons by phone
Allow patrons to receive Almost Due / Auto-renew messages through the SMS - Cirriusimpact product integration.
10 votes -
Search LEAP by username
LFPL would like the ability to search for patrons by their username in LEAP without having to use the SQL search
7 votes -
Add a feature for "weeding" inactive patrons similar to the new weeding workflow in 7.5
It would be great if staff could create a record set of patrons to delete and a supervisor could review them before deletion, similar to how item records can be reviewed in a record set by a supervisor before deletion.
10 votes -
Turning off Item Renewal at the Patron level
I would like to be able to adjust auto-renewals at a Patron level in addition to the item level. This would help some of our patron's who may have difficulty understanding how renewals work. This may seem silly, but we have had some cognitively impaired patrons become severely confused and upset when they think they are "wasting renewal's". Being able to adjust these settings individually at the patron record portion would be extremely helpful. Excluding them from the auto-renewal notice is a band-aid, but this causes other confusing issues with the patrons as a result.
7 votes -
Re-arrange records in the Workform Tracker
It would be handy to be able to re-arrange records listed in the Workform Tracker. Sometimes I'm using a few records for some activity, and it can be confusing to keep track of them (especially since hold queues, hold records, items and bibs can have the same name, even if the icons used are different). The ability to change their order would allow some flexibility, such as allowing a user to place a hold record with the patron record they "belong" with.
4 votes -
Upload patron barcodes into a record set
The add from file feature in patron record sets should allow importing by patron barcode in addtion to patron ID.
22 votes -
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.
38 votes -
Outreach alert during hold creation
A request for an enhancement from our Homebound Services (Outreach) department: In Reading History, it would be beneficial to generate an alert (has had) from the Reading History when placing a hold, not during check out of the item. Presently, the current setting notifies staff at check out whether the patron has had the title already.
20 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 (?)
30 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.5 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.
7 votes -
reading history
Reading history improvements, allow for more then 9,999 and allow reading history to be searchable on staff and patron side.
12 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.
24 votes
- Don't see your idea?