628 results found
-
Make the chronology date field manually adjustable in serial check-in boxes
When a serial holdings record includes a pattern for a completely irregular issue, and the only chronology date on the issue is the year, the chronology day and month chosen when the publication pattern was set up is used for all following issues checked in using that pattern. The ability to manually adjust the chronology date would be very helpful, and would ensure that issues display in the correct order.
In the attached image, the expected date shows the date that the issue was actually received. However, because the chronology date for the first completely irregular issue we received was…5 votes -
Bulk delete ILL-requests in Leap
When searching by ILL-Request in Leap for a specific date range, I would like to be able to Shift + Click to highlight and add to a record set to perform a bulk delete.
5 votes -
More granular permissions for patron registration workform
We would like to be able to limit who can change the Expiration Date and Address Check Date in the patron registration workform. Off the two, Address Check Date is most important as this is what we use to make sure patrons are updating their information regularly.
These are configured in SA and are set system wide yet staff continue to change them.
If I remove the 'Patron registration: Modify permission' for member library staff, they won't be able to change other fields.
5 votes -
Allow setting continuity pattern at the first level of enumeration
We have some serials that only have one level of enumeration, that resets annually (i.e. no. 1 is published in January and no. 12 is published in December and there is no volume number). It would be nice to have option to set the number of units and the continuity at this level.
5 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.
5 votes -
Registration Drop Down Box
Please add a drop-down box for the profile section of registration. There is a drop-down box for the address section labeled term but there is not one for the profile section. It makes it easier for staff to choose the correct date. In the Polaris toolbar, there is a drop-down box for patron info and address.
5 votes -
Add patron blocked to AuthenticatePatron API endpoint
It would be helpful to have an indicator for if a patron has circulation blocks in the response of the AuthenticatePatron API endpoint. This would allow vendors and custom integrations to determine if a patron should be allowed access to a system based on if they are allowed to checkout items without having to do an additional API call.
5 votes -
Leap Offline patron data tables should be purged - PII Concern
When leap offline data is uploaded, it goes into [LeapOfflineTransactionDataID]. This contains PII information of the items & patrons that performed CKOs. However, this data is never cleared by the system, even after it is processed.
I can see keeping it around for awhile, but maybe have it follow one of the other settings in SA for purging data or set up a new SA setting for purging this PII data.
5 votes -
Polaris integration with Kajeet
More and more libraries circulate mobile wifi hotspots to the public. Polaris and Polaris Leap do not currently integrate with Kajeet, which is one of the more popular wifi hotspot providers for schools and libraries. It would be beneficial to libraries using the Polaris ILS to be able to streamline the circulation process such that checking in/out a hotspot in Polaris also activated/deactivated the hotspot itself.
5 votes -
Default patron codes - Make Leap function like the Polaris Client
When a patron's registered branch is updated via Leap but their existing patron code is not available at the new branch, Leap assigns the first patron code alphabetically by default. The Polaris client, by contrast, applies the default patron code for the new registered branch. Please follow the patron registration default patron code for that location in Leap, as happens today in the Polaris client.
5 votes -
LEAP - Outreach Services - automatic print packing list during CKO
LEAP - Outreach Services: When processing held items in Outreach Services, items for a patron will deselect after checking out. This requires staff to go back and reselect the desired items to print a packing list.
The ability to turn packing lists on such that they print with CKO would be appreciated.
A prompt to "print packing list?" during CKO would also work.
5 votes -
Add POLI record ID to header (Leap)
Currently the POLI record ID is only visible as part of the url in the browser. It would help staff to more easily differentiate between multiple POLIs for the same title if the unique ID was included in the POLI header and as a column in the PO.
4 votes -
split screen in patron record fix
There are times when staff will have a split screen when working in a patron account (ex: puling patron account info to fill out a separate form), but with how the screen looks in that function, it can be difficult to navigate. Particularly because the left hand menu gets interlaid over the information fields. Ideally, the image on the screen would adjust with the size of the screen- allowing for a (smaller version) of the full screen to be viewable or at least the ability to scroll over or down more easily.
4 votes -
Allow searching more than 10 remote databases at a time in Leap
There's no limit (that we've run into, anyway) in the desktop client to the number of z39.50 remote databases you can search at a time, but Leap has implemented a 10 database limit. If there needs to be a limit, can it be slightly higher at least?
4 votes -
Separate permission for offline upload (Bookmobile) and patron import in Leap
Our consortium still uses the Polaris staff client for a couple of functions - primarily for offline circulation during upgrades and emergency outages (loss of internet or urgent server maintenance). For this reason, most senior circulation staff have to have the "Access patron import" permission as that controls access to the Bookmobile offline upload process. But we don't want all senior circulation staff to have the ability to import patron records - we want that to be limited to a very small group of staff who have been cleared to handle student data files (and have the approved secure file…
4 votes -
Ability to create a child record in Leap and link to the child record
In Leap, the parent/child item relationship is currently limited and does not support full navigation or management between linked records. To support a complete workflow in Leap, the following enhancements are needed:
- Add the ability to link from a parent item record to its associated child item record (currently, linking is only possible from child to parent).
- Add the ability to create a child item directly from an existing item record.
These features are essential for fully managing parent/child item relationships within Leap.
4 votes -
POST and DELETE methods for Record Sets
Currently with PAPI there is the ability to GET the contents of a Record Set and PUT additional records into Record Sets. We would love the Record Set API to be fully built out with POST methods (to create new Record Sets) and a DELETE method (to delete an existing Record Set).
4 votes -
Configure Notification Options Based on Patron Attributes
Currently, notifications in Polaris can only be filtered by branch. For example, one branch can enable specific notifications and another can disable them. We would love the ability to apply more granular filtering to determine which patrons receive certain notifications.
A workflow for us is billing notifications. Our library policy exempts certain patrons from billing based on their Patron Code. Because Polaris does not currently allow notifications to be filtered by Patron Code, we must manually work around the existing workflow to align with our policy.
We would love the ability, within SA, to filter notifications by patron attributes such…4 votes -
Reading History - Add Check In Date
Reading History presents only a partial view of the transaction lifecycle. While it shows when an item was borrowed, it does not show when it was returned.
This creates several practical issues:
-- Staff cannot easily confirm whether and when an item was returned
-- Additional steps are required to investigate the item history, which are time-consuming and cumbersome
-- It introduces confusion at service points, particularly when responding to patron queries about past borrowing activityCould a “Check In Date” column be added to the Reading History grid in Polaris Leap to provide a more complete and usable record…
4 votes -
Clarify Transaction History Display Behavior
When viewing a patron’s transaction history, selecting a transaction displays the related/paired transaction (e.g., waive vs. original charge). This behavior is working as designed but creates confusion because the displayed details do not match the selected row.
Current Behavior
• Staff select a transaction (e.g., a charge from 2/23/26) and select the history button.
• The system opens a detail view showing the associated transaction (e.g., the waive from 3/26/26).
• This makes it appear as though the system is pulling incorrect or reversed data.User Impact
• Causes confusion and lack of confidence in the accuracy of transaction records.…4 votes
.png){kind=link}
- Don't see your idea?