Skip to content
Innovative Idea Exchange

ILS - Polaris

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

676 results found

  1. This might be coming in 8.0 - it's not on the roadmap, but maybe it's too small to feature there. In the Polaris client, within an authority record, there is an option to create links to bib records (see attached screenshot). This same functionality should also be included in Leap in order for cataloguers to fully switch over to Leap.

    42 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 are upgrading to 7.7 and have just decided to NOT turn on the new feature that suppresses non-blocking 'blocks' such as the 'patron has holds' popup block.

    Ellie K. submitted a related request here: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/49700207-remove-pop-up-about-holds-on-shelf-when-checking-o to suppress the block if the first item being scanned for checkout is a hold from the current branch.

    We'd like to take this a step further and suggest the block appear when the check out workform is opened. This achieves the purpose of the block (triggering staff to alert the patron that holds are available) without even getting into whether the transaction that…

    42 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. We have a long list of vendors and would like to clean it up, removing any who we no longer purchase from. This can't be done because of the links and layers in Acquisitions to attached purchase orders and invoices. It would help with clutter if there was a way to delete these suppliers or hide them in some way.

    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)
  4. Unless I'm doing something wrong, when I am in a PO and go into a PO LINE to check ISBN, discount or whatever, I hit save and go back and it takes me to the top of the PO. Some of my PO's are really big so I'd like to know how to just go back to the spot I was at before instead of the top.

    42 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. In the client, funds link directly to invoices, POs, POLIs, and other related records. Funds in Leap have very few links. Direct linking to working acq records facilitates tech services workflows.

    42 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. 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)
  7. Option to automatically update circulation status of an item to "missing" if the item is not found on a picklist after a designated # of searches.

    41 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. As Polaris currently exists (v7.3 at my library), User 1 wants to share a bibliographic record set with User 2 and User 3. In order to do this, they have to change the record set's owner from User 1 to Organization 1. But this allows all members of Organization 1 with the permissions "Cataloging Record Sets: Modify" and "Cataloging Record Sets: Delete/Undelete" to make changes to that record set. Let's say that at some point down the road, User 4 sees this bib record set owned by Organization 1 and thinks they're being helpful by updating or deleting it. They…

    41 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. Currently in Leap (we're on 7.8), in order to take full advantage of an item template, you have to click on Actions--Create Item (within the bib record), then add your barcode & select the template you want to use, and then click Save. If you don't click on Save, the template only populates some of the template information. It doesn't change any of the call number fields or the number of renewals, even when the option to use template values is checked.

    This is existing functionality in the Polaris toolbar client, and should be in Leap as well. (See attached…

    40 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 printing spine labels from an item record in the client, you can choose to print multiple of that same label. I would like to have that functionality in Leap. This will be helpful when processing multiple of the same item without having to send the label request for each individual item.

    41 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. Polaris supports a preferred pickup branch for patrons. This request is to extend that support to allow the patron to set a preferred pickup area.

    Many patrons prefer to 100% always use a particular pickup area, for example outside lockers. So, they shouldn't have to select that area everytime they make a request.

    This would allow them to set their own preferred pickup area the way they can set a preferred pickup branch. This preferred pickup area should also be used when the staff bulk places a title on hold for a batch of patrons, again the same way the…

    40 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. To truly determine whether an item is "older than" a certain time frame for the weeding criteria in our consortium, it should be based on First available date, not Creation date. Many of our libraries add the item record when the item is ordered, which could be months before it actually releases, and they make the status either Being Acquired or In-Process until it's received and checked in, which updates its First available date at that point. Then the item actually begins its "life span" so to speak. So the item isn't truly "older than" a certain time frame until…

    40 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. I would like to upload images for an item record. We are attempting to build our Library of Things and these items don't have photos tied to the item record.

    39 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. In our consortium, libraries weed items based on their circulation almost exclusively, not based on how new or old they are or how many lifetime circs they had. The most important piece of information to them, the Last circ date, however, is missing from the weeding template criteria. We are aware that you can add dates to the power search for inclusion criteria, but those have to be specific dates, so they can't be reused as criteria several months or years later - you'd have to continue remaking the criteria with new dates each time, which isn't convenient or efficient.…

    39 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. As a multi-branch system that floats some of our collections, we desperately need a way to set limits on the number of copies on shelf without giving up our ability to set limits on overall floating collection size. Currently in Polaris you must choose one limit or the other. Being able to spread copies throughout our system makes them more available for discovery and increases circulation.

    40 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. In the client, staff often use the link to individual purchase order line items, but this is not yet available in Leap. Because an invoice may have many linked POs, and POs may have many POLIs, it can be difficult to find the correct POLI without access to direct links.

    Adding POLI links would reduce friction for tech services staff making the move to Leap.

    39 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 a number of custom reports in the Polaris Staff Client that need to be accessible to our Circulation Staff in Leap. Ideally all Polaris canned reports should also be available to all staff in Leap. One custom report we use is for patrons who don't have an email address. Their notification option is set to mailing address. However, if they have a hold we call them instead of sending the hold notice by mail. The custom report is a quick way to find the patrons that we need to call. Staff have to have access to both Polaris…

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

    Just to set expectations, our strategy at this time is for users to access reports through the SSRS portal. As Eleanor mentioned in her comment, we are adding customizable menu options to Leap in 7.5 with the intent that they be used to link users to the reporting interface.

  18. The Polaris Leap login screen consists of two text fields, a button, and a low resolution PNG floating upon an ocean of #CCCCCC. It is, in a word, boring. There are no easy customization options offered that allow a library to give it the look and feel that they want, save for one option that will change the colour of the menu bar. Now, granted, if you have a staff member with some web coding knowledge, they can modify the Leap CSS and replace some images to give things a spruce up. Five lines of code and a fresh image…

    38 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. Picklist is great - unless you are a large location that needs to distribute the list among several staff and do not have devices for everyone. Currently in staff client, we can sort multiple columns - example, by Collection then by call number within collection, then hide unwanted columns, print and distribute pages among multiple staff. You can only sort 1x in Leap and then there is a lot of white space, etc. which results in paper waste. It would be great to have the ability to fine sort, hide columns and headers when printing Picklist. Without that, staff will…

    39 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. Polaris has long supported an option in Patron Registration where you can mark a patron record as "Do Not Delete." I'd like to see that same functionality carried over to record sets. For me, it's a fairly common task to recover accidentally deleted record sets for staff members who've somehow managed to delete an important and often used record set, despite every warning they receive.

    Specifically, I'd like to see this option added at the permissions level, with separate permissions for:

    • Mark a record set as "do not delete"
    • Clear a record set for deletion

    That way staff members can't…

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