Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

538 results found

  1. When you are adding an account or changing information on an account and the system detects a duplicate, it won't let you proceed. However, it won't give you any information on the conflict account.

    It would be super helpful to have the conflicting ID shown in the popup message to make tracking down the other account easier.

    Especially if the dup happens to be because of something weird like a space or non-printable character.

    This seems to happen more as locations move to SSO and fill in their external ID field.

    2 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. We've begun leveraging the "ExternalID" field in Polaris to integrate staff authentication with Google using our Google Workspace email addresses. During this process, we've encountered matching errors when updating existing Polaris accounts that share email addresses with previously deleted user accounts.

    It would be extremely helpful if, when a Polaris staff account is deleted, the associated ExternalID is automatically cleared to prevent these conflicts. Additionally, when an error does occur due to a duplicate ExternalID, a clearer error dialog that identifies the conflicting PolarisUserID would greatly assist in resolving the issue quickly.

    1 vote

    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)
  3. Polaris client allows staff to populate a patron record set from an xlsx or csv on the local machine. Please enable this capability for item and bib record sets as well.

    1 vote

    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. Currently, when we need to edit a serial's status, it has to be done one at a time. We have multiple branches that all are scheduled to receive the same issue of a magazine. When the expected issue isn't published, due to a double or special issue instead, we have to edit each serial's status individually to "Never published". Adding serial specific fields where appropriate to bulk item edit would help this.

    2 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. Cataloging staff using the client have to resize the columns of the find tool results every time they search bibs and items. They also would like to be able to add and remove columns from their default searches. In LEAP, they can add and remove columns and LEAP remembers when they resize a column. This functionality in the client would save them steps.

    1 vote

    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. Currently Item Ad Hoc Bulk Change is only available on mouse right-click. Please add a toolbar button and/or a keystroke shortcut.

    1 vote

    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. Allow SSO logins for SimplyReports. Right now, staff who are SSO accounts only cannot log into SimplyReports. Leap and /PolarisAdmin support SSO and we'd like to be able to extend this to SimplyReports.

    This prevents us from being able to fully adopt SSO at some locations because the staff can't create reports. This means we have to continue to hold onto and maintain less secure connections between networks, so these staff can run SimplyReports.

    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)
  8. 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.

    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)
  9. 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.

    1 vote

    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. Reset Claim Count is currently all or nothing. We need the ability to reduce the claim count incrementally. This would help in situations where we actually find a bona fide claim return on our shelf for a customer who otherwise has a pattern of making false claims. We want to be able to clear that incident from the claim count without having to reset to zero.

    2 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. It would be helpful if Polaris could integrate with Skyward and TeacherEase Student Integration Systems. We currently provide service for a number of K-12 schools and it would be helpful if fines/fees could be transferred to the primary system a school uses.

    1 vote

    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. Current Situation:
    We currently have an unwieldy number of Patron Codes, which we aim to streamline by shifting toward greater use of Patron Statistical Classes. This is possible because many of our existing Patron Codes have minimal or no functional differences. However, Patron Statistical Classes are not currently displayed within Leap’s Patron Info (‘I’ button) panel, requiring extra steps for staff who frequently need quick access to this detail regardless of which patron registration view they are currently in.

    Suggested Enhancement:
    Add the Patron Statistical Code directly below the Patron Code within the Leap patron information (‘I’) panel. This would…

    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)
  13. You cannot output or filter on Hold Pickup Areas in SimplyReports. Not being able to report on them limits their usefulness for things like looking at which schools are busiest or which bookmobile stops are most active. The information is available in hold request data and in transaction details.

    Although we can add it as a custom output that will only show the ID which is of limited value to staff.

    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)
  14. The Leap quick search could do a better job of searching Hispanic names. Often, patrons consider their first two names as given names, not as first and middle, which makes it difficult to search for them when they come in without their cards. For example, if I search for Luis Miguel Paco Sanchez using all four names, LEAP finds the patron. If I search for Luis Paco Sanchez or Luis + either last name individually, LEAP will not find the patron. If I search for Miguel Paco Sanchez, LEAP finds the patron. In this example, Luis Miguel is the first…

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

    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)
  16. There are lots of things that can go wrong with holds fulfillment. From things remaining too long in the RTF, to holds that were item specific, and now the item record has been deleted, holds on bibs where all items are restricted from filling bibs, holds where the item has been shipped months ago, holds where the volume-level hold information is incorrect.

    While there are reports that some libraries run for this, those are not "front and center" in most workflows for ALL libraries to be aware of them and be taking action to handle them.

    About the best solution…

    2 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)
  17. We have dozens of SQL searches, however it can be hard to find them. They are presented in an alphabetical list, but over the years our naming isn't always consistent. It would be great if you could filter the name drop-down like you filter can in other areas of Leap.

    So, for example, if I typed "volume" it would show many any SQL search with Volume in the name. Bonus points might be if we could also be searching some of the SQL search contents itself because maybe I want to find all SQL searches that query a particular field…

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

    1 vote

    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. You should be able to search in the Find Tool by record modification date. So far I'm seeing this missing from Record Sets, Patron Accounts, etc.. This would make it easier to Find Records without having to resort to using SQL which makes it much more accessible to all staff.

    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)
  20. The ability to link a supplier to use a specific fund so that the header charge gets applied to that fund instead of having to select one generic fund for all header charges.

    2 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)
← Previous 1 3 4 5 26 27
  • Don't see your idea?