Skip to content
Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

35 results found

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

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

    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. Expand NotificationStatusID list/table to include TXT Sent and TXT Failed, plus any additional like TXT Failed - bad phone number

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

    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. Allow permissions to modify the branch floating table so that each branch can maintain their own float in counts for their collections and/or media types.

    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)
  6. I realize this is niche, but if you go to set up SSO in your environment, heaven help you. My crew just got through a week of getting things set up. There were 3 of my employees and at least 1 Innovative support staff and 1 Innovative dev involved all week. I can't imagine the amount of $$$ that was burned in hourly staff time getting it going. And of course the good news is that an upgrade or server move could break it all again! Some of the documentation is wrong and some of the transcribing of the data…

    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)
  7. Sometimes I have a lot of records open in the workform tracker, and it's a pain to have to go into each to close it. It would be useful to have a button I could quickly click to close them instead.

    In cases where a record has been modified it should generate a prompt about saving changes, and show you the record again in this case so it's clear what's being saved.

    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)
  8. It would be helpful if we could move rows up and down in the item statistical class code policy table. We have librarians transferring items between branches that have statistical class codes in them. The codes will automatically change to a different code when assigned to the new branch because the position of the code in the policy table does not align. The cataloger must remember to update that field to the correct code.

    This would be beneficial to our librarians, simplify their workflow, and prevent errors.

    10 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 would like to see additional information and functions available in the Polaris Client or LEAP so that staff have more resources and information to support customers with questions about online resources.

    For example, library staff would benefit from seeing real-time hold information in Polaris about items on Overdrive or Hoopla. Currently, Polaris shows an asterix (*) under holds. Library staff need to either go to the PAC or Overdrive to provide customers with this information. It would help library staff to have information available in one place rather than requiring staff to go to multiple sources to answer a…

    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)
  10. When staff log out of Leap at the end of their shift, Microsoft prompts them to sign out of their Microsoft account. I think it confuses staff, they click on the prompt and then they get logged out of their Microsoft account. They then have to log back in and due to MFA need to get a code to log back in. This isn't ideal.
    Customer support said currently this behavior is how Leap with OAuth/SSO works. Leap uses the identity provider to control the login and logout when setup with OAuth/SSO. Can you place an enhancement request to see…

    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)
  11. We would like to be able to copy an existing branch when creating a new branch, since often our additions are branch locations of an existing library that will have almost the same exact settings.

    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)
  12. Reviewing the process of integrating Cirriusimpact at our library, we've encountered a notable issue: patrons opting out of text messaging and staff needing to adjust their notifications accordingly. Currently, we're relying on CGS to send daily email alerts when someone opts out, but it would be more convenient to add a non-blocking note to the Polaris account visible to all staff. This would ensure everyone is aware of a patron's preference change and simplify the search for patrons with similar notification settings.

    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. The Polaris Transactions database TransactionID is an int data type. This 2,147,483,647 means the biggest number supported by the database. In our busy system, we're about halfway through the available TransactionIDs as we're about to reach 1 billion. This field should be moved up to a bigint data type. Otherwise inserting new data will fail.

    10 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. It would be nice to have the ability to set different email notice schedules for each branch.
    We would like to line up our notice delivery times with the operating hours of our branches, or allow more frequent hold notice emails at a specific branch.

    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)
  15. In addition to Single Sign-On (SSO) support for Microsoft Azure and ADFS, please consider support for Google Workspace. We recently migrated all of our email for our consortium (42 members) to Google and would greatly benefit from the ability to use the already signed-in information to authenticate into Leap. See screenshots for a design/concept mock-up.

    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)
  16. We have a Bookmobile service that is setup as it's own branch as well as a holds pickup location. With the limited capacity of this "pickup location", we are trying to restrict the material type loan limit block by location instead of by branch association.

    It would help to have some sort of Policy Table that does Material Type Loan Limit by Branch Pickup Location.

    Idea Value
    This would filter out items that cannot be picked up on the Bookmobile Branch to stop patrons from placing the hold and avoiding staff to have to manually cancel the hold and follow…

    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)
  17. Allow multiple selections of Organizations & Patron Codes to populate Material Type list (lower table) on the Patron / Material Type Loan Limit Blocks, Policy Table.

    16 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. We're working with a vendor to import patron records into Polaris as part of a program to give every student of the local school district a library card. As part of the arrangement, these student cards will be exempt from billing.

    Unfortunately, there is no means to check the "exclude from" overdues, billing, etc. boxes in the API, so this will have to be done manually every time a new batch of students is imported. Please make it possible to modify these options via API.

    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)
  19. Currently, when staff update their library's Dates Closed table for a single date in the future they are required to select/enter the same date in both the Dates Closed and the Until fields.

    While it is just a couple additional clicks, having the Until field auto-populate with the same date that staff have selected/entered in the Date Closed field would improve the end user experience when they are entering a number of single dates at once.

    6 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. Currently we have to send patrons from our websites to the PAC if they need to reset their passwords. It would be great if there was an API call for this, as it's disruptive to the patron experience to have to send them to another site.

    The suggested functionality would reflect the PAC experience: once they enter a barcode, a password reset email would be sent to the email address on the account.

    15 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
  • Don't see your idea?