Skip to content
Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

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

411 results found

  1. Sometimes I have a lot of records open in the workform tracker, and it's a pain to have to go into each to close it. It would be useful to have a button I could quickly click to close them instead.

    In cases where a record has been modified it should generate a prompt about saving changes, and show you the record again in this case so it's clear what's being saved.

    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)
  2. When dealing with missing/damaged/canceled orders, we start at the Bib record and link over to the attached POs/Invoices. Right now in LEAP we have to start with the PO or Invoice, which we often don't know when we have the book in hand. I'd like to be able to link from the Bib Record to either Purchase Orders or Invoices or both.

    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)
  3. Leap should include the ability to create or add to an item record from the check-in workform. Most of the functionality is already there in that items can be selected via checkboxes and all items can selected from the topmost checkbox. By adding the option to the Actions menu, circ staff could quickly roll items over into a record set for a variety of other uses.

    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)
  4. In Polaris, a single delete of a bib/item record will result in that record being 'marked for deletion.' It is no longer visible in the PAC, but is still visible in Polaris with a Deleted status. Deleting a record in Deleted status, or what we've termed 'double-delete,' will result in the record being fully purged from the database.

    Sometimes, staff will delete a record and go back to it to verify the deletion. They see it's still visible in Polaris (missing the Deleted status) and delete it a second time. This accidental purging results in no longer being able to…

    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)
  5. Frontline staff currently have an alert to click through when they view an Authority record. Could there be separated permission levels to allow staff to View an Authority Record without clicking through the pop-up, vs Modifying these records?

    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)
  6. I realized recently that all our bibliographic records have the Modification Date populated, even new records. It turns out that the process of creating the record will update the Modification Date due to an aspect of the process. This doesn't seem part of the intended design, so it would make sense to correct the process to stop adding a Modification Date entry.

    Idea Value
    This may cause confusion for staff working with bib records, and in general it's not good from a record metadata quality perspective to have misleading modification details. It can be filtered around in queries (the modifier…

    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)
  7. Within the bibliographic record, occasionally there are duplicate fields. We need a way to easily detect them, especially with bibs upon bibs that are merged. We end up with a ton of duplicate 035 fields.

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

    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)
  9. In the client we are able to create multiple new item records at the same time and we would like this functionality in LEAP as well.

    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)
  10. Allow multiple selections of Organizations & Patron Codes to populate Material Type list (lower table) on the Patron / Material Type Loan Limit Blocks, Policy Table.

    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. When libraries within our consortium borrow and lend items among each other, they send those items through the mail. Currently, they have to manually look up each other's mailing addresses (many times by Googling which isn't always accurate). It would save staff time and reduce errors if a library's mailing address could be included on the In-Transit Slips.

    This would also allow for libraries to ensure the requesting library has their 'preferred' mailing address if an item needs to be returned to a location other than the owning library. For example, if a Main Library processes holds for its smaller…

    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)
  12. Today if a record set is deleted it's still visible in the list of record sets a specific record is a part of (either on the Record Sets tab in Leap, or list of Linked Record Sets in the client). However there's no clear indicator that it's a deleted record set, which can cause confusion for staff. It would be helpful if the Record Status column was visible, and if there was an option to not display deleted record sets (ideally the setting could be applied at various organizational levels). Both these options would allow more clarity and control for…

    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)
  13. Currently, customers' first, middle and last names display identically in Leap patron accounts. This can make identifying the last name difficult which impacts staff ability to properly address customers and to accurately retrieve holds for customers with more than 1 last name. We propose bolding or in some other way making more distinctive in the patron account header any values in coming from the last name field in patron registration. Currently, we often have to click into patron registration in order to determine which name(s) are actually in the last name field when retrieving holds, etc. Making this change would…

    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)
  14. Currently deleting older Import Reports and Bulk Change Reports is manual and can be very time consuming. Our consortium has generated a lot over time, and even once we get through the backlog it would be onerous to keep up with regular activity. It would be handy if there was a process that could run on the back-end deleting these, so managing a backlog doesn't need to be a concern.

    I picture the process being optional, and deleting the reports based on age (older than X number of weeks/months/years). The process would run overnight, and would ideally be built to…

    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)
  15. Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.

    This was previously submitted in the old enhancement process:

    "Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can…

    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)
  16. I have occasionally found multiple supplier records for a single supplier account, whether added by mistake or under multiple names (Thomas Klise and Crimson, for example). When these supplier records are accidental duplicates, I believe it would be helpful to have the ability to merge them (retaining all linked POs and invoices) to maintain one supplier record per account.

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

    17 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. As a library with a lot of historical serials, it would be very helpful to have barcodes visible in the OPAC so if I want to look at a serial issue that's a troublemaker in the catalog, I don't have to scroll through sometimes hundreds of issues in the client/LEAP to find the one I wanted to investigate.

    17 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 need a note field in the item record that pops up as a warning box at check out and check in for notes that staff and patron may need to act on before checking out and in. Notes such as "Patron needs to sign a hold harmless form." Or the price of this piece of the kit is $250.00. Or "Item must be returned to this library." Staff should be able to close the window once they have read it.

    17 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. Current functionality says "If the item is held at your library (the pickup branch is the same as your log-in branch), and you change the pickup branch, the hold will automatically change from Held to Shipped."

    We would like this to function the same as if the item is not at your location and mark the item so it appears on the holds to transfer list. The staff will then scan the item to mark it as shipped. We have staff that work at different service points no where near our holds shelves and it would be convenient if they…

    17 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)
1 2 6 8 10 20 21
  • Don't see your idea?