Skip to content
Innovative Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

582 results found

  1. We would like to be able to limit who can change the Expiration Date and Address Check Date in the patron registration workform. Off the two, Address Check Date is most important as this is what we use to make sure patrons are updating their information regularly.

    These are configured in SA and are set system wide yet staff continue to change them.

    If I remove the 'Patron registration: Modify permission' for member library staff, they won't be able to change other fields.

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

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

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

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

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

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

    32 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. When the callnumber column is pulled from itemrecorddetails via SQL (as opposed to SimplyReports) it includes trailing and leading spaces. It's easy to fix these unwanted spaces in the client, but they don't show up at all in Leap, so can't be fixed. If Leap is to replace the client eventually, it would be great to able to fully edit these fields in Leap (we are hosted, so can't easily modify the data via SQL).

    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. We recently had a location close for a few weeks for a construction project. During that time, we turned it off as a holds pickup option in the PAC. However, patrons who were logged into their accounts and had that location as their default holds pickup location could still place holds for pickup at that location using One-Click. The only way to completely stop patrons placing holds for pickup at our closed location was to disable One-Click completely. This annoyed patrons at our locations that remained open, who saw a popular feature of the PAC disappear without warning for seemingly…

    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. We would like to request that transit slips print for INN-Reach items that have been borrowed by our patrons and need to be returned. When these items are checked in, no transit slips print for us to easily return them to the lending libraries. We came from Sierra, where this was standard. Adding the return transit receipt would streamline our workload back to what it was before migration as we won't have to look up these codes manually. It will also help staff recognize that the returned item is not ours and needs to go back to another library.

    2 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. It would be nice for third party vendors and developers to have access to the Postal Code table via PAPI. Something similar to the OrganizationsGet method.

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

    30 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. When you refresh the Offline installation in Leap it would be good to present the URL for Offline mode bookmarking again. The suggestion would be to show it in the pop-up toast message once the offline data is refreshed.

    There currently is not an easy way for staff to get to the Offline link again without deleting the offline files and setting it up again.

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

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

    26 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. Our library team have requested to be able to see the series name and volume number in the returned bib records when searching with the find tool. It will mean they no longer need to open each result to see this information

    similar proposal as:
    https://ideas.iii.com/forums/951742-ils-polaris/suggestions/48194096-add-edition-statement-to-results-list-in-find-tool

    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)
  18. It would be great to be able to edit or modify publication patterns as needed.

    Currently, we are only able to modify publication patterns IF no issues have been received. After that, the only way to change a publication pattern is to close the current one and open a new one.

    It would save staff time and effort if they could update a current pattern with necessary changes rather than being required to create a new one each time.

    47 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. It would be helpful if the PatronRegistrationCreate endpoint was able to write to the Patron Custom Data Fields.

    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. Currently, we utilize a bookmobile and would love if we can limit that pickup location to our outreach patrons. This could easily be accomplished if we could limit locations based on patron codes.

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