604 results found
-
Eliminate the barcode requirement for placing holds on on-order multivolume set records and serials
At this time, holds on the serials and multivolume set records are not functioning in an efficient manner when the title is not under serial control. Examples include manga, college guides, or test prep guides. In PowerPAC and Leap, patrons and staff cannot place volume level holds when the associated item is on order and does not have a barcode. It is not part of the staff's normal workflow to add a barcode to on-order items until the physical item arrives at the library. As long as a volume is in the volume field, Polaris should be able to identify…
45 votes -
Add “Show SQL” Button to SimplyReports
Summary:
It would be extremely useful to have a “Show SQL” button available for both ad-hoc and saved reports in SimplyReports.Background and Problem:
There are currently well-known workarounds that allow users to view or reconstruct the SQL generated by a report, but they’re tedious and time-consuming. These methods often involve extra steps like exporting report definitions, or having to view the page source after scary looking resubmission warnings. For users who need the SQL quickly, these barriers can be a significant slowdown.Proposed Solution:
Add a “Show SQL” button directly in the report interface—both for ad-hoc reports and saved…37 votes -
Option to tell customer if they have already read a title
An option added in the patron registration that turns on a "loan tracking" feature. When checking out books, if this feature is turned on, then when a barcode is scanned that the patron has already borrowed a message comes up to let the patron know they have already read this title.
Would check at a bib level (so not just the actual item that is scanned, but any bib that item is associated with). Should be based on what is in the reading history of the account. Would need enhancement for serial issues, as the reading history currently only advises…30 votes -
Allow for creating links to bib records from within an authority record
This might be coming in 8.0 - it's not on the roadmap, but maybe it's too small to feature there. In the Polaris client, within an authority record, there is an option to create links to bib records (see attached screenshot). This same functionality should also be included in Leap in order for cataloguers to fully switch over to Leap.
27 votes -
Support EAN for Syndetics Images
At this time, the EAN is not being used to add the images from Syndetics to the PowerPAC or Vega. There are many products that have EANs instead of UPCs. Many libraries have been requesting that images be added for these products so that patrons can have an idea of what the item is before they check it out. We have asked Syndetics about it and they do have the images for these products. In fact, the images are appearing in Leap. Given that the images are available, the PowerPAC and Vega should have this capability. It will enhance the…
46 votes -
Item template use in Leap
Currently in Leap (we're on 7.8), in order to take full advantage of an item template, you have to click on Actions--Create Item (within the bib record), then add your barcode & select the template you want to use, and then click Save. If you don't click on Save, the template only populates some of the template information. It doesn't change any of the call number fields or the number of renewals, even when the option to use template values is checked.
This is existing functionality in the Polaris toolbar client, and should be in Leap as well. (See attached…
27 votes -
Make phone number searching better
This request is for a new feature to improve phone number search capabilities, specifically by handling varied formatting in the free-text phone number field.
The current phone number search often fails because it's a simple text match that can't account for different formats like hyphens, spaces, or parentheses. Staff will sometimes report back to a patron that their phone number isn't in the system because they didn't search for it in the way it was entered into the patron's record. This can then frustrate patrons if they continued to get called or texted by the notification system.
Implementing a search…
27 votes -
Comprehensive Audit Trail for System Administration Changes
Implement a detailed and accessible audit log for all configuration changes made within the Polaris ILS System Administration (SA) and "adjacent" modules.
Description of the Problem
The Polaris ILS lacks a granular, searchable audit trail for System Administration changes. This makes it difficult to determine who made a specific change, when it occurred, and what the previous setting was. This ambiguity hinders troubleshooting when a configuration error occurs, complicates training, and reduces accountability.
Proposed Solution
A comprehensive, transaction-based audit log that automatically records the following data for every saved change in the SA module:
Timestamp: The precise date and time…
30 votes -
Automatically change items stuck in transit to missing
Some items get stuck in transit and are never found again, it would be nice if these could automatically transition to missing after a customizable period of time, similar to Lost -> Withdrawn and Missing -> Withdrawn.
85 votes -
Adding Shelf Check Requests to the Picklist
In our system of 33 branch locations, we often receive system-wide email requests to complete checks of the stacks for items customers claim to have returned but that are still on their accounts.
It would be helpful if Item Records had an additional "Action" option that allowed staff to select "Request Shelf Check". The item would then populate on every branch's picklist with a unique icon next to it, and there would be a checkbox at the top of the list, similar to "INN-Reach Only", that would allow staff to narrow the list to what was shelf check requested by…
30 votes -
Verify patron email address and phone number
Incorrect email addresses and phone numbers in patron records cause hold and overdue notices to fail. This results in a negative patron experience and requires wasted staff time for troubleshooting and manual data correction. Polaris should behave like other systems and verify contact information before using it.
When an email address is entered into a record, the system will send a message with a verification link. After the patron clicks the link, the email's status in the ILS will change from "Unverified" to "Verified". A visual indicator will show the verified status to both staff and patrons.
This function will…
24 votes -
Comparing authority records in Leap
Similar to the compare feature for bibliographic records, please implement a compare feature for authority records. This would be helpful when editing authority records in Leap.
44 votes -
Allow for alphabetizing checkout screen in Leap
Please allow the checkout screen in Leap to be sorted/alphabetized by clicking any of the header columns, Title in particular. This is currently something that can be done in the Polaris client, and is useful for library staff when checking out large amounts of books to patrons who would like an alphabetized list of what they've just checked out. The columns in Leap appear to be clickable for sorting, but they currently are not.
19 votes -
Compare bibs with an outside source - Leap
We would like the ability to compare bibliographic records in Leap with ones from an outside source, like z39.50. This is a key part of our cataloguing process and is a necessary piece to moving those staff members over to Leap.
40 votes -
Remove Notification Options for Staff
Our Library will soon no longer be offering phone notification. I'd like the ability added to remove notification types (Phone 1,Phone 2 etc) from the staff interface so a invalid choice is not longer available. However, we'd still like the ability to record that information in the patron registration if needed.
56 votes -
Add an option to mark record sets as "do not delete."
Polaris has long supported an option in Patron Registration where you can mark a patron record as "Do Not Delete." I'd like to see that same functionality carried over to record sets. For me, it's a fairly common task to recover accidentally deleted record sets for staff members who've somehow managed to delete an important and often used record set, despite every warning they receive.
Specifically, I'd like to see this option added at the permissions level, with separate permissions for:
- Mark a record set as "do not delete"
- Clear a record set for deletion
That way staff members can't…
28 votes -
Adding a bulk change option for item records linked to a PO
In the toolbar version of Polaris, it is easy to make bulk changes to item records from the PO, which we occasionally need to do to change things like shelf locations, call number prefixes, and notes that can’t be added via the item record templates. In Leap, there’s no bulk change option on the items tab for a purchase order, and there is also no way to select the item records to add to a record set to be able to do a bulk change that way, meaning any edits to the item records needs to be done one by…
16 votes -
Polaris 8.1 - Leap Find Tool Window Expansion
It would be nice if the Leap Find Tool window could be enlarged to full screen.
39 votes -
Automatic deletion of item records
Just as Polaris offers a workflow for the automatic deletion of patron records, introducing a similar feature for item records would be a highly valuable enhancement. The ability to automatically remove items based on defined criteria would streamline operations significantly. Currently, the manual process—such as creating a Record Set and performing bulk deletions—is repetitive and time-consuming. Automating this task would not only improve efficiency but also reduce the administrative burden on staff.
17 votes -
patron account edit history
I would like there to be a way to see who has interacted with a patron account, in the same way there is a history on an item record. Today we were trying to see who had made a specific change to a patron account, but because someone else had fixed it already, we couldn't. So, if we had a list like the item history, where we could see who had been in and what had been done, we could more easily know who to contact and train on an issue.
48 votes
- Don't see your idea?