681 results found
-
Ability to Suppress Custom Data Fields
In Polaris System Administration, there is existing functionality to suppress UDF 1–5 in the Web App (Leap), which allow the fields to be written to, but prevents staff from viewing or editing them.
We would like to request that the same suppression functionality be extended to Patron Custom Data Fields. Currently, the only available option is to enable these fields, which simply turns them on or off. This lacks the flexibility we need.Adding suppression capability to Patron Custom Data Fields would greatly enhance our ability to manage sensitive or system-used data more effectively.
2 votes -
Add eReceipts as an option in LX Starter.
The only option for eReceipts is plain text. It would be a fantastic feature to customers to be able to build a nice HTML email for them.
14 votes -
Standard Address Number (SAN) Inconsistency
There is no hyphen in Branch SAN but Supplier SAN has a hyphen. This causes confusion for both the library and suppliers while setting up EDI for the very first time for new Polaris customers. It would be better if there was a consistency.
6 votes -
bulk change due dates
Allow libraries to bulk change due dates of items to account for unexpected closures. Would be ideal to be able to do this from a records set. Or create a SQL job and put it in GitHub or some other accessible location for libraries.
16 votes -
Add Items to a Record set from Patron's Hold List
Cataloging staff use staff cards to request items in for call number changes or various projects. It would be helpful for them to be able to add those items into a Record Set for bulk changes directly from the patron record Hold list, in lieu of individually from the item records.
14 votes -
Edit Half-Deleted Item Records
When doing clean up work we run into instances where we are not able to delete something like shelf locations because it is assigned to records that are in a deleted state. While we know we can just delete the records 1 more time, some of these records are tied to other things we track and would prefer to keep them in the system.
Currently we bulk change them at the server level but would like a way to be able to do this within the ILS.
13 votes -
Add a permission to allow/prevent staff member override a hold and check out a Held item to a different patrony
Currently, Polaris allows all staff members to override a hold and check out a Held item to a different patron. We need a System Administrator (SA) permission to control this functionality. Our preference is to prevent staff from overriding holds, ensuring items are always checked out to the requesting patron.
4 votes -
Provide alert when staffer selects a location different from that a workstation is associated with when logging into Leap.
Despite constant reminders, we have issues with substitute staff who cover at various locations logging in under the wrong branch. It would be great if Leap could have a pop up box, requiring confirmation to proceed, that alerts the staffer if the workstation they are logging in on is associated with a location other than the login branch.
5 votes -
Ability to block holds by resource group or vendor account
Library staff frequently place holds that can’t be filled on the records for e-books from non-integrated vendors like Hoopla. Canceling these holds takes time. Since we still need to allow holds for the integrated vendors, we can’t change the material type to unholdable in system administration. Adding the ability to block holds by resource group or vendor account would solve the problem.
29 votes -
Combine current and recent workform tracker into one and use indicators
Separating the Current & Recent workform trackers means you sometimes have to check both to regain access to a record quickly. There really is no need to separate them.
Modern systems indicate active records using a "dot" (think Mac OS, Windows 11, etc.). Combining the workform tracker into a single list would make access workforms in Leap faster.
PS I do acknowledge that some people would have a problem with a growing list of workforms showing. So an option to clear all inactive workforms would probably needed to be added in addition to the close all active workforms option.
6 votes -
Bookmobile address locations for hold pickup
Bookmobiles move around. When customers get the holds notice, the address listed on the notice is usually the bookmobile home address. The customer shows up only to find that the bookmobile isn't home. We have pickup locations for the customer to choose from in the PAC, but they do not have addresses assigned to them. If they did, we would want that address to be used on the holds notice. Can this be a LX starter and/or Polaris enhancement for Bookmobile.
8 votes -
Hide libraries and branches in Polaris System Administration
Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.
Just sitting there and doing nothing.
I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.
So add the ability to hide them instead.
That way, when a library leaves the system, you're not wading through the settings and…
28 votes -
free text block
There should be a free text block that only people from the owning branch for that item can edit. This would allow staff from the owning library to make notes about pieces in an item or damage to an item without risking staff from other branches/libraries deleting the note from the home branch.
6 votes -
Support Dark Mode for Leap
Dark mode is preferred by many users due to lower brightness and less eye strain, as well as less screen glare. Support Dark Mode for Leap!
55 votes -
Express Check: Enable Barcode Scanning from Username Field
We use both the barcode field and username field interchangeably for patron access at our express checkout units. Currently, the unit only recognizes barcodes when they are scanned from the barcode field. We need the system to also recognize and process barcodes stored in the username field when scanned.
For example, our school students have their student IDs stored as their primary barcode in Polaris, with their former library barcodes stored in the username field. When students attempt to use their RHPL cards, the barcode currently only works if they manually type it in. We would like these cards to…3 votes -
Hoopla integration with Polaris
The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.
15 votes -
Create Multiple Items in LEAP
In the client we are able to create multiple new item records at the same time and we would like this functionality in LEAP as well.
43 votes -
Add an Invoice Status of 'Ready to pay'
Add an Invoice Status of 'Ready to pay' or 'All items received' in the Find Tool - Invoice - search filter. This will allow EDI invoices to be filtered to ones where all items have been 'received' and make the invoices ready to 'pay' easier to find
5 votes -
Entering new accounts
When entering new accounts in to LEAP, we enter the patron zip code and the city is automatically filled out. At Phoenix libraries, if the city is not Phoenix, we have to remember to change the patron code to Maricopa and the expiration date to only one year. Could these 2 fields also be automatically filled out by the zip code information. It would save a lot of jumping from the top of the registration form to the bottom and back...and could save mistakes when we have a LOT of outreach library card forms to enter.
11 votes -
Force Leap Logout at Browser Close
Leap should force logout when browser/browser tab is closed. Forcing a logout at browser/browser tab close would ensure that any open editable records are closed out as well.
54 votes
- Don't see your idea?