577 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…
44 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…21 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…
45 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.
75 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…
25 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.
41 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.
52 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…
23 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.
33 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…
16 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…
17 votes -
Easily print multiple of the same spine lable in Leap
When printing spine labels from an item record in the client, you can choose to print multiple of that same label. I would like to have that functionality in Leap. This will be helpful when processing multiple of the same item without having to send the label request for each individual item.
32 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…
20 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.
39 votes -
Return to where you were in your record set list after closing an item record from the record set
When I am working in a long record set and open an item record and then close it again, it returns me to the top of the record set. I would really like it to return me to where I was in the list to more easily continue my work.
41 votes -
Service Name Logging in PatronValidate API
This proposal outlines an extension to the Patron Validation API to include an optional serviceName parameter. When provided, this value will be recorded in the Integrated Library System (ILS) transaction log, allowing us to track which service initiates each patron validation request.
Currently, the ILS transaction log records patron validations without capturing which service initiated the request. This lack of context makes it difficult to analyze traffic from third-party services (e.g., OverDrive, Hoopla) or internal applications, troubleshoot validation spikes, and make informed decisions about service contracts and resource allocation.
The proposed solution is to modify the Patron Validation API to…
12 votes -
Send record sets to Label Manager in Leap
The desktop client has the ability to send a record set to Label Manager; Leap does not. Without this feature, mass relabelling projects such as adding a new section are an enormous drain on staff time.
29 votes -
Recall function
Create a recall function that is separate from the holds queue so Technical Services can get items back (for relabeling, for weeding, etc.). Technical Services often use internal cards to place holds on a specific barcode. This sometimes work, but has a few drawbacks:
1. The hold disrupts circulation (renewals, other holds, potentially in-transit)
2. If the item goes into a status that cannot fulfill holds (e.g. item becomes LOST), the holds will go back the queue and be reassigned to another item on the bib. Technical Services usually needs the specific barcode, not just any item on the bib.…
45 votes -
Trim Whitespace on Username and External ID Fields in /PolarisAdmin (Web Admin)
We would like to enhance /PolarisAdmin (Web Admin) so that leading and trailing spaces are automatically trimmed from the Username and External ID fields upon entry.
Problem Statement
Currently, if administrators accidentally enter a username or external ID with a leading or trailing space, it is saved as entered. This creates login and authentication issues for end users, since the system considers the space a part of the credential. This can be difficult to troubleshoot and frustrating for both administrators and end users.This is especially likely to happen when copying/pasting from certain user management platforms.
Proposed Enhancement
Automatically strip…12 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…
53 votes
- Don't see your idea?