67 results found
-
Comprehensive Audit Trail for System Administration Changes
Implement a detailed and accessible audit log for all configuration changes made within the Polaris ILS System Administration (SA) and "adjacent" modules.
Description of the Problem
The Polaris ILS lacks a granular, searchable audit trail for System Administration changes. This makes it difficult to determine who made a specific change, when it occurred, and what the previous setting was. This ambiguity hinders troubleshooting when a configuration error occurs, complicates training, and reduces accountability.
Proposed Solution
A comprehensive, transaction-based audit log that automatically records the following data for every saved change in the SA module:
Timestamp: The precise date and time…
36 votes -
Service Name Logging in PatronValidate API
This proposal outlines an extension to the Patron Validation API to include an optional serviceName parameter. When provided, this value will be recorded in the Integrated Library System (ILS) transaction log, allowing us to track which service initiates each patron validation request.
Currently, the ILS transaction log records patron validations without capturing which service initiated the request. This lack of context makes it difficult to analyze traffic from third-party services (e.g., OverDrive, Hoopla) or internal applications, troubleshoot validation spikes, and make informed decisions about service contracts and resource allocation.
The proposed solution is to modify the Patron Validation API to…
18 votes -
Back to Search from Send to Record Set
When you create a search to then send to record set we would like option to go Back to Search. Sometimes we only grab part of the initial results into a record set and we would like to go back to the larger list to grab additional items to add into a completely different record set.
Some lists are too long or we want them split up for multiple staff to manage and having these results in different record sets helps with that.
25 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…
55 votes -
Hide/Supress Material Type and/or Circulation Status in staff view
There are times when Material Types and Circulation Statuses are not used by either the entire system or specific libraries. This can cause staff errors and general confusion when there are options available that are outside of the libraries workflow. We would love to see SA options that would be able to hide/suppress both Material Types and Circulation Statuses in the staff client/Leap.
4 votes -
Include Call Number Field in SIP Item Information Response (18) Message
No that we have migrated from Sierra to Polaris, the call number field is not included in the SIP response when using an inventory wand. At this point we only see the barcode and title of an item, which makes it more difficult to find identified items.
11 votes -
Allow favicon to be set for leap as a staff visual cue
You can set the title bar color and the login message for Leap. However, it would also be nice to have the option to set the favicon so when you have a test, development, and production server open, you could use a favicon to more quickly distinguish between them in your open tabs.
10 votes -
Patron Import Process (LEAP) adding Polaris Username field
Adding the ability to add / update the Polaris username field as an alternative barcode for students/patrons would be hugely beneficial in the import process. This would allow us to have a student ID as a barcode and a former library barcode for patrons to use at the expresscheck.
11 votes -
When logging into Leap make the focus on the Continue button
When you are logging into Leap on a machine where you've already logged in, a cookie is set that pre-fills the Branch and workstation. However, you canNOT simply hit enter to continue through this screen because the focus is on the workstation drop down.
This is a request to make it focus on the Continue button when you've already logged in on this browser to make the login process more seamless.
9 votes -
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…
18 votes -
Allow 3M SIP 2 Port for the branch to be viewed
Information about which 3M SIP port that is tied to each branch is only available if you have SQL. This request is to allow that port to be viewed in Sys Admin. Even if it was just part of a a branch's properties that would be fine.
It could also be in a table view format (like Fine Codes, etc.) but it would just be nice to see that information somewhere outside of SQL.
7 votes -
PII Management Options
Although there are current options for purging patron IDs from circ transactions, and deleting account transactions, there are some gaps with removing PII (personally identifiable information) we'd like to see addressed.
We'd like the option to purge patron IDs from non-circ transactions (incl. patron account history and record history). We'd also like the option to manage patron details on any other tables where history may be maintained after a patron record is deleted (e.g. Notification History, DeletedPatrons, DeletedPatronAccounts, kwmssg, and offline and InnReach process tables). It would also be ideal to have a plan for removing any CNV tables (from…
15 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 -
Vendor-Profile SIP2 Due Date Formatting
In the i-tiva 3.0 dial-in process, there are menu navigation issues caused by a SIP2 Due Date (AH field) formatting issue. These issues cause the dial-in process to fail.
In SIP2 message 18 (Item Information), Polaris is currently returning the Due Date in the following format:
DD/MM/YYYY HH:MM:SS
Because the SIP2 standard does not define or enforce a required date format, i-tiva relies on vendor-compatible parsing. i-tiva has confirmed that this specific format is not parsed correctly and results in call-flow failures.
i-tiva supports the following date formats, any of which would resolve the issue:
• DD/MM/YYYY
• D-M-YY
•…1 vote -
Ability to Suppress Custom Data Fields
In Polaris System Administration, there is existing functionality to suppress UDF 1–5 in the Web App (Leap), which allow the fields to be written to, but prevents staff from viewing or editing them.
We would like to request that the same suppression functionality be extended to Patron Custom Data Fields. Currently, the only available option is to enable these fields, which simply turns them on or off. This lacks the flexibility we need.Adding suppression capability to Patron Custom Data Fields would greatly enhance our ability to manage sensitive or system-used data more effectively.
2 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 -
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 -
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 -
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.
10 votes -
Integrate cloudLibrary with both Polaris and BiblioCommons
We recently began integrating Polaris with cloudLibrary in an effort to keep our collection more up-to-date and have patrons' Polaris accounts reflect their cloudLibrary borrowing. Unfortunately, our results have been inconsistent because while the Polaris/cloudLibrary connection works, there is not a fluid integration between Polaris, cloudLibrary, and BiblioCommons, where patrons are also able to check out cloudLibrary titles. We would like to see full integration between all three vendors so that transactions on any platform are properly communicated to the others.
3 votes
- Don't see your idea?