37 results found
-
Allow for customization of the Notification preferences dropdown in PAC self-registration
In order to require patrons who are self-registering via the PAC to choose a notification preference, please remove the 'none' option from the Preferences dropdown, or at least allow for the option to customize what appears in the Preferences dropdown. By removing 'none' - or allowing for the option to remove it - patrons would effectively be required to provide a notification method, which would allow the library they are self-registering with to easily contact them should any problems arise with their application.
11 votes -
Enhanced Patron Privacy (UDF)
Patron Privacy is becoming a much larger issue. We currently use a UDF to hold our Patron ID.
We'd like to suggest that having the ability to create some way to collect and keep private patron data such as an ID or other PII would be ideal. And having this information encrypted in the database would be preferable as well.
Being able to prevent this information from always showing, would be a benefit and even having the ability to only show a part of that information, such as the last four digits or something similar, would be useful.
3 votes -
Collapse Name on Identification Fields
Staff have suggested that the Name on Identification area of the Leap registration form be collapsable, so that it will only be accessed if absolutely necessary. This measure would be an extra step in ensuring a patron's privacy, if a staff member accessing the record doesn't need that particular information.
2 votes -
Clearer messaging when an invalid barcode is used in a password reset
A patron was using their former barcode to try to do a password reset, and before we realized what the issue was, the system told them they 'had no email address' associated with that account. It would be more helpful if the system told them the barcode was invalid or, even better, that they were using an old barcode.
7 votes -
Leap doesn't save or prompt to save notes when you close a record
- Open a patron record in leap
- Navigate to the notes section
- Make a change to the note field
- Click the button to close the note (upper right hand corner)
The note is not saved, nor is a warning message shown. This is different from the behavior of the desktop, which always saves the note when you close the record (not really the preferred behavior either since there is no undo in notes).
This should work the way changes to the patron registrations work in Leap - warn there has been a change before allowing the record to be closed.
16 votes -
Changing Lost to a Claim
We have customers who do not pay attention to their notifications and an item gets declared Lost that they believe they have returned. I would like to have the option of taking an item that was declared Lost and making it Claimed Returned and even better if it could auto-waive any associated fines.
9 votes -
Generate Alert when Applying An Adult Patron Code for Minor Applicant
When creating a new account in Leap, it would be helpful if when the date of birth was less than 18 years from the registration date AND a patron code for adult patrons was selected, that an alert would display prior to saving, as we see for missing DOBs or other fields.
It should not be a hard block, as it is possible for someone under 18 to register as an adult, but the alert would catch attention to remind staff to confirm/correct during the registration process.
5 votes -
More chances for automatic renewals
Right now, automatic renewals happen 3 days before the due date. If the item someone has out is supposed to fill a hold for someone else then it never automatically renews even if another item ends up filling that hold. There should be a schedule for automatic renewals to occur 3 days, 2 days, 1 day, before the item is due and the day the item is due so there are multiple opportunities for that item to automatically renew in the event that a hold gets filled by another library and that item is now eligible for renewal again. It's…
19 votes -
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.
12 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…20 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.
3 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.
12 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.
3 votes -
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…
31 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…
7 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…
13 votes -
Polaris 7.8 - Allow for Almost Due / Auto-renew to patrons by SMS
Allow patrons to receive Almost Due / Auto-renew messages through the SMS - Cirriusimpact product integration.
12 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
9 votes
- Don't see your idea?