Skip to content
Innovative Idea Exchange

ILS - Polaris

Recently Activity

ILS - Polaris Updated

Last In House Use column

Reporting & Analytics UNDER REVIEW

ILS - Polaris Updated

Automatic processing for item record details

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Patron block pop up

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Holds that can't be filled

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Volume-Level Holds for Blank Volume Field

Circulation, Access Services & Fulfillment UNDER REVIEW

ILS - Polaris Updated

Live Preview Within Bibliographic Record Sets

Cataloging & Metadata Management UNDER REVIEW

ILS - Polaris Updated

Vendor integration

Customer Relationship & Account Management UNDER REVIEW

Don't see your product?

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

695 results found

  1. We would like the ability to set one number of days for an item to remain held if other holds are attached to the same bib record and a second setting to set a number of days for an item to remain held if no holds are attached. This would allow high-demand items with waiting lists to move more quickly through patrons, while at the same time keep low-demand items on hold shelves for longer, increasing the rate at which they get picked up and borrowed.

    Right now, we hold items for 7 days. For a popular title, that adds…

    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. Blocking a patron from being able to place holds when holds unclaimed reaches a set limit/threshold within 6 months would be beneficial. There is a great deal of staff time and financial resources that gets wasted when items on hold shelves never get picked up and checked out. The block could auto-clear after a set time period.

    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. It would be very helpful to have an option to view Import Reports for both bibliographic and authority record imports as a spreadsheet, as well as the existing PDF.

    This is mostly true for the records (and associated errors, warnings, and messages) themselves, rather than the more general import information (duplicate detection criteria, MARC validation rules, etc.). This would be helpful for quickly flagging errors, duplicates, and other areas that need attention without having to scroll through a lengthy report.

    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)
  4. There's no limit (that we've run into, anyway) in the desktop client to the number of z39.50 remote databases you can search at a time, but Leap has implemented a 10 database limit. If there needs to be a limit, can it be slightly higher at least?

    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)
  5. There have been many times when we've needed to know which specific copy(barcode) is in transit to fill a hold. Currently the only option seems to be going thru each item record to see which is attached to the customer record. Very annoying and time consuming. Perhaps on the Holds Queue screen could include a column (Item Assigned) to list the barcode filling the hold when a hold has been trapped. Or on the Hold Request screen, on the Satisfied By menu a indicator of which item is being used for that hold. Or both.

    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)
  6. The new Web version of System Administration is great, but I was sad to learn when upgrading from Polaris 7.7 to 8.0 that the search filter box for Workstations and Staff Users is no longer "sticky". In 7.7, I could enter a search for one of our Branches, click on a workstation, edit it, close it, and return to my filtered-by-branch search. Now, when you leave a workform, you return back to the full workstation list. Same for staff members. I'd like a button similar to the Leap "return to results" button in the workstation and staff member modules of…

    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)
  7. In Sirsi, there was a quick option to post holdings to OCLC (for ILL holdings). In Polaris, we have to use OCLC Connexion and post the holding there for each item that is not automatic (like items from Ingram). This is not ideal, as it takes more steps to log into Connexion and find a good record (when we are already locating the record once from a remote database when we add the record in LEAP). It would be nice if there was an option to click to post the holding while cleaning up the record.

    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)
  8. Currently, when I create a record set for authority records not connected to a bib record, and then try to delete multiple records, I get a pop-up that asks if I'm sure I want to delete the record even though it is attached to the record set (that I just created). I get this pop-up for EVERY authority record I try to delete, so if I delete 100 records, I will have to see this pop-up 100 times. There is no way around this currently and I'd like it to be fixed. It should be like deleting items in other…

    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. It's possible the Description and Comments configured for MARC validation display somewhere else already, but it would be nice if there were a couple of buttons to display that data in the MARC tooltips. The Description would be helpful for any tags that aren't used regularly or for staff with limited familiarity with MARC formats while the Comments could be useful in communicating local cataloging policies. Bonus points if we could allow staff with the appropriate permissions to edit the Description and Comments directly in the tooltip. It's not a particularly good example, but you could include something like "Please…

    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)
  10. 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,…

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

    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)
    1. Patron has a held item
    2. Held item is cancelled
    3. Then the patron record is deleted
    4. The hold on the holds to action will have no patron name shown.

    This means that staff have no real way to know where their hold is on the hold shelf (holds are arranged on the shelf by patron name) to be removed. This was originally entered as a bug, but it was closed as a bug because it was working as designed.

    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)
  12. When some notice types are posted, they show up in the item record history. But not all notices show up there, for example, printed hold notices do not show up there. It is also difficult, for example, if you want to find out who printed a fine notice to be able to locate that information because it isn't always tied to an item record.

    This request is to add to the notice history information on the user and workstation that posted the notices to the database. There is very miniscule information in the notice history already.

    This additional information would…

    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. We have dozens of SQL searches, however it can be hard to find them. They are presented in an alphabetical list, but over the years our naming isn't always consistent. It would be great if you could filter the name drop-down like you filter can in other areas of Leap.

    So, for example, if I typed "volume" it would show many any SQL search with Volume in the name. Bonus points might be if we could also be searching some of the SQL search contents itself because maybe I want to find all SQL searches that query a particular field…

    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 useful to have in the item history when a hold was activated. I had an instance where an item was put on hold for the wrong account, and it would have been useful to see who had placed the hold or where it had been added. I figure you can see this from the hold record, but the staff member who had received the accidental holds cancelled them before we got a chance to look at it.

    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)
  15. Polaris should be able to generate barcodes outside of self-registration. Sometimes you want to generate barcodes without relying on a physical card that already has a barcode printed on it. Polaris already can do this because it does it for self-registration cards. So it should be able to occur on demand.

    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)
  16. We have found it hard to work with the Current and Recent workfrom menu when working with lots of Patron Records, or more commonly, Duplicate Patron Records.

    Names work, but when names are similar or the same it can be hard to figure out which records are which.
    Sometimes staff are working with Barcodes as a reference vs. patron names.

    It would be nice to have a subtext under the Patrons name in the Current and Recent workform list that shows the last 4 digits or the full barcode underneath the patron name.

    I have 2 images attached that demonstrates…

    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)
  17. The current method for changing a Polaris Staff Member's password is clunky and not ideal if part of a large library system. Additionally, all SA management is moving towards the web-based interface. It makes sense to incorporate staff password management into the SA web-based interface.

    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)
  18. Please expand the search functionality to include searching and pulling results for both the 024#a MARC tag, as well as 020#a

    Functionally this will improve searches as results will include hits on an ISBN whether it's in 020 or 024

    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)
  19. Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.

    This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like…

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