Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

476 results found

  1. Some locations need to apply both a distributed tax and a header tax to invoices (in Canada a PST and a GST). Currently, Polaris adds the percentage from the distributed tax to the header tax, so the total is higher than it should be. Libraries can work around this by reducing the header amount by the percentage of the distributed amount, but this is a fiddly process and sometimes results in rounding errors.

    We would like to see Polaris parse the calculation of the header tax charge, so it no longer includes the distributed tax amount. Polaris should also round…

    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. Being able to see a more complete circulation statistics for the lifetime of a title gives selection staff a more complete picture of the use of a title, in order to make better decisions about purchasing future titles by an author or in a series.

    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)
  3. In the Item tab of the popup window for a patron's overdue charge properties, the "Check Out date" indicates the item's last renewal date, rather than its actual check out date. A more helpful date to see would be the original check out date; this would also better suit the title for this line.

    11 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. It would be nice if from the staff side in Polaris and LEAP we could select whether to notify the patron if an item they placed on hold gets cancelled. Sometimes we have to cancel holds for various reasons and LEAP is often faster in notifying the patron with no context when their request was cancelled which can cause confusion for the patron. Staff should get the option of whether a patron gets notified or not and if possible, if we could have the option to add a message to the cancel notification they get.
    Relatedly, patrons should get a…

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

    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. While there are many advantages to way that Polaris calculates TOMs, there are currently some significant limitations for differentiating between formats. 4K BluRays, Playaways/Yotos, and video game systems are all very difficult to distinguish from one another when using only the MARC fixed fields. Additionally, many libraries are expanding their collections with Libraries of Things that are usually coded as "Kit" or "Three Dimensional Object" rather than describing what it actually is. These bib TOMS are also now featured prominently in Vega Discover's rollups.

    Over on the Sierra side, the options for bibliographic format can be customized. If a library…

    117 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. Right now in the Polaris SIP environment, if you attempt to get patron information using a 63 message, but you put in the WRONG password, the patron accounts LAST ACTIVITY DATE will STILL be updated.

    We recently had a vendor that for some crazy reason, went through and was attempting a 63 message for all patron barcodes they had on file. This updated the last activity date for tens of thousands of patron accounts.

    Although I suppose there could be some arguments for this behavior, it should not be the default. By default if an account login FAILS, for any…

    31 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 it is only possible to apply a credit to an entire invoice, which then distributes that across all funds for all items on the invoice. We rarely actually have a credit that applies to an entire invoice. It will apply to a single title, or even and single item, and should only apply to the fund for that item/title.
    It would be much better to be able to apply a credit to a POLI, or even better, a specific POLI segment.

    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 our previous ILS, we had the ability for renewals to have a different renewal length compared to check out length. For example- books checked out for 28 days but renewals were 14 days.

    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)
  10. We would like Polaris to transition items with a Circulation Status of Damaged to Withdrawn after a specified time frame. We envision this working like Lost Item Transition and the Missing Item Transition.

    Adding this feature would allow a library to automatically remove items from a patron's record (but still retain any associated charges) and allow for a more streamline process for deleting item records.

    37 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. Currently cutting and pasting from OCLC Connexion Client into Polaris is cumbersome. Allow for complete fields and their delimiters to paste into Polaris seamlessly.

    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. Currently, the only way to view pending holds for pickup at other libraries in Request Manager is in the Polaris Client. We would like this brought over to Leap. This idea would make the Request Manager in Leap and the client equal in terms of capabilities.

    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)
  13. Currently, receipt/slip configuration is hard-coded into Polaris system administration. Libraries are limited in what information they can add to a receipt or slip and do not have control over design elements in sys admin. Innovative does not recommend modifying the related SQL job to make changes there. It would be helpful to have greater flexibility and customization options for libraries, especially for hold and in-transit slips. For example, a library could configure in-transit slip information to match what is required by their library system's delivery service.

    53 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. On an item record, you can currently only see the information about the current borrower and the most recent previous borrower. This should be increased to at least 3, so that in the case of a question about condition or missing parts, we have more than 1 patron we can ask.

    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)
  15. Option to automatically update circulation status of an item to "missing" if the item is not found on a picklist after a designated # of searches.

    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)
  16. Currently staff can either edit/modify bib records or they can't. Greater granularity in what edits can be allowed would help distribute the work of maintaining bib records.

    For example, if acquisitions staff could be allowed to add additional ISBNs or UPCs to existing bibs, it would free up cataloguing staff from this simple task without opening bib editing completely to a large number of people.

    In a larger library system, especially a consortium with a shared catalogue, this could be a big time-saver to both acq and cat staff.

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

    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)
  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. Because new is both a location and a status, it would be helpful to have an item level field in LEAP that is for "new" items. A simple checkbox would be sufficient, like "holdable" or "display in PAC." This would free up shelf location for any items that are both new and in a specific area, such as Travel, World, Graphic, etc.

    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. It would be great to have a way in Leap to change the patron barcode and have it auto populate the "Former Barcode" field in a single step. Perhaps a button could be added underneath "Reset Password" for "Replace Barcode" that simply prompts the staff member to scan a new barcode number. Leap would then move the existing barcode to the "Former Barcode" field, and then populate the Barcode field will the newly provided number. Help us save a few steps! Thanks for the consideration.

    27 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?