Skip to content
Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

229 results found

  1. Currently, there are two options for handling postal codes, which I like to term: “Wild West” and “In Lock Down”. The postal codes are collected and managed within the Postal Code table in Administration>Explorer>Database Tables. Staff functionality is governed by the permission Patron registration: Modify postal address fields.
    The Wild West option is to allow staff the permission to enter any address information provided by patrons, resulting in a table populated with a lot of incorrect city/town to postal code data. This way lies madness and continuous clean-up.

    On the other hand, removing the permission from staff logins, puts them…

    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)
  2. We often use the "Holds" reports of Simple Reports to watch demand on titles - especially the Hold Count report. It would be very helpful if UPC could be one of the output columns, so that we could copy it for media, which doesn't always have an ISBN in the vendor MARC.
    Right now we have to output the bib record id, copy it and search in Polaris, then copy the UPC from there.

    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. In our consortium, libraries weed items based on their circulation almost exclusively, not based on how new or old they are or how many lifetime circs they had. The most important piece of information to them, the Last circ date, however, is missing from the weeding template criteria. We are aware that you can add dates to the power search for inclusion criteria, but those have to be specific dates, so they can't be reused as criteria several months or years later - you'd have to continue remaking the criteria with new dates each time, which isn't convenient or efficient.…

    24 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. To truly determine whether an item is "older than" a certain time frame for the weeding criteria in our consortium, it should be based on First available date, not Creation date. Many of our libraries add the item record when the item is ordered, which could be months before it actually releases, and they make the status either Being Acquired or In-Process until it's received and checked in, which updates its First available date at that point. Then the item actually begins its "life span" so to speak. So the item isn't truly "older than" a certain time frame until…

    22 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 Damaged feature in Polaris 7.5 was implemented without a permission to enable libraries to turn it off if they prefer their existing procedure. Because we can't turn it off and we have several hundred staff members, many new, all of whom do not have all our procedures memorized, some of the staff now use the Damage feature. This means that we now need a report to catch these transactions and extra staff time to undo them. To try to mitigate, we changed the string "Damaged" to "Do not use". It would be much preferred if a permission would allow…

    7 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 to see additional information and functions available in the Polaris Client or LEAP so that staff have more resources and information to support customers with questions about online resources.

    For example, library staff would benefit from seeing real-time hold information in Polaris about items on Overdrive or Hoopla. Currently, Polaris shows an asterix (*) under holds. Library staff need to either go to the PAC or Overdrive to provide customers with this information. It would help library staff to have information available in one place rather than requiring staff to go to multiple sources to answer 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)
  7. Currently, when working through Picklist processing, items can be marked as "Located". While this is useful for in-library work flow to indicate that it has been found, it doesn't do anything to prevent another member library or branch location from filling the hold request when trapped at point of check-in. This causes problems in a multi-branch or larger consortia system where there is a higher chance of popular material being checked in throughout the day.

    Ideally, it would be great if marking an item as "Located" not only changed the status from the Picklist, but also prevented another item from…

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

    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)
  9. I would like to be able to run reports in Simply Reports to get our item return statistics broken down into time increments (such as hourly), as well as by date.

    This would be useful for tracking busy times and identifying trends/patterns at our library.

    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. Our catalogers would love to be able to search the Remote Databases by UPC.

    18 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, when we turn over weeding lists to staff to pull, they manually mark 'not on shelf - NOS' if they don't find the item. In order to make the new weeding list functional in LEAP, we need the weeding record sets to have the same sort of functionality as a PickList - a column where staff can either mark the item as 'Not Found' or "missing". Ideally the circulation status could be changed to missing at this point, removing the need to manually change these items in the system and remove them from the record set.

    Related to idea …

    23 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. We currently have the ability to set the default status for the 3 request manager views but it would be great to be able to set a default VIEW for request manager to open in as well. At our library, Request Manager is intensively used for receiving incoming INN-Reach requests (ILL view) and it would save time if we could make that the default view.

    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. The edition statement should be added to the results list in the find tool and the duplicate detection results. The edition statement is already visible to patrons in the brief display of the records in the results list in the PowerPAC. When staff need to search by title or deduplicate records, they need to look at each record to identify the record for the correct edition. If the edition statement were added to the table that displays the results, they could identify the correct records in a more efficient manner.

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

    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. When staff log out of Leap at the end of their shift, Microsoft prompts them to sign out of their Microsoft account. I think it confuses staff, they click on the prompt and then they get logged out of their Microsoft account. They then have to log back in and due to MFA need to get a code to log back in. This isn't ideal.
    Customer support said currently this behavior is how Leap with OAuth/SSO works. Leap uses the identity provider to control the login and logout when setup with OAuth/SSO. Can you place an enhancement request to see…

    7 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 receive vendor records with file extensions .FIL and .001. We are able to import these in the Client but are not able to import them in Leap.

    7 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. In Simply Reports, some filter menus do not populate options until a library/branch is chosen (i.e. Shelf Location, Stat Code, Statistical Class). This is helpful for consortia because the menus only become populated with the options available at each selected branch(es), keeping the options to a manageable size.

    We would like to see this dynamic menu functionality applied to the Collection, Material Type, and Patron Code filters as well.

    Currently, our consortium has 55 Material Types, 57 Patron Codes, and 284 Collections to choose from in these menus, which becomes quite overwhelming for users and involves A LOT of tedious…

    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. We would like to be able to copy an existing branch when creating a new branch, since often our additions are branch locations of an existing library that will have almost the same exact settings.

    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)
  19. We have a long list of vendors and would like to clean it up, removing any who we no longer purchase from. This can't be done because of the links and layers in Acquisitions to attached purchase orders and invoices. It would help with clutter if there was a way to delete these suppliers or hide them in some way.

    22 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. We would like the ability to made Collection a required field when adding item records. While we can instruct all of our members to have Collections selected as part of their templates, there is still the possibility of forgetting and having items that are missing a collection. Having a collection at minimum, and ideally collection and shelf location combination set on each item greatly helps wayfinding for the patrons, and we'd like Polaris to allow us to enforce selection of at least a Collection. Other customers may want to enforce selection of both Collection and Shelf Location. As long as…

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