342 results found
-
Include patron preferences such as billing notifications in PAPI patron update/create
The Jacksonville Public Library leverages the Polaris API to manage student records. Currently we have to take an extra step in the LEAP UI to set the communication preferences. We don't bill students or send their accounts to collections, so we have to do a bulk update of all the records with the UI after already touching every record with the API. This is cumbersome because there are over 100,000 student records that need to be updated. Most updates are smaller, but at the start of the school year we do a full refresh.
We would like to be able…
2 votes -
Improve Hold Duplicate Detection
Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.
This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like…
2 votes -
Additional UI Customization Options
Across our consortium, we have some library staff who exclusively use Leap, some who exclusively use the Remote Client, and some who use both depending on the task.
Currently, there is only one system-level setting responsible for the Visual Alert Configuration (top banner color) in Leap & the Remote Client. Unfortunately, this doesn’t work well given that Leap has a light font color and the Client has a dark font color across the top, so to achieve an ideal level of contrast for both versions simultaneously is impossible.
To improve accessibility for all users, regardless of the version of Polaris…
10 votes -
Transitioning Claim Returned and Claim Never Had
We would like Polaris to transition items with a Circulation Status of Claim Returned and Claim Never Had to Withdrawn after a specified number of days. We envision this working like Lost Item Transition and the Missing Item Transition.
Idea Value
Adding this feature would allow a library to automatically remove items from patron view and allow for a more streamline process for deleting item records.37 votes -
Add Library Level to Hold Pickup Limit
Currently, a library may limit an item to be holdable for pickup at a single branch location. This setting allows the item to be limited to pick up at the item's assigned branch only. While this feature may work for single-branch libraries, it does not function in a practical way for multi-branch libraries. Expanding this feature to have a library-level option would increase the usability of this setting.
Example 1: Library A has 3 branches. They want to make their mobile hotspots holdable for pickup at any of their 3 branches. They do not want their hotspots to be placed…
33 votes -
Ability to remove spaces from call numbers in Leap
When the callnumber column is pulled from itemrecorddetails via SQL (as opposed to SimplyReports) it includes trailing and leading spaces. It's easy to fix these unwanted spaces in the client, but they don't show up at all in Leap, so can't be fixed. If Leap is to replace the client eventually, it would be great to able to fully edit these fields in Leap (we are hosted, so can't easily modify the data via SQL).
3 votes -
Create Bibliographic Record Sets from Weeding Record Sets
Working with the weeding-type record set workflow in an attempt to streamline, we have found the absence of an option to create a Bib record set from the available actions takes us a rhetorical two steps back from before (when we weeded via item record sets). Once the items have been withdrawn, we now have to go through each withdrawn item's record to their respective bibs, to uncheck "Display in PAC". It would be nice to add a "Display in PAC" uncheck in the Weeding template creation - however, it would need an added function to alert staff of bibs…
1 vote -
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…
11 votes -
Adding a "New" field in LEAP
Because new is both a location and a status, it would be helpful to have an item level field in LEAP that is for "new" items. A simple checkbox would be sufficient, like "holdable" or "display in PAC." This would free up shelf location for any items that are both new and in a specific area, such as Travel, World, Graphic, etc.
9 votes -
Increase visibility of Reading History feature in PAC
A consistent piece of feedback we get from front-line staff is that patrons struggle to find where to turn on Reading History and that they themselves often forget where it is located. Having it buried within "My Record"-->"Contact Information and Preferences" and having to scroll down to it apparently is not effective. Having the "Reading History" tab always visible under the patron's name on the left-hand menu would be more effective, instead of having it only appear once Reading History has already been turned on.
3 votes -
Ability to enter a single date when searching for a patron’s date of birth. Currently, the search for date of birth consists of two search f
Our staff searches for patrons by date of birth to check for duplicate accounts. It would be nice to enter only one date instead of two.
3 votes -
1 vote
-
Polaris integration with Kajeet
More and more libraries circulate mobile wifi hotspots to the public. Polaris and Polaris Leap do not currently integrate with Kajeet, which is one of the more popular wifi hotspot providers for schools and libraries. It would be beneficial to libraries using the Polaris ILS to be able to streamline the circulation process such that checking in/out a hotspot in Polaris also activated/deactivated the hotspot itself.
2 votes -
Fund Hierarchy Report
Currently, the fund hierarchy report organizes at the Organization level by Org ID. This means that as new organization levels are added they drop to the bottom of the list, and I'm often looking at this from an alphabetical perspective. It would be helpful to have the option to organize the output alphabetically instead.
3 votes -
Make SimplyReports reports truly use the library level for reports
When you use SimplyReports (née Simply Reports) and create a report and select a LIBRARY, the report data is actually using the branches at the time the report was created. It is essentially a branch level report with the branches a the time of report creation.
This means that if you save the report, then you add a branch, that branch is NOT included in the report output. This causes confusion and extra work. There should be an option to truly make a "LIBRARY" level report, or part of the process of adding a new branch should go back and…
13 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.
28 votes -
Add a copy button to supplier records in Leap
The ability to copy existing records makes record creation more efficient. In the Client, staff have the ability to copy an existing supplier record to create another one with similar information. This happens when staff have multiple supplier records for the same vendor because they have separate account numbers. A copy button is not in the supplier record workform in Leap yet. It should be added to the actions drop-down menu of the supplier record like it is in other record types. This will allow staff to feel like the transition to Leap will be easier since it is a…
25 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.
36 votes -
Include All Patron Duplicate Detection Settings in the API
Currently the API only performs basic duplicate detection (name, birthdate, barcode, username, and optionally the name on ID) when a patron record is created using the PatronRegistrationCreate call. It does not apply other optional settings - email, phone 1, or the UDFs - these only get applied directly in Polaris or the PAC. This idea is for including these optional settings in the API logic.
11 votes -
Leap patron search options expanded
Expand upon Leap Patron search by 'Notification Option', and 'Wireless Carrier'.
4 votes
- Don't see your idea?