613 results found
-
Show Due Date for ILLs in Request Manager
Our ILL clerk would like to be able to see the due date for ILLs from the request manager, so she can make sure that the dates have been added correctly to these items. She currently has to go into each item individually to make sure they were correct.
15 votes -
Ability to Export Individual Owned Record Sets
I had a coworker ask why she couldn't export her record set into excel to allow for more sortability. I was surprised she couldn't and began looking at documentation and noticed that there is that ability, but you have to change the owner of the record set to the branch or system level, which feels like an unnecessary step. I should be able to export a record set I am working on to Excel with my regular ownership without having the (slim) possibility of a coworker accidentally accessing and messing up anything.
15 votes -
Hoopla integration with Polaris
The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.
15 votes -
Auto suggest volumes while adding items to a bib record
When creating a new item record on a bib, it would be wonderful if while typing in the volume field, Leap automatically suggested volumes from other items attached to that particular bib. This would help ensure standardization of how the volume is entered on each item record (eg. V.1 vs V. 1 vs. V.01) while also allowing the libraries to add a new volume number for volumes 2, 3, etc. since it would suggest while typing rather than changing the volume field to be a drop down menu of pre-defined options.
15 votes -
Move Leap timeout setting to SA
We would like to be able to adjust the timeout in Leap after inactivity ourselves. Currently, we have to contact support to do this after each upgrade, since it resets itself. If the setting was in SA, we could reset it ourselves after each upgrade.
15 votes -
Reverting to what the bibliographic record (or any authority record for that matter) was when it was last saved
When you want to get rid of a bunch of edits, but only the ones made since the last save, it saves time to have just one button to click on. For example, when you want to validate juvenile headings, you need to take out |v Fiction for each heading. If they are all good, you want it back in each heading.
15 votes -
Select multiple items to delete
From the Leap Serials Check In screen, include the ability to select multiple dates for deletion.
15 votes -
bulk add "stat code"
Be able to bulk add stat codes. Currently we can only add at the branch level manually because the library and system level tables are too large. This requires a manual change or contracting Polaris every time we want to add stat codes for all locations.
15 votes -
Allow libraries to customize info displayed in Leap Patron Record header and properties
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…
15 votes -
Allow Google as a sign-in method for Staff Accounts
In addition to Single Sign-On (SSO) support for Microsoft Azure and ADFS, please consider support for Google Workspace. We recently migrated all of our email for our consortium (42 members) to Google and would greatly benefit from the ability to use the already signed-in information to authenticate into Leap. See screenshots for a design/concept mock-up.
15 votes -
LEAP: Allow sending items to an item record set from a patron record "Out / Renew" screen
LEAP: Allow sending items to an item record set from a patron record "Out / Renew" screen
15 votes -
API reading history sortable by title or last added
We have had multiple patron requests to be able to sort reading history delivered by API by latest added or by title. Currently reading history is displayed with the oldest first which results in a lot of scrolling by the user.
15 votes -
Add electronic signature option to online registration
We are interested in going paperless and no longer using registration cards but we would still like to collect patron signatures. Can Leap/Polaris allow for electronic signature collection?
15 votes -
Allow library to exclude certain material types from Claim Return function
Polaris' claim return function is great for locally-owned items but is problematic with INN-Reach. We are constantly reminding staff NOT to use Claim Return for INN-Reach items because it can break transaction links but they continue to do so. If system admin allowed us to exclude our INN-Reach and WorldCat material types from Claim Return and Claim Missing Part functions, it would reduce errors significantly.
15 votes -
Run date specific report on Patron activity (not last activity)
I would like to submit the idea that Polaris offers the ability to run a report based on patron activity dates, and not their LAST activity date.
Currently, we can only run a report using "Last Activity". This is not helpful if trying to determine how many patrons were active in a given period because if they have had activity after the specified period, they would no longer be counted in the report.
There is a canned report under System > statistical summary, but it only looks at borrows, and would not count ILS card activity such as from a…15 votes -
Reporting Groups for Collection Codes / Material Types (reporting only)
Add a reporting-only way to map Collection Codes and/or Material Types into any number of user-defined reporting groups, with many-to-many membership. Grouping logic should live in a maintained mapping table (not hardcoded in reports) so changes update all dependent reports automatically.
Problem
Only staff with database access can currently create sequel/SQL mapping tables (e.g., MapCollection, MapMaterialType) for flexible rollups. Others must regroup exports manually, which is inconsistent and fragile.
Provide a UI-managed “Reporting Groups” feature that acts like a built-in mapping/lookup table:
• Many-to-many: one code can belong to multiple groups; groups can contain multiple codes.
• Reporting-only: no impact…14 votes -
Leap: quickly copy line items
One impediment for our processing staff in moving to Leap is the lack of the ability to quickly copy a line item in Leap (here's the process in the client: https://documentation.iii.com/polaris/7.6/#PolarisStaffHelp/Acquisitions/PAorder/Copy_a_purchase_order_line_item.htm)
The same process in Leap involves several more steps:
1.Go back to the PO
2. click new line item
3.fill out line item details
4. click on segments
5. click new segment
6. fill out Collection Code and FundA quicker way to get through a PO would be if we could add the same segment to all of the line items at once, e.g click the check…
14 votes -
Add pickup area support to SimplyReports
You cannot output or filter on Hold Pickup Areas in SimplyReports. Not being able to report on them limits their usefulness for things like looking at which schools are busiest or which bookmobile stops are most active. The information is available in hold request data and in transaction details.
Although we can add it as a custom output that will only show the ID which is of limited value to staff.
14 votes -
Permission the volume field on item records
The volume field might seem straightforward, but when it's not standardized—or when anyone can input anything—it quickly becomes a source of frustration, especially with holds and sorting. Imagine a patron placing a hold on “Volume 2,” but one record says “v.2,” another says “Vol 2,” and another just “2”… chaos ensues.
Making that field permission-based could go a long way in preserving data consistency and reducing hold errors. It puts a bit more control in the hands of cataloging staff or system administrators
14 votes -
Cancel Holds in Bulk Based on Item Circ Status
We’d like the ability to “bulk” cancel holds for items by status (lost, missing, withdrawn, etc.) either by being able to view the circulation status in the patron holds view, or by having the ability to “bulk” cancel holds from a record set.
14 votes
- Don't see your idea?