74 results found
-
Leap Login Setting: Set Default Branch to Workstation's Assigned Branch
Requested Change:
We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection. We would like it to default to the workstation's branch.Desktop Client:
When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.Leap:
When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.Why:
At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location.…2 votes -
De-index or filter deleted staff accounts in web system admin
In the staff client, it's possible to delete a staff user account in system administration and the account will no longer show up linked from associated records or in search results. In the Web version of System Administration (as of at least 8.0), deleted staff users continue to show up, but the username is appended with "(Deleted)." User accounts in Web SysAd can be sorted based on whether they are Enabled or not, but the search and filtering options don't allow for filtering out Deleted staff from searches. We have been on Polaris since 1998, so our Deleted staff far…
7 votes -
Add Elavon integration as a vendor for ExpressCheck payment gateway
We would like to see Elavon added as an vendor for ExpressCheck payments. Currently, because it is not an available vendor, we cannot customize our fees on our self-check machines.
1 vote -
Add You Saved to PAPI patronBasicData
We'd like to be able to pull the patron YTD and Lifetime You Saved amounts in a patronBasicData call.
18 votes -
Enhance PAPI HoldRequestGetList to Return and Filter by Pickup Area
Enhance the Polaris API HoldRequestGetList endpoint to include the assigned PickupAreaID and PickupArea for each hold, and add support for an optional pickuareaid query parameter. Polaris introduced Pickup Areas in version 7.5 to let libraries define multiple pickup points inside a single branch, such as lockers, curbside locations, drive‑through windows, or other specialized service points. Pickup areas were created to avoid the need to create extra branches and to support the increasing use of lockers and flexible pickup workflows. However, HoldRequestGetList does not return the Pickup Area, which means an integration cannot determine where a hold is supposed to be…
4 votes -
Improve Toast management
Toast messages can sometimes be difficult to catch if they fade too quickly or can get in the way if they accumulate on the screen. It would help if the toast appeared, then was reduced to a smaller indicator that could be cleared. Aso allow staff to open the history of toasts for their current session, so they can refind a message once they have finished what they were doing.
7 votes -
delete all permission groups from staff account
It would be helpful to be able to select all permission groups in a staff account and delete from PolarisSA. This exists in the client. When a staff member changes positions, we copy the new set of permission groups from an existing account, but first we delete all their existing permissions in case they have something they will no longer need. In PolarisSA, this requires deleting each permission group individually.
8 votes -
Include Hold Bulk Change in Background Processing
Polaris 8.1 introduced Bulk Changs within the Request Manager. However, when a bulk change is made, the only verification the user receives is a message that tells the user how many holds were changed. It would be beneficial (and would follow Polaris' bulk change practices) to include the results in the Background Processing function.
11 votes -
Add temporary shelf location to PAPI
BibHoldingsGet, SynchItemsByBibIDGet, and SynchItemByIDGet all return the shelf location of an item, but not the temporary shelf location.
4 votes -
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.
2 votes -
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.
9 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…
8 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 -
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
- Don't see your idea?