Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

612 results found

  1. It would be nice to be able to add captcha (or something similar) as added protection to Self-Registration through the PAC. It would ensure that a human is actually entering the information on the other end rather than a bot. An uptick of suspicious registrations is eating into valuable staff time and we would like to be able to add a layer of protection to our Self-Registration process.

    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)
  2. We’d like the ability to “bulk” cancel holds for items by status (lost, missing, withdrawn, etc.) either by being able to view the circulation status in the patron holds view, or by having the ability to “bulk” cancel holds from a record set.

    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)
  3. When doing clean up work we run into instances where we are not able to delete something like shelf locations because it is assigned to records that are in a deleted state. While we know we can just delete the records 1 more time, some of these records are tied to other things we track and would prefer to keep them in the system.

    Currently we bulk change them at the server level but would like a way to be able to do this within the ILS.

    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)
  4. Currently, Polaris allows all staff members to override a hold and check out a Held item to a different patron. We need a System Administrator (SA) permission to control this functionality. Our preference is to prevent staff from overriding holds, ensuring items are always checked out to the requesting patron.

    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)
  5. The ability to edit patron information—such as custom data fields or core registration details like name and email—without requiring the patron’s PIN or password would be highly beneficial. While using a Record Set to bulk edit standardized fields (e.g., expiration date or User1–User5) is extremely helpful, it doesn't cover all use cases.
    For example, we regularly receive updated information from our partner school, including address changes. Currently, the inability to programmatically update these records creates workflow bottlenecks and limits our efficiency in maintaining accurate patron data.

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

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

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

    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)
  9. Bookmobiles move around. When customers get the holds notice, the address listed on the notice is usually the bookmobile home address. The customer shows up only to find that the bookmobile isn't home. We have pickup locations for the customer to choose from in the PAC, but they do not have addresses assigned to them. If they did, we would want that address to be used on the holds notice. Can this be a LX starter and/or Polaris enhancement for Bookmobile.

    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)
  10. Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.

    Just sitting there and doing nothing.

    I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.

    So add the ability to hide them instead.

    That way, when a library leaves the system, you're not wading through the settings and…

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

    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)
  12. Now that we have the capability to do ad hoc bulk changes to item records from the bibliographic record in Polaris 7.6, we also need the ability to delete item records in bulk. The workflow in the Client includes the ability to select multiple item records ad-hoc, right click on them, and press delete (or undelete). Delete and undelete buttons should be added next to the Bulk Change button on the Local Items and All Items tabs of the bibliographic workform in Leap. An alternate option could be to add a delete option to the bulk change.

    75 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. Cataloging staff use staff cards to request items in for call number changes or various projects. It would be helpful for them to be able to add those items into a Record Set for bulk changes directly from the patron record Hold list, in lieu of individually from the item records.

    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)
  14. We could use a report based on staff user and/or workstation listing all transactions made for a given date range. Most importantly for us, cataloging information which could provide date and time of bib records being created and/or modified as well as circulation information for staff who work the circ desk.

    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)
  15. We use both the barcode field and username field interchangeably for patron access at our express checkout units. Currently, the unit only recognizes barcodes when they are scanned from the barcode field. We need the system to also recognize and process barcodes stored in the username field when scanned.
    For example, our school students have their student IDs stored as their primary barcode in Polaris, with their former library barcodes stored in the username field. When students attempt to use their RHPL cards, the barcode currently only works if they manually type it in. We would like these cards to…

    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. The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.

    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)
  17. When entering new accounts in to LEAP, we enter the patron zip code and the city is automatically filled out. At Phoenix libraries, if the city is not Phoenix, we have to remember to change the patron code to Maricopa and the expiration date to only one year. Could these 2 fields also be automatically filled out by the zip code information. It would save a lot of jumping from the top of the registration form to the bottom and back...and could save mistakes when we have a LOT of outreach library card forms to enter.

    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)
  18. Allow libraries to bulk change due dates of items to account for unexpected closures. Would be ideal to be able to do this from a records set. Or create a SQL job and put it in GitHub or some other accessible location for libraries.

    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)
  19. We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?

    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. Leap should force logout when browser/browser tab is closed. Forcing a logout at browser/browser tab close would ensure that any open editable records are closed out as well.

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