648 results found
-
Expand Bulk Change to allow editing
Currently, Bulk Change allows staff to replace existing information in free-text fields, and add to the beginning or end of the field in some cases. However, existing text cannot be edited.
For example, if a group of item records need the volume numbering changed from “v.” to “vol.,” Bulk Change cannot update all the items if they have different volume numbers. Staff have to replace “v. 1” with “vol. 1,” then do all the v. 2s, then v. 3s, and so on. Similarly, if a library discovers that some of its records have incorrect diacritics, each word must be changed…
58 votes -
Block patrons with lost items from checking out on SIP2 selfcheck
We'd like to block patrons from checking out on selfcheck units if they have lost items. Even though Polaris SA has a configuration in place, that setting only works for API setup, not sip2. we'd like to have a similar setting for sip2.
16 votes -
Trap hold with first item received
Our libraries in our consortium are frustrated when items from other libraries arrive to fill holds for their patrons and their own copy is sitting on their shelves, making the process look rather inefficient.
What I think might solve this is implementing SirsiDynix's "Trap hold with first item received" feature. Rather than try to explain it myself, I've quoted it from their website below:
"Using the "Trap hold with first item received at pickup library" feature, the system can be configured to allow filling a library user's hold with the first holdable copy of an item received at the pickup…
43 votes -
Send patrons a notification when holds go into Not Supplied status
Unless patrons are regularly monitoring their account (some don't even do this at all) they would have no idea when their holds go into Not Supplied status. Having a notification for this would alert them to take some sort of action (try to reactivate if possible, order another edition/version, contact the library for other options).
24 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 -
Bulk waive criteria should allow user to specify maximum or minimum amount of charge to be waived
The new(ish) bulk waive options in Leap are extremely useful, but library administrators often want to waive charges of a certain amount - usually "waive all charges of less than X dollars." The current interface, however, doesn't allow the user to specify an amount for the charge to be waived. This would be very useful and would avoid the need for creating a SQL statement to identify such charges. The scenario of waiving all charges greater than a given amount is less likely, but if you're adding the ability to specify a maximum, why not add the option for a…
7 votes -
Ability for staff to bulk change a patron's pickup branch
Staff would like to be able to bulk change a patron's pickup branch for selected (or all) holds on the patron's account. Be they holds already trapped, suspended or active. We often have patrons that move from one part of the area to another and need to change their holds to reflect their new pickup branch. Having to change one hold at a time is tedious.
10 votes -
Add support for Preferred Borrowers that applies to checkouts as well as holds
In larger consortia, it's very impractical to have granular patron codes per library or branch. Our resident patron codes are shared by all the libraries, but this creates some problems for certain materials that libraries can't reasonably share. The Preferred Borrower hold limit can help with this, but it puts the control of circulating restricted materials on the staff. If a Preferred Borrower setting could apply to checkout of certain materials the way holds can be limited with Preferred Borrower settings, staff would not have to struggle with overrides or demanding patrons from the next town over.
3 votes -
Leap - allow for adding selected records to a PO or selection list
Please add more options for adding records in a record set to purchase orders or selection lists in Leap. Currently, the only actions in Leap are to bulk add records to a new or existing PO; the Polaris client also has options to add all records to a new or existing selection list, to add selected records to a new or existing PO, or to add selected records to new or existing selection lists. (See screenshots.)
11 votes -
Staff's ability to make item bulk changes should follow permissions for item record change
Currently item bulk change functionality allows staff to bulk change fields that they can't change in individual item records. This allows staff to modify item records using bulk change when they're blocked from modifying directly in the item record. The same permissions should apply to bulk change:
• Item records: Modify cataloging view
• Item records: Modify source and acquisitions view
• Item records: Modify reserves view
• Item records: Modify history viewThe library feels this is a data security risk. Fundamentally, here is the question: what is the purpose of the permission Item records: Modify cataloging view?
If…
58 votes -
Registration renewal option to add a renewal period on top of the existing expiration date
We have paid non-resident fees which get used for unique patron codes which last 1 year. If a customer is renewing their registration early, we give them a year from their expiration date so that they are not losing any of the time that they previously paid for. Perhaps a checkbox in the renewal dialog box to indicate that this is what we want to do, but also an option to have this automatically toggled for certain patron codes and an option to suppress its use when an account is fully expired.
7 votes -
Append Hold Pickup Slip to Hold Slip
There are already some other ideas/requests for additional Hold Slip configurations and, while I fully support any additional receipt configuration, they're scope is pretty broad. Meanwhile, this is a pretty specific idea/request that I would hope could be implemented easily. The subject pretty much says it all, but we would like the ability to append the Hold Pickup Slip to the Hold Slip. Currently, it is only possible to append the Hold Pickup Slip to the Hold Call Slip (not a particularly distinct name...) which prints ALL of the patron's available holds. This can result in some VERY long receipts…
3 votes -
Include Call Number Field in SIP Item Information Response (18) Message
No that we have migrated from Sierra to Polaris, the call number field is not included in the SIP response when using an inventory wand. At this point we only see the barcode and title of an item, which makes it more difficult to find identified items.
21 votes -
Using Shift + Click for holds
Staff would love to be able the ability to use Shift + Click to select a range of hold requests in the Leap Patron record Holds view. This is an option in the Items out view (as well as in the Find tool and record sets) and it would be great it this could also be added into the patron Holds view.
7 votes -
Undo/Redo Buttons in the Leap MARC Editor
In the Client, there are undo and redo buttons. The undo button is particularly useful when someone has made a mistake. It quickly allows staff to correct the mistake by pressing a single button. When training technical services staff to use Leap, this button is clearly missed. Having this button will make the transition to Leap easier. Questions and comments about the lack of the undo button are common during training.
108 votes -
Saving Registrations in Leap
My library is on Leap 7.6 and we have a problem when our staff is setting up new registrations. The “Save” button is right next to the “Cancel” button and when you accidently hit cancel there is no “Are you sure” pop up or something similar. We would love for this to be fixed! We've had to redo way to many patron accounts!
18 votes -
Add Power Search features to Leap's OmniSearch
The usefulness of the OmniSearch box in Leap would be greatly enhanced by the addition of operators and Power Search (CCL) features so an experienced Polaris user could execute their search right away, in the OmniSearch, and get the results back in a Find Tool. As it is, if I want to search for, say, an item record, I need to:
- Click Find to launch the Find Tool
- Change the search type to Item Records
- Change whatever parameters I need to change after that.
- Maybe add a filter or two and then apply those filters
- Go back to the Find…
18 votes -
Launch bib record compare from Find Tool
It would be really helpful for fixing rollups if you could pick records to compare directly from the Find Tool instead of opening one record and then running a search again to find records to compare!
43 votes -
Provide additional reporting options for In-House Use
In-house counts are very important for informing staffing and collection maintenance. It would be great to have more options around in-house beyond YTD and Lifetime counts. For example, it would be helpful to run reports on the amount of in-house use within a specified time frame in both item list and item count reports as well as the ability to run item statistical reports on in-house use.
5 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
- Don't see your idea?