Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

573 results found

  1. With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).

    We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in…

    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)

    We will be adding a permission to address the issue of users with general access being able to reach the PAPI keys. There are some other comments here that could be considered separate enhancements, so please open new ideas for changes beyond a PAPI Key Management permission.

  2. Although there are current options for purging patron IDs from circ transactions, and deleting account transactions, there are some gaps with removing PII (personally identifiable information) we'd like to see addressed.

    We'd like the option to purge patron IDs from non-circ transactions (incl. patron account history and record history). We'd also like the option to manage patron details on any other tables where history may be maintained after a patron record is deleted (e.g. Notification History, DeletedPatrons, DeletedPatronAccounts, kwmssg, and offline and InnReach process tables). It would also be ideal to have a plan for removing any CNV tables (from…

    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)
  3. 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)
  4. 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)
  5. We would like to be able to adjust the timeout in Leap after inactivity ourselves. Currently, we have to contact support to do this after each upgrade, since it resets itself. If the setting was in SA, we could reset it ourselves after each upgrade.

    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)
  6. We would like Polaris to transition expired patrons to Deleted after a specified time frame. (Such patrons would of course need to have no lost items or checkouts.) We envision this working like Lost Item Transition and the Missing Item Transition. Ideally, we could also set a fine threshold to only delete those expired patrons with less than a certain amount of fines on their cards.

    Adding this feature would allow a library to automatically remove expired patrons and allow for a more streamline process for deleting the ones they wanted.

    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)
  7. It would be awesome if we could add or adjust the information that displays on the Check In screen in Leap, for example to include an item's shelf location for easier staff sorting - and it would also help to catch Display items that have circulated on their return.

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

    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)
  9. In addition to Single Sign-On (SSO) support for Microsoft Azure and ADFS, please consider support for Google Workspace. We recently migrated all of our email for our consortium (42 members) to Google and would greatly benefit from the ability to use the already signed-in information to authenticate into Leap. See screenshots for a design/concept mock-up.

    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)
  10. Item editing permission organizations are based on the Owning Branch of an item. However, permissions for item editing through the checkout page ('Manage Item Dialogs') are based on the item's Assigned Branch (as well as the check-in branch matching the assigned branch).

    We think it makes sense for both these permissions to be aligned to the Owning Branch, otherwise it can leave room for inappropriate changes. For instance, in our consortia some items are owned by one library but lent to others (assigned to their libraries), and this gap has led to item changes by staff that shouldn't have had…

    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. We have had multiple patron requests to be able to sort reading history delivered by API by latest added or by title. Currently reading history is displayed with the oldest first which results in a lot of scrolling by the user.

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

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

    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)
  14. I'd like to see the option to have more than only one screen open at one time, vs needing to close out the current screen before performing another/a different related search (like we can in the staff client).

    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. We have locations that would like greater options for customizing checkout receipts. In particular, they would like to add an image at the bottom -- a library logo, or a graphic version of the library name, or a periodically changeable "word bubble" graphic promoting upcoming activities at the library.

    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)
  16. It would be beneficial to have a total item count in the header of POs and Invoices for quick reference. Currently there is no easy way to get this count from a PO or Invoice because there is not even a row count column under the items view.

    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)
  17. Enhance operational efficiency and standardization by allowing the saving of Leap power searches beyond individual staff profiles. Currently, saved power searches reside only at the personal level, hindering consistent workflows and leading to duplicated effort. Enabling system- or library-level saving for power searches will allow libraries to establish shared, robust searches, improving consistency and ensuring critical search capabilities remain accessible regardless of staff changes.

    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)
  18. I had a coworker ask why she couldn't export her record set into excel to allow for more sortability. I was surprised she couldn't and began looking at documentation and noticed that there is that ability, but you have to change the owner of the record set to the branch or system level, which feels like an unnecessary step. I should be able to export a record set I am working on to Excel with my regular ownership without having the (slim) possibility of a coworker accidentally accessing and messing up anything.

    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)
  19. We’d like the ability to “bulk” cancel holds for items by status (lost, missing, withdrawn, etc.) either by being able to view the circulation status in the patron holds view, or by having the ability to “bulk” cancel holds from a record set.

    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)
  20. When using the date picker, we'd love an option to select "Today" and have it set the date automatically for us. When updating really old cards, it can be a pain to have to select a date with the picker when we have to change every field. Typing is limited in its ability to be a workaround, because it requires specific formatting in order to work.

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