603 results found
-
Activate arrows on a keyboard
Whenever there are menus like "Yes", "no", "cancel", it would be nice to use arrows and enter buttons on a keyboard and not a mouse. Right now arrows don't work.
10 votesJust a quick note that because these are button elements, you can tab or shift+tab to move forwards and backwards between the options.
-
Show workstation and staff information for posted patron notices
When some notice types are posted, they show up in the item record history. But not all notices show up there, for example, printed hold notices do not show up there. It is also difficult, for example, if you want to find out who printed a fine notice to be able to locate that information because it isn't always tied to an item record.
This request is to add to the notice history information on the user and workstation that posted the notices to the database. There is very miniscule information in the notice history already.
This additional information would…
10 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.
10 votes -
Autowaive Fine for Returned Withdrawn Items
We would like, when items with a Withdrawn status are returned by patrons in a good enough condition to still circulate, for the replacement fees associated with the item to auto-waive in the same way that items with a Lost status can auto-waive. This would prevent confusion at the circulation desk and streamline the check-in process.
10 votes -
Add 'Hold Activated/Created" to item history
It would be useful to have in the item history when a hold was activated. I had an instance where an item was put on hold for the wrong account, and it would have been useful to see who had placed the hold or where it had been added. I figure you can see this from the hold record, but the staff member who had received the accidental holds cancelled them before we got a chance to look at it.
10 votes -
Generate patron barcodes outside of self-registration
Polaris should be able to generate barcodes outside of self-registration. Sometimes you want to generate barcodes without relying on a physical card that already has a barcode printed on it. Polaris already can do this because it does it for self-registration cards. So it should be able to occur on demand.
10 votes -
Patron Barcode as Subtext in Current/Recent menu (last4) in Leap
We have found it hard to work with the Current and Recent workfrom menu when working with lots of Patron Records, or more commonly, Duplicate Patron Records.
Names work, but when names are similar or the same it can be hard to figure out which records are which.
Sometimes staff are working with Barcodes as a reference vs. patron names.It would be nice to have a subtext under the Patrons name in the Current and Recent workform list that shows the last 4 digits or the full barcode underneath the patron name.
I have 2 images attached that demonstrates…
10 votes -
Update Bulk Waive schedule in LEAP - add reoccurring
Provide an option to schedule bulk fee waive in records on a reoccurring basis, such as daily, monthly, or other specified intervals. At the moment you can only select one date and run it once.
10 votes -
Include Active Directory in web-based System Administration
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.
10 votes -
Include 024 tags in ISBN index
Please expand the search functionality to include searching and pulling results for both the 024#a MARC tag, as well as 020#a
Functionally this will improve searches as results will include hits on an ISBN whether it's in 020 or 024
10 votes -
Clearer messaging when an invalid barcode is used in a password reset
A patron was using their former barcode to try to do a password reset, and before we realized what the issue was, the system told them they 'had no email address' associated with that account. It would be more helpful if the system told them the barcode was invalid or, even better, that they were using an old barcode.
10 votes -
Ability to create reports with charts and graphs
I came across this report using a bar chart to reflect the Total Number of Items Added. Our staff would love the ability to create statistical reports and display them as bar, line, and or pie charts.
10 votes -
Include patron preferences such as billing notifications in PAPI patron update/create
The Jacksonville Public Library leverages the Polaris API to manage student records. Currently we have to take an extra step in the LEAP UI to set the communication preferences. We don't bill students or send their accounts to collections, so we have to do a bulk update of all the records with the UI after already touching every record with the API. This is cumbersome because there are over 100,000 student records that need to be updated. Most updates are smaller, but at the start of the school year we do a full refresh.
We would like to be able…
10 votes -
Improve Hold Duplicate Detection
Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.
This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like…
10 votes -
Allow volume level AND item level requests
We were told that in order to activate volume level requests in the PAC and in Vega, we would have to turn off the ability for item level requests to be placed, since it's an either or setting (see attached). However, we need to be able to offer our patrons both options. In the case of volume level requests, we can't have patrons getting a random volume that they might not even want when they place a title level hold. Since we also have patrons that use item level requesting, we can't just turn that off in favor of volume…
10 votes -
Fund Hierarchy Report
Currently, the fund hierarchy report organizes at the Organization level by Org ID. This means that as new organization levels are added they drop to the bottom of the list, and I'm often looking at this from an alphabetical perspective. It would be helpful to have the option to organize the output alphabetically instead.
10 votes -
Block holds creation when all items in a suppressed circulation status
There should be an option to block patrons from placing holds on items if there is only one owning library and the circulation status of the item is listed as missing or in storage. While in storage items should be visible to patrons in the OPAC since sometimes that item can be taken out of storage if a patron wants it, they shouldn't be able to place a hold if there's only one owning library and their only copy is listed as in storage. Like withdrawn items, missing items simply shouldn't show up at all for patrons as an option.
10 votes -
Circulation by Loaning Branch at the Bib level
Currently the preview screen in Client and the Bibliographic level statistics screen in Leap provides circulation by Owning Branch. It would be more helpful in determining where a title is popular (and more useful for acquisitions) to have this data based on Loaning Branch. Use on a specific copy would still be accessible on the item record. If circulation by loaning branch can't be provided there, having it accessible elsewhere from the Bib record would be great.
10 votes -
020 Field Character Limit Should Exceed 50 Characters & Not Reject Placing an Item On Order
We are having manually placed orders rejected because the 020 field for large print books sometimes exceeds the 50 character limit. Polaris/Leap will accept 020 fields that are up to 49 characters, but not for OCLC MARC records that have extended to 54 characters. This happens whether we are attaching to an existing record in Polaris/Leap or for a new one imported from OCLC/Connexion. It seems completely arbitrary that 49 characters are accepted, but 54 characters -- just a few over the limit -- are not. Thanks for looking into & considering this request.
9 votes -
Leap: include examples for pub pattern creation
Staff find the examples provided in the client helpful when creating a new pub pattern. It would be great to see the same in Leap.
9 votes
- Don't see your idea?