Skip to content
Innovative Idea Exchange

ILS - Polaris

Recently Activity

ILS - Polaris Updated

Last In House Use column

Reporting & Analytics UNDER REVIEW

ILS - Polaris Updated

Automatic processing for item record details

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Patron block pop up

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Holds that can't be filled

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Volume-Level Holds for Blank Volume Field

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Live Preview Within Bibliographic Record Sets

Cataloging & Metadata Management UNDER REVIEW

ILS - Polaris Updated

Vendor integration

Customer Relationship & Account Management UNDER REVIEW

Don't see your product?

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

695 results found

  1. 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…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. In Leap, when you edit the 008 field by typing in the field directly, instead of opening the editing box, the position of the subfields is corrupted. The ability to edit the 008 field directly works correctly in the Client, and is an important, time-saving feature. Common edits include adding an 'a' for illustrations in position 18 or adding a second date in positions 11-14.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Clarification on the enhancement: the 008 field is currently editable without expanding and using the drop downs.

    The enhancement is to no longer require you to remove the character that is in the 008 field to replace it.

    For example: if you have a blank space in position 23 the enhancement would allow you to type "b" without having to highlight the space to replace it, or delete the space after typing your desired value.

  3. 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.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. With the new option to update patron codes based on age criteria (which we're excited about!), it would be useful to be able to send notices to patrons whose account type was auto-updated and/or to pull a report we could use for sending out messaging to the impacted patrons in our newsletter platform.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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.

    121 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. By adding received date and user to the POLI segment view, we would be able to quickly troubleshoot issues without needing to run reports.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently, when checking in, if you have the barcode box selected, you can click Enter on the keyboard to RFID scan. But, when you have to print a receipt, even if you click Enter to just choose yes, the focus doesn't go back to the barcode box so you have to mouse back over.

    This is a minor but constant annoyance. In the desktop staff client, F9 was the keyboard shortcut to trigger RFID scans, so it didn't matter what part of the app was in focus.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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…

    43 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We have recently been coming up against an error when adding additional notes to the Non-blocking notes field. There is a current character limit of 4,000 characters that's not noted anywhere I could find on the help section. Can this character limit be updated, as there are many instances where notes need to be kept for historical purposes?

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add an error message to the EDI logs when an invoice fails to load into the Polaris invoice tables due to a duplicate invoice number already existing in Polaris.

    This is becoming a bigger issue as Ingram has changed their invoice number scheme and they are using the same numbers as Midwest has used. There is no way to delete or edit past Midwest invoices, so this is a critical issue for figuring out why invoices aren't loading.

    Current Issue
    - If a duplicate is detected during the Polaris invoice creation step, no error is recorded.
    - This results in…

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. When manually entering POs and POLIs in Leap, I want to be able to do an ISBN search via remote databases to pull in an on-order MARC as I do in the client.

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Make temporary shelf location visible on picklist. Adding this to the picklist will allow staff to quickly locate items that might be on display or some other temporary shelf location.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Holds are currently listed by date with the holds ready for pick up grouped at the bottom. We would like to customize how the holds are sorted with the holds ready for pick up listed on top.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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.

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. To be able to create customized circulation statuses that work for our system versus using the only given statuses. For example, the ability to create various Withdrawn - Leased, Condition, Relevancy. This would then offer additional feedback for staff when stats are ran to determine why materials were withdrawn versus they were.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    For the withdrawn example, does this really require custom circulation statuses? Or just a way to indicate/query the reason an item was withdrawn?


    The reason Polaris has traditional restricted circulation statuses is because of our automated processes around certain statuses. Using the withdrawn example, our automatic Lost/Missing to Withdrawn processing would not know about custom statuses or which one to use.


    If we reworked this enhancement as needing to be able to track/report on withdrawn reasons, we could plan for that within the automated processes.

  17. 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.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. When creating multiple records for a family, our staff often copy the patron record when creating the next. Unfortunately, they sometimes changes some needed fields when copying. It would be great to be able to configure what fields are copied in a patron record. For instance, not copy the birthdate and the first/middle name. From what I can see, this is currently not available. https://documentation.iii.com/leap/8.0/Default.htm#LEAP1_0/Patrons/Copy_an_existing_patron_record.htm

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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.…

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 … 8 10 12 … 34 35
  • Don't see your idea?