598 results found
-
LEAP POLI linking needed
POLI does not link to the supplier record. Bibliographic record does not link to POLI or invoice line item unlike in the Client.
Add functionality in LEAP to not only link from Bib to PO or Invoice but also link to line item.
5 votes -
Allow for adding a file to a record set by UPC
Currently, the only option for importing a file with bibliographic data into a record set in Leap is by ISBN. It would be helpful for staff to have the option to be able to use UPC as well, as ISBN restricts this to just books and audiobooks. This leaves out DVDs and Blu-rays, as well as other non-book/audiobook material such as a Library of Things.
28 votes -
Improve Visual UI of Leap screens
Many screens in Leap are awash with 1px borders, which make it difficult to visually distinguish different areas of the system because of the "noise".
While there are lots of ares for UI improvement across Leap, this one might be an easy win, as shown in the side by side screenshots.
9 votes -
Block non-owning libraries from waiving fines
It'd be nice if fines could be ineligible for being waived by staff from any library other than the owning library. In our consortia staff can waive any fine regardless of how much it is and what library it's from, this also goes for lost and damaged items on a patron's card. This can lead to staff just waiving fines that they shouldn't be waiving, or accidentally paying out lost/damaged items for another library, which we aren't supposed to do. Similar to how staff from other libraries can't update item details like call number, etc. for an item that doesn't…
5 votes -
Patron Import Process (LEAP) adding Polaris Username field
Adding the ability to add / update the Polaris username field as an alternative barcode for students/patrons would be hugely beneficial in the import process. This would allow us to have a student ID as a barcode and a former library barcode for patrons to use at the expresscheck.
11 votes -
Allow libraries to reset staff accounts that are locked out
There are a few scenarios where staff don't remember their exact password and get themselves locked out of LEAP: they are adjunct staff who work infrequently, they have just returned from a long vacation, or simply have brain freeze. In these cases, they open a support ticket, and I would like to be able to reset their account so that they can log in immediately, the same way I can now clear an object lock on an item that someone needs to use. Thanks for considering!
8 votes -
Hold History report where you could enter a Bibliographic Record ID
If Simply Reports had a Hold History report, where you could enter a Bibliographic Record ID and then see the history of hold requests created for that bibliographic record -- it would be most helpful when trying to see why an item wasn't automatically renewed, or was blocked from renewing.
12 votes -
Polaris ExpressCheck Auto-Renew
When a patron accidentally scans an item twice at the ExpressCheck, it performs an auto-renew. It would be nice to have an alert stating it's a duplicate checkout or something that prevents it from using a renewal.
6 votes -
Enable Add from file to bib and item record sets in Polaris client
Polaris client allows staff to populate a patron record set from an xlsx or csv on the local machine. Please enable this capability for item and bib record sets as well.
10 votes -
Allow library to choose which "unexpected" item statuses will prevent checkouts
If staff attempt to check out an item with an "unexpected" status, such as Withdrawn, Unavailable, or Missing the checkout fails, with an error message "unexpected item status." Staff must check the item in to change its status to Available, and then check it out. This breaks the flow of the checkout transactions and causes a delay for the patron. It would be very helpful if we could specify in System Administration which statuses cause a complete failure of the checkout (the current rule for all of these statuses), which cause a warning message that staff can override, and which…
20 votes -
Improve Leap quick search for complex patron names
The Leap quick search could do a better job of searching Hispanic names. Often, patrons consider their first two names as given names, not as first and middle, which makes it difficult to search for them when they come in without their cards. For example, if I search for Luis Miguel Paco Sanchez using all four names, LEAP finds the patron. If I search for Luis Paco Sanchez or Luis + either last name individually, LEAP will not find the patron. If I search for Miguel Paco Sanchez, LEAP finds the patron. In this example, Luis Miguel is the first…
10 votes -
SIP2 support for checking in lost items via sorter
Support should be included so that when lost items are checking via automated materials handlers, they should be checked in and processed - bill waived and item status updated appropriately.
24 votes -
Add series info when linking
Currently, if I want to add series information for a book in the item record when I link it, I would need to put it in the volume field. It'd be nice if there was an easy way to indicate if a book is part of a series and where it falls in the series without it creating a super long call number. Series info isn't standardized when it comes from publishers and isn't always included in the MARC record. This does make a difference for my patrons to know if a book is part of a series and would…
19 votes -
Include Call Number Field in SIP Item Information Response (18) Message
No that we have migrated from Sierra to Polaris, the call number field is not included in the SIP response when using an inventory wand. At this point we only see the barcode and title of an item, which makes it more difficult to find identified items.
8 votes -
Ability to share saved reports in Simply Reports
We would like to be able to share the reports we save in My Reports in Simply Reports. That way multiple people have the ability to run a report with the exact same parameters without having to share the very long list of parameters.
18 votes -
Display latest additions to record sets at the top of the record set
We create large weeding record sets by pulling items from the shelves then scanning them into the record set. Additions to the set are always shown at the bottom of the list. This means the user needs to keep scrolling to the end of the list to be assured their scanned item did save to the list and if they want to query last scanned items.
This request is simply to change the order in which the set is displayed on screen, with most recent additions added at the top of the list.
25 votes -
When logging into Leap make the focus on the Continue button
When you are logging into Leap on a machine where you've already logged in, a cookie is set that pre-fills the Branch and workstation. However, you canNOT simply hit enter to continue through this screen because the focus is on the workstation drop down.
This is a request to make it focus on the Continue button when you've already logged in on this browser to make the login process more seamless.
9 votes -
Bib-Level Multiple Holds
This is somewhat of an add-on to other improvement requests to the multiple holds feature. We would like to have an option for bib-level multiple holds. We have noticed that when teachers or book club leaders are placing the multiple holds and assigned to an item-level hold, they might get routed to a member library that doesn't frequently check their requests. This is absolutely a training issue, but we do see this a lot with our K-12 school libraries. We would like to see an option to put them in the queue as a bib-level hold where they will get…
5 votes -
Option to suppress more fields in patron registration
For our system, having both an expiration date and an address check date is redundant, and staff constantly fail to update the address check date to match the expiration date. I'd like to have the ability to suppress the address check date as well as other fields, such as street address lines 1 and 2.
22 votes -
Bibliographic consistency check when editing bibs
In cleaning up bibliographic data after years of laissez faire cataloguing practice, we have run into a consistent stumbling block that requires us to backtrack. Certain bytes, especially in the 007 and 008 fields appear to require consistency across them to properly read at an item level (we became aware of this when getting red toasts scanning items for a weeding record set, that appeared initially to be in the inclusion criteria).
By way of example: If you input in 007 an 01 byte of 'd - Videodisc', than the 04 byte would have to be 'g' 'h' 's' or…
12 votes
- Don't see your idea?