53 results found
-
Expired patron transition
We would like Polaris to transition expired patrons to Deleted after a specified time frame. (Such patrons would of course need to have no lost items or checkouts.) We envision this working like Lost Item Transition and the Missing Item Transition. Ideally, we could also set a fine threshold to only delete those expired patrons with less than a certain amount of fines on their cards.
Adding this feature would allow a library to automatically remove expired patrons and allow for a more streamline process for deleting the ones they wanted.
21 votes -
remove notification for cancelled items
It would be nice if from the staff side in Polaris and LEAP we could select whether to notify the patron if an item they placed on hold gets cancelled. Sometimes we have to cancel holds for various reasons and LEAP is often faster in notifying the patron with no context when their request was cancelled which can cause confusion for the patron. Staff should get the option of whether a patron gets notified or not and if possible, if we could have the option to add a message to the cancel notification they get.
Relatedly, patrons should get a…28 votes -
Export email notices
We already have the option in 7.6 to export print, phone, and TXT notices via the native Polaris admin settings. The only format that cannot be exported is email.
It would make notices integrations to third-party and other hosted solutions more accessible and easier to maintain if the same functionality were supported for all notification methods.
6 votes -
subject headings to browse
Polaris Leap--Be able to use subject headings to browse/search while in Leap without having to go into the PAC.
15 votes -
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.
6 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.
4 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…
16 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
15 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.
52 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.
11 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.
76 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…
24 votes -
LEAP - Picklist processing display - customize fields (exact fields TBD)
Currently the picklist processing report is as-is with no options to modify.
We've found it would be helpful for our library to have the last activity date to display when printing the picklist as items may have been returned within the last few days and on their way to being re-shelved or possibly on shelf for years & actually missing. Thinking others may have additional fields that would be of use to them as well.
It would be a helpful enhancement for staff to have the ability to choose additional fields to customize & re-arrange the columns on the picklist…
84 votes
- Don't see your idea?