62 results found
-
Allow PolarisAdmin sidebar to be pinned
Unlike the Leap sidebars, you can NOT pin the PolarisAdmin sidebar, making it more difficult to move around the system versus the desktop SA.
10 votes -
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 -
Add Title & Suffix to PAPI PatronRegistrationCreate2 & Update2
It would be helpful to be able to create or update, via PAPI, patron registration records with the Title and Suffix fields populated. Currently, there is no way to ingest this information when using custom registration forms that utilize PAPI to create patron records.
2 votes -
Move the Leap quotes out of WebAdmin and into SA
The author quotes in Polaris Leap suddenly became a hot topic because of a Neil Gaiman quote within the list. While making some adjustments, it occurred to me that there are more possibilities for those Leap quotes and that they could be used to convey real information to the staff about things like upcoming Polaris upgrades, library events, and so on. At the very least, changing the quotes in WebAdmin is a bit of a pain because you have to change a quote and an author separately.
My idea is that the quotes should be added to SA, where they're…
51 votes -
Add patron blocked to AuthenticatePatron API endpoint
It would be helpful to have an indicator for if a patron has circulation blocks in the response of the AuthenticatePatron API endpoint. This would allow vendors and custom integrations to determine if a patron should be allowed access to a system based on if they are allowed to checkout items without having to do an additional API call.
5 votes -
Create a Back End Updating Feature
A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.
So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the…
16 votes -
Support for VMSS
Support for Virtual Machine Scale Set (VMSS) allows for automated OS upgrades and patching thus creating a more secure solution than a standalone VM.
2 votes -
Add "You Saved" Text to PAPI Checkout
When items are checked out through SIP2, Polaris includes the "You just saved __ by using the library" text in the response. However, this information is not available when using the ItemCheckout method through PAPI.
As we start moving vendors away from SIP2 and towards PAPI, we'd like to replicate the functionality of SIP2.
Thanks
13 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 -
Hide libraries and branches in Polaris System Administration
Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.
Just sitting there and doing nothing.
I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.
So add the ability to hide them instead.
That way, when a library leaves the system, you're not wading through the settings and…
28 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…
3 votes -
Additional UI Customization Options
Across our consortium, we have some library staff who exclusively use Leap, some who exclusively use the Remote Client, and some who use both depending on the task.
Currently, there is only one system-level setting responsible for the Visual Alert Configuration (top banner color) in Leap & the Remote Client. Unfortunately, this doesn’t work well given that Leap has a light font color and the Client has a dark font color across the top, so to achieve an ideal level of contrast for both versions simultaneously is impossible.
To improve accessibility for all users, regardless of the version of Polaris…
13 votes -
Include All Patron Duplicate Detection Settings in the API
Currently the API only performs basic duplicate detection (name, birthdate, barcode, username, and optionally the name on ID) when a patron record is created using the PatronRegistrationCreate call. It does not apply other optional settings - email, phone 1, or the UDFs - these only get applied directly in Polaris or the PAC. This idea is for including these optional settings in the API logic.
13 votes -
Assign users to manage their branch's float table.
Allow permissions to modify the branch floating table so that each branch can maintain their own float in counts for their collections and/or media types.
2 votes -
Create tool to generate SSO settings files
I realize this is niche, but if you go to set up SSO in your environment, heaven help you. My crew just got through a week of getting things set up. There were 3 of my employees and at least 1 Innovative support staff and 1 Innovative dev involved all week. I can't imagine the amount of $$$ that was burned in hourly staff time getting it going. And of course the good news is that an upgrade or server move could break it all again! Some of the documentation is wrong and some of the transcribing of the data…
6 votes -
Include an "X"/close button on workform tracker records
Sometimes I have a lot of records open in the workform tracker, and it's a pain to have to go into each to close it. It would be useful to have a button I could quickly click to close them instead.
In cases where a record has been modified it should generate a prompt about saving changes, and show you the record again in this case so it's clear what's being saved.
19 votes -
Ability to move rows in the Item Statistical Class Code policy table
It would be helpful if we could move rows up and down in the item statistical class code policy table. We have librarians transferring items between branches that have statistical class codes in them. The codes will automatically change to a different code when assigned to the new branch because the position of the code in the policy table does not align. The cataloger must remember to update that field to the correct code.
This would be beneficial to our librarians, simplify their workflow, and prevent errors.
12 votes -
Increase functionality of API with Overdrive
We would like to see additional information and functions available in the Polaris Client or LEAP so that staff have more resources and information to support customers with questions about online resources.
For example, library staff would benefit from seeing real-time hold information in Polaris about items on Overdrive or Hoopla. Currently, Polaris shows an asterix (*) under holds. Library staff need to either go to the PAC or Overdrive to provide customers with this information. It would help library staff to have information available in one place rather than requiring staff to go to multiple sources to answer a…
23 votes -
Add the ability to clone an existing branch when creating a new branch
We would like to be able to copy an existing branch when creating a new branch, since often our additions are branch locations of an existing library that will have almost the same exact settings.
27 votes -
(SMS - Cirriusimpact/third-party SMS) Flag patron account within Polaris when patron "opts out"
Reviewing the process of integrating Cirriusimpact at our library, we've encountered a notable issue: patrons opting out of text messaging and staff needing to adjust their notifications accordingly. Currently, we're relying on CGS to send daily email alerts when someone opts out, but it would be more convenient to add a non-blocking note to the Polaris account visible to all staff. This would ensure everyone is aware of a patron's preference change and simplify the search for patrons with similar notification settings.
4 votes
- Don't see your idea?