68 results found
-
Powerpac in web PolarisAdmin - Individual collapse/expand settings for web parts
Currently there is a universal expanded/collapsed setting for the web parts. Providing individual settings would ensure patrons can immediatley view contents for key information.
E.g., Closure Notices and special events might be expanded by default as they include timely information while the other web parts (What's my PIN?, Add/edit Username, Suggest a Purchase) might be collapsed by default.
1 vote -
Leap: Allow logging in to other branches.
Currently, you can only log in to Leap using your workstation's assigned branch.
In the desktop client, you can use a workstation to log in to any branch.
Choosing a workstation in Leap that doesn't match your computer's system name breaks RFID functionality, as well as breaks reporting by workstation, and is not a workable solution.
This is impairing our ability to make a full move to Leap, and is one of the things that feels like a huge step backwards from the desktop staff client.
7 votes -
Web System Admin "return to results" from a staff or workstation workform.
The new Web version of System Administration is great, but I was sad to learn when upgrading from Polaris 7.7 to 8.0 that the search filter box for Workstations and Staff Users is no longer "sticky". In 7.7, I could enter a search for one of our Branches, click on a workstation, edit it, close it, and return to my filtered-by-branch search. Now, when you leave a workform, you return back to the full workstation list. Same for staff members. I'd like a button similar to the Leap "return to results" button in the workstation and staff member modules of…
7 votes -
Add PAPI method to GET picklist
Please consider adding a GET PAPI method to retrieve the picklist. While it’s usually convenient to obtain the picklist from the client/Leap, having a direct API option would enable custom workflows and more flexibility for libraries.
3 votes -
Powerpac in web PolarisAdmin - Include assign/remove button in Web part editor
In the web PolarisAdmin, provide a button in "Dashboards: Web part editor: User defined" to assign/remove the web part directly to web pages.
Subsequent idea: Provide an option to assign/remove a web part to all web pages.
Subsequent idea: Provide an option to mark web pages as favorites or frequently used so we can quickly add/remove the web part to a set of web pages. E.g., Apply the updated Closure Notice to default.aspx, login.aspx, patronaccount/default.aspx, patronaccount/itemsout.aspx, etc.Idea Value
Offering this button would streamline the process of adding/updating the web part and immediately assigning/removing the part to its relevant pages.…2 votes -
PowerPAC editing
Allow PowerPAC to lock independently of the other Polaris Admin features (client and web PolarisAdmin).
PowerPAC editing is locked when another SysAdmin is using the Administration Explorer. My primary responsibilities in the client are to update the PowerPAC, especially notes for upcoming library closures (holidays, staff development day).
Idea value
Provides uninterrupted workflow for primary SysAdmin to continue working when the web services focused SysAdmin needs to update the PowerPAC dashboard elements/layout.1 vote -
POST and DELETE methods for Record Sets
Currently with PAPI there is the ability to GET the contents of a Record Set and PUT additional records into Record Sets. We would love the Record Set API to be fully built out with POST methods (to create new Record Sets) and a DELETE method (to delete an existing Record Set).
4 votes -
Configure Notification Options Based on Patron Attributes
Currently, notifications in Polaris can only be filtered by branch. For example, one branch can enable specific notifications and another can disable them. We would love the ability to apply more granular filtering to determine which patrons receive certain notifications.
A workflow for us is billing notifications. Our library policy exempts certain patrons from billing based on their Patron Code. Because Polaris does not currently allow notifications to be filtered by Patron Code, we must manually work around the existing workflow to align with our policy.
We would love the ability, within SA, to filter notifications by patron attributes such…4 votes -
SQL Changes in Polaris System Admin
I know that it is planned to be able to run SQL jobs in the Web Based System Admin but that you won't be able to make changes from there, only to view data etc. I would love to be able to make changes through SQL in the System Admin and to have it be permission based.
13 votes -
Add PAPI method to merge bibliographic records
Adding this to PAPI would allow this process to be performed without SQL access and also fully leverage all of the existing Polaris business logic. It would also allow hosted customers to utilize the functionality.
11 votes -
Edit Items via API
Polaris APIs provide the ability to edit both Bibliographic records and Patron records via API. This is very useful for internal processes as well as third party processing.
5 votes -
Hide staff username or allow preferred name display for Leap
Staff have expressed concern that their Polaris username appears in the upper-right corner of Leap, making their last name visible to customers when screens are shared. They would prefer the option to hide or anonymize the display (e.g., first name only). While the username also appears in the Polaris client, it is less prominent and therefore raises fewer concerns.
7 votes -
Include DELETE method for Patron Blocks
As of Polaris 8.0, PAPI supports creating new Patron Blocks but does not provide a method to delete them. For internal automation and vendor workflows, the ability to programmatically remove Patron Blocks is essential. Adding a delete method will reduce the need for manual intervention.
9 votes -
Create custom circulation statuses
To be able to create customized circulation statuses that work for our system versus using the only given statuses. For example, the ability to create various Withdrawn - Leased, Condition, Relevancy. This would then offer additional feedback for staff when stats are ran to determine why materials were withdrawn versus they were.
13 votesFor the withdrawn example, does this really require custom circulation statuses? Or just a way to indicate/query the reason an item was withdrawn?
The reason Polaris has traditional restricted circulation statuses is because of our automated processes around certain statuses. Using the withdrawn example, our automatic Lost/Missing to Withdrawn processing would not know about custom statuses or which one to use.
If we reworked this enhancement as needing to be able to track/report on withdrawn reasons, we could plan for that within the automated processes.
-
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.
6 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
•…2 votes -
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.
3 votes -
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…
40 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…
19 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
- Don't see your idea?