Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

617 results found

  1. Staff would like to be able to bulk change a patron's pickup branch for selected (or all) holds on the patron's account. Be they holds already trapped, suspended or active. We often have patrons that move from one part of the area to another and need to change their holds to reflect their new pickup branch. Having to change one hold at a time is tedious.

    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)
  2. Please add more options for adding records in a record set to purchase orders or selection lists in Leap. Currently, the only actions in Leap are to bulk add records to a new or existing PO; the Polaris client also has options to add all records to a new or existing selection list, to add selected records to a new or existing PO, or to add selected records to new or existing selection lists. (See screenshots.)

    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. Post OverDue notices to the database without printing them. We have libraries that are not regularly printing and posting to the database overdue notices so items move in the system to missing and withdrawn before some libraries ever send out a notice. Some libraries haven't sent them in 1-3 years. So, I want to post them and then email a pdf on the overdues automatically on the first of every month.

    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)
  4. User Interface remains unintuitive, and lack of session tab awareness contributes to workflow issues.
    Cosmetic appearance, the Claim icon appearance could be changed or improved.
    Add Tabs to be developed as an alternative for User Interface other than the hamburger three horizontal lines.

    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. Tab session visibility is unclear, leading to records being locked unknowingly by users.
    In addition to "hamburger" on upper left-hand side of the screen three horizontal lines.

    Please add Tab indicators or auto-close function when navigating away.

    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)
  6. POLI does not link to the supplier record. Bibliographic record does not link to POLI or invoice line item unlike in the Client.

    Add functionality in LEAP to not only link from Bib to PO or Invoice but also link to line item.

    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)
  7. Polaris currently (as of 7.8) offers some limited customization of which fields in the patron registration form in Leap are required to save a record.

    When the "Name on ID" fields were introduced several releases ago (7.2?) we were excited. However, the way the feature was implemented meant that the primary name fields were now the "preferred name" fields and were required to be filled out in order to save a record. However, a record could be saved without recording a name on ID.

    Our broader city government did not like us dropping the requirement to capture patrons' legal names,…

    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)
  8. We recently did an overhaul of our messaging in the notice strings to make things clearer for patrons, and we had issues with clear messaging for Almost Overdue and Autorenew notices, since there are sometimes two separate options for Almost Overdue and Autorenew notice strings, but not always. This only allows us to partially customize them separately, when we would like fully separate options. As a result, for certain strings, we are forced to be more vague, which is not ideal.

    Please offer separate options for the email subject line and the email 'other header' strings, as well as the…

    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)
  9. In the toolbar version of Polaris, it is easy to make bulk changes to item records from the PO, which we occasionally need to do to change things like shelf locations, call number prefixes, and notes that can’t be added via the item record templates. In Leap, there’s no bulk change option on the items tab for a purchase order, and there is also no way to select the item records to add to a record set to be able to do a bulk change that way, meaning any edits to the item records needs to be done one by…

    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)
  10. When checking out a stack of items via RFID pad, LEAP will only display the held item's patron's name and barcode. It would be helpful to have the item's title and/or barcode, so we may capture the hold without going through each item individually.

    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)
  11. Just as Polaris offers a workflow for the automatic deletion of patron records, introducing a similar feature for item records would be a highly valuable enhancement. The ability to automatically remove items based on defined criteria would streamline operations significantly. Currently, the manual process—such as creating a Record Set and performing bulk deletions—is repetitive and time-consuming. Automating this task would not only improve efficiency but also reduce the administrative burden on staff.

    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)
  12. Please update Label Manager to restrict the Content option of Author from including subfields 0 and 1 when printing. These are relatively new fields for linked data. We would like to retain the data without have to manually deleting it in Label Manager to print pocket labels. They are valid in MARC21 and should be retained to future-proof our records for if and when Polaris makes use of linked data.

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

    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)
  14. Provide options to allow patrons to toggle showing images/details for a simpler view within the PowerPAC. Ideally, this would be available regardless of login status.
    E.g., "Show images" and "Show details" in the search screens (simplified to title, author as well as the buttons on the right for Availability, Full Display, Place Request, Add to My List )
    "Show images" in the checkouts, lists, saved searches and reading history screens.

    We've had a few patrons request a more simplified view of the PowerPAC (which we call the basic catalog, opposite our Vega Discover catalog) with less information and images to…

    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. Make it easier for staff to quickly view the borrowing history of an item by including a column that shows the customer's name. Having to click on the PATRONID is meaningless to staff and an additional unnecessary click.

    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)
  16. We would like to see a "Patron barcode for damaged item" option as an output column in SimplyReports, similar to the one available for Lost items called "Patron barcode for lost item". This would help us when running reports on Damaged items.

    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)
  17. Please allow the checkout screen in Leap to be sorted/alphabetized by clicking any of the header columns, Title in particular. This is currently something that can be done in the Polaris client, and is useful for library staff when checking out large amounts of books to patrons who would like an alphabetized list of what they've just checked out. The columns in Leap appear to be clickable for sorting, but they currently are not.

    21 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. For pocket labels update the author field to exclude new URI fields found in the 100 field (subfields 0 and 1). This should be an easy fix. We want to retain that information in the bibliographic records without having to manually remove them in label manager before printing.

    When working with an SL4 or any label type that has a spine and pocket label, allow for alignment to vary between the spine portion and pocket portion. This is important for how we label our picture books. We center align the first 3 letters (with linebreaks) of the author's name. Setting…

    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)
  19. This is somewhat of an add-on to other improvement requests to the multiple holds feature. We would like to have an option for bib-level multiple holds. We have noticed that when teachers or book club leaders are placing the multiple holds and assigned to an item-level hold, they might get routed to a member library that doesn't frequently check their requests. This is absolutely a training issue, but we do see this a lot with our K-12 school libraries. We would like to see an option to put them in the queue as a bib-level hold where they will get…

    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. We would like to have an option where non-resident patron types have a blocking condition for e-resources, but it only limits e-resources. We would like for them to be able to still manage their online accounts and renew physical items, so the patron-initiated blocking condition does not work. Right now, that can only be done in CloudLibrary through SIP, not API.

    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)

    I think this idea needs some clarification. Are you using a non-resident patron code? If so, we do return the PatronCodeID in our PatronValidate API. I wonder if this is a situation where Cloudlibrary has infrastructure in place to support checking the patron code via SIP, but not yet via the Polaris API.

  • Don't see your idea?