Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

580 results found

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

    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)
  2. 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)
  3. We have instances where an EDI invoice from a vendor will contain materials that were ordered both via EDI and directly through the vendor. The EDI invoice in Polaris only includes the EDI ordered materials and then we add a line item for the materials that were not ordered via EDI.
    In LEAP we are able to add a line item to an EDI invoice but we are not able to receive it manually like we are in the client. I have included a screenshot to illustrate this.

    19 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. Sierra includes the ability export records directly from OCLC into Sierra using the OCLC gateway. This allows librarians to quickly make edits in OCLC using macros, and export those records to Sierra without actually affecting the master record in OCLC. Having this feature in Leap would be great.

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

    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)
  6. 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)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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.

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

    73 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 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)
  15. When a patron accidentally scans an item twice at the ExpressCheck, it performs an auto-renew. It would be nice to have an alert stating it's a duplicate checkout or something that prevents it from using a renewal.

    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 is no hyphen in Branch SAN but Supplier SAN has a hyphen. This causes confusion for both the library and suppliers while setting up EDI for the very first time for new Polaris customers. It would be better if there was a consistency.

    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)
  17. We’ve long benefited from Sierra’s well-supported EDI claims functionality, which has enabled seamless communication and efficient claims processing with our library partners. However, we’ve observed that Polaris currently lacks equivalent support for sending claims via EDI in the same format.

    Can you please port over the EDI Claiming Format From Sierra & Millennium to Polaris? This would make it easier for libraries migrating to Polaris from these products.

    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)
  18. A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.

    So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the…

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

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

    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)
1 2 6 8 10 28 29
  • Don't see your idea?