603 results found
-
Ability to have a different 'Number days held for pickup' based on Material Type
Our member libraries would like to have their admission passes (Material Type 'Pass') configured for a 3 or 4 business day pickup window, whereas all other material types are configured for 10 days. (10 days is too long to hold admission passes for pickup, but makes sense for everything else.) I could see where this might be beneficial for other material types also.
16 votes -
Standard Identifier Number search option in Leap
In the client, you can do a bibliographic search by "standard identifier number" and it searches a bunch of different possible fields (the corresponding power search: (((ISBN="1234" OR ISSN="1234") OR (OSI="1234" OR STRN="1234")) OR (((PN="1234" OR CODEN="1234") OR OCN="1234") OR (SOA="1234" OR UPC="1234*")))). We would also like to see this option in Leap.
Currently, staff don't get results for a scanned barcode unless they choose the correct field to search and the indicators in the record are properly set. This means they often get no results and incorrectly assume we don't have…
19 votes -
Merge patron function write note to Dated Notes
When merging patron records, the system currently appends merge details to the Non-Blocking Notes section. However, with the introduction of Dated Notes and the ability to hide Non-Blocking Notes, this information can be lost depending on system settings.
We would like to see one of the following options implemented:Allow administrators to choose where the system writes merge notes.
Have the system automatically write merge notes to both note types (Non-Blocking and Dated Notes).
12 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.
25 votes -
Consistent Collection Name Display in Cataloging and Acquisitions Modules
We would like to submit an enhancement request regarding the display of collection names in the system.
Currently, the Cataloging module displays the collection name together with its abbreviation, while the Acquisitions module only shows the first part of the collection name in the dropdown list. This difference in display may cause confusion for staff when selecting or identifying the correct collection.
We would like to propose an enhancement so that the collection name display is consistent across both modules, ideally showing the full collection name together with its abbreviation, similar to the display in the Cataloging module.
This improvement…
10 votes -
Add newer LEAP Pagination to MARC Import Background Processing Screen
The Background Processing screen (specifically under MARC Import) does not currently support the newer LEAP pagination options available in other, more recent LEAP screens. This creates usability challenges when reviewing and managing historical imports.
Problem:
The current interface relies on a “More” button to load additional records page by page rather than having the option to load all and setting the record count to view. This creates several issues:
• Staff must repeatedly click “More” to access older records, which is inefficient and time-consuming
• There is no option to “load all” or quickly navigate to a specific point in…9 votes -
Polaris should re-evaluate hold eligibility when trapping preferences are set
When a hold request is placed, Polaris performs an eligibility evaluation only once—at the moment when the request is first placed. Polaris does not re-evaluate eligibility later. So if Polaris is configured to use hold trapping preferences that prefers "my patron" but some temporary circumstance prevents the assigned library's item from filling a hold for the library's patron, the hold must now be filled by a different library. This can be mitigated if staff notice the problem and delete and replace the hold, but this is a lot of extra overhead and in all likelihood the problem will go unnoticed.…
12 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…
31 votes -
Registration confirmation email as part of patron self-registration
My library would like an email to be sent to patrons who use the self-registration form in the PAC with a confirmation that the registration has gone through and with reminder information that they will need to come in to complete their full registration. This would also allow us to confirm that we have a correct contact for the patron.
8 votes -
Export authority records from Leap
As of 8.0, users can export MARC bibliographic data, but not MARC authority data. Can this utility be updated to also allow export of authority data? This would help catalogers during cleanup and maintenance projects, and it would make Leap functionality align with the desktop client.
Example of a case where this function would be useful: Vendors like Backstage may ask for a sample of existing authority records. Being able to use Leap to export MARC authority files would help libraries with limited or no desktop client access.8 votes -
Add support for direct print (QZ tray) to leap offline
Add support for Leap direct print using QZ tray to Leap offline. That way libraries don't have to figure out something special when they are in offline mode which is already a stressful time period for them.
13 votes -
Include DELETE method for Patron Blocks
As of Polaris 8.0, PAPI supports creating new Patron Blocks but does not provide a method to delete them. For internal automation and vendor workflows, the ability to programmatically remove Patron Blocks is essential. Adding a delete method will reduce the need for manual intervention.
9 votes -
Blocking Conditions for Item Barcodes
The ability to block item barcodes that begin with specific digits, such as 978, would be a tremendous benefit for libraries. During item record creation, staff may accidentally scan the ISBN or UPC printed on the item instead of the library-assigned barcode intended for circulation use.
Providing the ability to restrict or block specific barcode patterns would help prevent incorrect barcodes from being saved to item records. For example, preventing an item record from being saved when the barcode begins with 978, the standard prefix for traditional ISBNs, would significantly reduce these types of errors and improve data accuracy.
5 votes -
Leap - Give the option to overlay a record while comparing multiple MARC records
When comparing bib records in Leap, it would be nice to be able to choose the bib to keep and overlay the other with. This would streamline deduplicating similar records.
29 votes -
Force the use of templates
AS a consortia that includes many small 1-2 person libraries, we would like the option added to force member libraries to use templates. No matter how much we encourage, train, and setup their templates, they are not being used consistently across all members. This is causing export issues when sharing our catalog statewide for ILL and will now being causing issues when we are a ztarget for the state ILL system. We can bulk change all these items, but that is wasted staff time, when it would just be easier to force those 1-2 person libraries to use the templates…
6 votes -
Conditional Required State for Fields on Registration
We would like to be able to control whether or not a given field is required on registration based on the patron code selected. For example, we have a "No Permanent Address" patron code where ideally, address would not be required when that is selected. Or, we use one of our User Defined Fields for Parent/Guardian Information, which we would love to make required when a patron code indicating a minor is selected.
6 votes -
Grouped Bibs
Since moving to Vega Discover, we are finding that we are having some issues there with holds queues due to the rolled up records (I've posted an idea over there too), but it's also exacerbated by the way records show in Leap.
Ultimately, it would be great if bibs rolled up in Leap in a similar way to Discover. Not the different formats per say, but if there is a softcover, hardcover, deluxe, and reissue of a book, it would be nice to be able to see those all together to determine circ stats for them in a combined view,…
13 votesI want to note that we may need to split this into several smaller requests, but we can keep this open until we have a better sense of how to best to break it down.
The BIBFRAME-based model in Vega natively handles some of this grouping. It's not really feasible for us to create BIBFRAME-based groups in Polaris right now, but some of the problems mentioned here we might be able to solve. For example, Vega Reports might offer us an opportunity to provide grouped bib stats by combining stats for MARC bibs based on Vega roll-ups.
-
Navigation buttons at the top and bottom of All Items list on LEAP bibliographic records
On the All Items tab of LEAP bib records, it would be helpful to have page turning buttons at both the top and bottom of the list for ease of navigation
18 votes -
Add 'Patron Record is Secured' to Report Output Column in Patron List Reports
Add 'Patron Record is Secured' to Report Output Column in Patron List Reports in Simply Reports. Available as a Patron Miscellaneous Filter but not as an output.
11 votesSecured patrons are patrons with a record status = 3. It is possible through SimplyReports content administration to add the RecordStatusID column from the Patrons table to the list of output columns.
I'm putting this idea under review because the RecordStatusID isn't exactly what was requested here. But I wanted to share that it may provide a workaround.
-
Update SIP to handle foreign characters (diacritics)
SIP should handle foreign characters (diacritics) correctly. When a patron's name or an item's title has a diacritic then it throws an error. For some vendors, it breaks the application and prevents customers from logging in and/or accessing their checked out or held items.
14 votes
- Don't see your idea?