67 results found
-
Improve Authority Records Search with a “Return to Results”
Current user experience shows a gap in the Authority Records search flow. After running an authority search in Leap and opening an individual record, users are unable to return to the original results list. The only available option is to close the record, which also closes the search, forcing users to re‑enter and re‑run the query. This creates unnecessary repetition and slows cataloging work.
Proposed Enhancement (User‑Journey View):
Add a “Results” button to Authority Record views—mirroring what already exists in Bibliographic Records.
This allows catalogers to:Move seamlessly between multiple authority records that appear in a single search (for example,…
10 votes -
Polaris 8.1 - Allow for alphabetizing checkout screen in Leap
Please allow the checkout screen in Leap to be sorted/alphabetized by clicking any of the header columns, Title in particular. This is currently something that can be done in the Polaris client, and is useful for library staff when checking out large amounts of books to patrons who would like an alphabetized list of what they've just checked out. The columns in Leap appear to be clickable for sorting, but they currently are not.
27 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.
30 votes -
Polaris 8.1 - Leap Find Tool Window Expansion
It would be nice if the Leap Find Tool window could be enlarged to full screen.
43 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.
57 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 - Add a 4K Disc icon following the 007/04 format update
Adding a 4K disc icon to the discovery layer to distinguish a 4K disc from a Blu-ray disc would be helpful to patrons.
3 votes -
Polaris 8.1 - Leap Search Filter Returning to Default Search After Return to Search Results
If you have a search filter saved as a default search (such as assigned branch saved, for example), but temporarily remove it for a search, then open a bib/item record, then go back to the search results, LEAP will go back to your default search with the filter applied instead of the one you just did with the filter removed. This doesn't appear to happen the other way around. If you don't have a filter saved as your default search, but apply one for a search and then go back to search results, your filter will still be present. Is…
6 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).
31 votes -
Polaris 8.0 - Auto assign Patron Code based on age
In our system we have different Patron Codes for different ages. This allows us to differentiate services in the library to patrons of different ages. Occasionally, during the registration process (we exclusively use Leap) staff will forget to assign the correct Patron Code based on the new patron's age. If the system was able to auto-assign Patron Codes based on the inputted Birthdate, it would greatly reduce human error.
3 votesHi Aaron, the patron aging functionality included in Polaris 8.0 will allow you to automatically assign patron codes based on age.
-
Polaris 8.1 - 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.
24 votes -
Polaris 8.1 - 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 -
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.1 - Add notes field to Polaris Staff Accounts
We occasionally need to document the use and purpose of special staff accounts. Mostly we do this to make sure they don't accidentally get deleted.
Historically we did this by using the email address field on the staff account. Now in PolarisAdmin (Web) it enforces email address formatting rules in that field so we can no longer use that field.
This was always a hacky work around. It would be better to have a notes field on polaris user staff accounts like patrons do. It should be up front and in your face though and not hidden behind menus. Again…
18 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 -
Polaris 8.1 - 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…
134 votes -
Polaris 8.1 - 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 -
Polaris 7.8 - Bib Record Links in LEAP
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.
23 votes -
Polaris 7.8 - Updated notification status descriptions
Expand NotificationStatusID list/table to include TXT Sent and TXT Failed, plus any additional like TXT Failed - bad phone number
5 votes -
Polaris 8.1 - 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.
47 votes
- Don't see your idea?