Skip to content
Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

453 results found

  1. Polaris Leap--Be able to use subject headings to browse/search while in Leap without having to go into the PAC.

    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)
  2. Ability to add QR codes to printed or emailed receipts

    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)
  3. We've discovered the keyboard shortcuts in LEAP do not work when you have cap locks on. Our catalogers are a 50/50 split on those who always have cap locks on while they work and those who don't. I'd like to have the option available for those who find it easiest to catalog with the cap locks and use the shortcuts.

    This is related to a couple of other ideas - https://ideas.iii.com/forums/951742-ils-polaris/suggestions/48517199-keyboard-shortcuts-for-marc-editor

    https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46446820-accessibility-shortcuts-in-leap

    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. We need a way to bring perennial critical patron info to staff attention without creating blocks for customers or forcing staff to open the full patron registration. Having this info in the patron record header or properties would be ideal. For example: at our library, customer registered at branch is not critical info yet it is the most prominent value displayed in the header after name and card number, if we could designate UDF values to take it's place (such as bookmobile stop or language assist needed) or have space to reveal a designated UDF value under patron properties, it…

    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)
  5. The Polaris Transactions database TransactionID is an int data type. This 2,147,483,647 means the biggest number supported by the database. In our busy system, we're about halfway through the available TransactionIDs as we're about to reach 1 billion. This field should be moved up to a bigint data type. Otherwise inserting new data will fail.

    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)
  6. It would be nice to have the ability to set different email notice schedules for each branch.
    We would like to line up our notice delivery times with the operating hours of our branches, or allow more frequent hold notice emails at a specific branch.

    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)
  7. Currently, when a patron selects a library for a hold in the PAC and Pickup Areas are enabled, the default option is "None" which might not make as much sense to them, and they might think they have to select one of the other options (if there are any). Can "None" be changed to something more intuitive like "Walk-in" or "Inside" or "Regular"?

    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)
  8. The weeding workflow and weeding record sets were added to LEAP in Polaris 7.5. I would like some more functionality in the weeding record sets at all stages of the approval process -- namely being able to bulk change and delete records from the set, being able to remove records from an approved record set, and being able to unapprove a list.

    I know there are options in the weeding template to change the record status to withdrawn and have the records automatically deleted when approved. However, we change our records to a status of "weeded" (we took over bindery)…

    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. There is currently no warning if a patron selects titles in one of their saved title lists with the intent to place a request but then accidentally clicks the Remove button instead.

    Providing either a warning message, as is the case for things like canceling holds, or putting deleted titles in something like a trash can for 30 days or so, would prevent accidental deletion and related frustration and improve the user experience.

    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)
  10. In Simply Reports, add ‘Hold activation date’ as an option under ‘Hold relative date filters’ for Hold List reports.
    We want to be able to use this report to provide a list of holds 45 days or more not filled based on the Hold activation date.

    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)
  11. The multiple holds feature in Leap is really nice - unless you want to make sure that a bib you're selecting is actually the thing you want, the need for a preview option has been suggested in another Idea Exchange submission.

    Another common use for multiple holds is creating what we at DPL call "Teacher Sets" where staff pull a bunch of topical items based on criteria provided by a teacher, place holds on them and then check them in to fill those requests and contact the customer.

    Right now this is really clunky. Since there is no option to…

    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)
  12. There is currently only one setting that determines how long an item needs to be overdue before it reaches billed status and charges the patron for the cost of the item.

    We would like to have different types of material reach billed status at shorter intervals. For example, we would like for a device that checks out for 4 hours to be billed on the patron record after 1 day, rather than the 63 day interval that we use for standard material. Similarly, we would like our hotspots to become billed after they have been overdue for 3 days.

    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)
  13. Polaris' claim return function is great for locally-owned items but is problematic with INN-Reach. We are constantly reminding staff NOT to use Claim Return for INN-Reach items because it can break transaction links but they continue to do so. If system admin allowed us to exclude our INN-Reach and WorldCat material types from Claim Return and Claim Missing Part functions, it would reduce errors significantly.

    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. I would like to submit the idea that Polaris offers the ability to run a report based on patron activity dates, and not their LAST activity date.
    Currently, we can only run a report using "Last Activity". This is not helpful if trying to determine how many patrons were active in a given period because if they have had activity after the specified period, they would no longer be counted in the report.
    There is a canned report under System > statistical summary, but it only looks at borrows, and would not count ILS card activity such as from a…

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

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

    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)
  17. When items are checked out through SIP2, Polaris includes the "You just saved __ by using the library" text in the response. However, this information is not available when using the ItemCheckout method through PAPI.

    As we start moving vendors away from SIP2 and towards PAPI, we'd like to replicate the functionality of SIP2.

    Thanks

    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)
  18. Currently the API only performs basic duplicate detection (name, birthdate, barcode, username, and optionally the name on ID) when a patron record is created using the PatronRegistrationCreate call. It does not apply other optional settings - email, phone 1, or the UDFs - these only get applied directly in Polaris or the PAC. This idea is for including these optional settings in the API logic.

    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)
  19. Inventory Check-in via Leap is recorded as Check-ins for Item Statistic reports in SimplyReports. A way to filter inventory check-ins from statistical reports would be nice.

    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)
  20. Be able to bulk add stat codes. Currently we can only add at the branch level manually because the library and system level tables are too large. This requires a manual change or contracting Polaris every time we want to add stat codes for all locations.

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