22 results found
-
Polaris 8.1 - Leap Find Tool Window Expansion
It would be nice if the Leap Find Tool window could be enlarged to full screen.
39 votes -
Polaris 8.1 - New tabs from find tool in Leap
One piece of feedback we've gotten is that staff members who are used to the client miss the ability to open and rearrange a bunch of windows from the find tools (for side-by-side comparison, or just for managing workflows). We're wondering if this experience could be recreated by allowing the option to open multiple results in new tabs from the find tool in Leap.
23 votes -
Polaris 8.1 - Return to where you were in your record set list after closing an item record from the record set
When I am working in a long record set and open an item record and then close it again, it returns me to the top of the record set. I would really like it to return me to where I was in the list to more easily continue my work.
52 votes -
Polaris 8.0 - Trim Whitespace on Username and External ID Fields in /PolarisAdmin (Web Admin)
We would like to enhance /PolarisAdmin (Web Admin) so that leading and trailing spaces are automatically trimmed from the Username and External ID fields upon entry.
Problem Statement
Currently, if administrators accidentally enter a username or external ID with a leading or trailing space, it is saved as entered. This creates login and authentication issues for end users, since the system considers the space a part of the credential. This can be difficult to troubleshoot and frustrating for both administrators and end users.This is especially likely to happen when copying/pasting from certain user management platforms.
Proposed Enhancement
Automatically strip…14 votes -
Polaris 8.1 - Stacked Sorting
We would like the ability to do stacked sorting in searches and record sets. This would allow the user to sort by one aspect and then another with it stacked (eg. sorting by pub date and then call number, so you see items within a call number in pub date order). In both searches and record sets, it only seems to sort by the current choice, meaning the way it's sorted within that one type is random (or alphabetical by title, which isn’t always the most useful).
30 votes -
Add Library Level to Hold Pickup Limit
Currently, a library may limit an item to be holdable for pickup at a single branch location. This setting allows the item to be limited to pick up at the item's assigned branch only. While this feature may work for single-branch libraries, it does not function in a practical way for multi-branch libraries. Expanding this feature to have a library-level option would increase the usability of this setting.
Example 1: Library A has 3 branches. They want to make their mobile hotspots holdable for pickup at any of their 3 branches. They do not want their hotspots to be placed…
39 votes -
Patron Notes field - pop-up alert on check out
It would be useful to have a pop-up alert for notes to patrons that are important, but not so urgent we need to block their record. This would mean that when staff scanned their card at check out, there would be an obvious pop-up to alert them of a message, rather than relying on them noticing a colour change to the Notes link.
20 votes -
Polaris 8.0 - Give staff ID of duplicate user when staff account username or external ID matches one in the system
When you are adding an account or changing information on an account and the system detects a duplicate, it won't let you proceed. However, it won't give you any information on the conflict account.
It would be super helpful to have the conflicting ID shown in the popup message to make tracking down the other account easier.
Especially if the dup happens to be because of something weird like a space or non-printable character.
This seems to happen more as locations move to SSO and fill in their external ID field.
6 votes -
Polaris 8.0 - Have PolarisAdmin follow colors and client alert boxes to distinguish system
When changing settings, it is critical to make sure you're changing them in the right place.
The /PolarisAdmin should also pick up the color coding and client alerts. Currently, the /PolarisAdmin does NOT pickup the client color changes or wording, which means you need to do extra work to make sure you are changing the settings in the proper system.
3 votes -
The ability to check in multiple issues in Leap Serials
In Leap Serials, the ability to select multiple issues and then click check in is needed for large libraries to use Leap Serials, exclusively. The workflow of selecting each individual issue and then clicking check in is slow and tedious.
30 votes -
Support Custom TOMs / TOM Override
While there are many advantages to way that Polaris calculates TOMs, there are currently some significant limitations for differentiating between formats. 4K BluRays, Playaways/Yotos, and video game systems are all very difficult to distinguish from one another when using only the MARC fixed fields. Additionally, many libraries are expanding their collections with Libraries of Things that are usually coded as "Kit" or "Three Dimensional Object" rather than describing what it actually is. These bib TOMS are also now featured prominently in Vega Discover's rollups.
Over on the Sierra side, the options for bibliographic format can be customized. If a library…
130 votes -
Allow Username to begin with number
It seems unnecessary to force the Polaris Username field to begin with a letter. We would love for the Username field to have the ability to begin with any character.
5 votes -
Bulk update held until dates
The ability to bulk change Held Until dates would allow library staff to perform this task themselves in a timely manner, rather than having to submit a ticket to Innovative.
43 votes -
Polaris 8.0 - Auto update member code from Junior to Adult when they turn 18
Having member codes change automatically based off patron age, changing junior to adult when they turn 18.
52 votes -
Polaris 8.1 - Add ability to enter a reason when cancelling a hold
Currently, patrons receive a default email message when their hold is cancelled. It would be great for staff to have the ability to enter a reason or write a brief message letting the patron know why their hold was cancelled.
152 votes -
Polaris 8.0 - Dated patron notes
It would be very useful for patron notes to automatically include date and time - this would allow us to track "updates" to progressive situations with patrons that multiple staff are addressing.
102 votes -
Bulk Edit Patron/Material Type Loan Limits
Allow multiple selections of Organizations & Patron Codes to populate Material Type list (lower table) on the Patron / Material Type Loan Limit Blocks, Policy Table.
21 votes -
Bulk Change Pickup Location for Held Items
We often have branches close unexpectedly due to facilities issues, when this happens we need to move the Held items from that branch to another branch. Currently there is no way to bulk change the pickup location between branches. This function would be very helpful for us.
36 votes -
API to Update Bibliographic Records
I'm specifically looking for a great integration between the cataloging tool BTCat and Polaris.
Libraries use tools like BTCat and Skyriver to search for new bib records and update/edit existing records. After making changes, the records currently have to be exported from the cataloging software, then imported into Polaris. These tools have the ability to "push" records into other ILS systems, skipping the need for a manual export/import of records. Adding this functionality would aid libraries in transitioning away from the Polaris desktop client (as bibliographic editing in Leap is a tedious process, at best).
23 votesWe actually added an endpoint to support this integration in Polaris 7.6 (BibsPost). We've been working with BTCat to consume the endpoint in their application.
I'm going to set this to "Planned" for now because the integration is not live with BTCat yet. But the development piece required for Polaris has been done. Please let BTCat know you are interested!!
-
Web Admin - PAPI Key Management Permissions
With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).
We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in…
16 votesWe will be adding a permission to address the issue of users with general access being able to reach the PAPI keys. There are some other comments here that could be considered separate enhancements, so please open new ideas for changes beyond a PAPI Key Management permission.
- Don't see your idea?