676 results found
-
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 -
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 -
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 -
Include perioidical issue information in overdue notices
We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?
14 votes -
44 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!
52 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.
41 votes -
Create a Back End Updating Feature
A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.
So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the…
16 votes -
Update Language Field in Item Bulk Change
The Language field was added to Polaris in 7.4 (I believe). The only way to update the Language field is to manually update each item record manually. As you can imagine, that is very time-consuming. It would be ideal if our Collection Management department could pull the appropriate item records into a record set and then do a batch update of the Language field.
11 votes -
More chances for automatic renewals
Right now, automatic renewals happen 3 days before the due date. If the item someone has out is supposed to fill a hold for someone else then it never automatically renews even if another item ends up filling that hold. There should be a schedule for automatic renewals to occur 3 days, 2 days, 1 day, before the item is due and the day the item is due so there are multiple opportunities for that item to automatically renew in the event that a hold gets filled by another library and that item is now eligible for renewal again. It's…
30 votes -
Add support for automated clearing of the [PolarisTransactions].[Polaris].[NotificationLog]
The PolarisTransactions].[Polaris].[NotificationLog] has Personally Identifiable Information (PII) in it. That table is never cleared, even if you select to clear the PatronID from the PolarisTransactions.
Ideally, we'd like an option for this data to just be cleared out after a certain period of time. If that is not possible, then NULLing the patron id when that option is enabled for the PolarisTransactions should work here too.
5 votes -
Increased reporting ability in SimplyReports
Details on items going in-transit, enroute, and/or transferred are not kept within the Polaris Transactions database. Instead, the data is only kept within the Polaris database. This means if an item is deleted, then statistics on it going in-transit/transferred/enroute are lost. The enhancement request here would be to include that information into the Polaris Transactions database.
This could also serve as a generic enhancement request for increased reporting abilities within Simply Reports. It seems there are a lot of things our libraries would like reports on that are not possible to create within Simply Reports. It almost always involves historical…
23 votes
- Don't see your idea?