55 results found
-
Expose web-based System Administration APIs
For larger library systems that need to continually create new staff members, being able to access the APIs would be a big time saver. That would allow, among other things, to automate that task.
1 vote -
A way to customize pop up notices
Various popups appear in Polaris via the client or Leap. Some are pretty clear in what the reminder or error message is about and some popups are not.
I am requesting a way to customize the text and title (Leap only has this visible) to make it more clear for our staff to understand either the popup reminder or the popup error with a little more explanation.
Example for Popup Reminder: Via the client we have a popup reminder about "reminder notices option is email. Do you want to continue?". This occurs when we leave the email field blank per…
8 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.
7 votes -
Add Postal Code table to PAPI
It would be nice for third party vendors and developers to have access to the Postal Code table via PAPI. Something similar to the OrganizationsGet method.
4 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.
6 votes -
Ability for PAPI to write to patron Custom Data Fields
It would be helpful if the PatronRegistrationCreate endpoint was able to write to the Patron Custom Data Fields.
4 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.
12 votes -
Add additional filters to PolarisAdmin (web SA)
In PolarisAdmin, it would be great to have a few additional filters other than the text box filter.
- Show non-default (would show any setting that wasn't at its default value)
- Show system/library/branch level (one for each, to show settings that were set at specific levels within Polaris SA)
This would allow for quick scans for changed settings that might be causing issues or problems. Especially in places where there are a wide range of settings that are largely kept at their default values (I'm looking at you Self-Check Unit Parameters).
I'm attaching a screenshot of another software I use that…
11 votes -
Allow the option to use OAuth to authenticate SMTP
Currently to use SMTP the account has to support basic authentication which is not secure and is being deprecated by Microsoft for Azure accounts. In the next few months, Microsoft will be enforcing MFA on Azure accounts in phases and the only way around that for things like SMTP is to use OAuth. Since the current version does not allow OAuth authentication for SMTP, this will cause notification services that use email to stop functioning.
Allowing the option to use OAuth to authenticate SMTP would resolve this issue and allow users with Microsoft Tenants to continue using notification services.
1 vote -
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.
8 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…
13 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…
31 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.
4 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…
12 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
11 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.
13 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…
25 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
- Don't see your idea?