76 results found
-
Patron Import Process (LEAP) leveraging patron templates
The new patron import process will be a major improvement for handling student data, but it still requires significant data formatting before uploading through LEAP. It would be incredibly helpful if libraries could create their own templates to define how data is mapped to specific CSV columns, including logic for assigning patron codes or populating fields like UDFs. This kind of flexibility would greatly reduce the staff time needed to prepare files for import.
4 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 -
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 -
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 -
More granular permissions for patron registration workform
We would like to be able to limit who can change the Expiration Date and Address Check Date in the patron registration workform. Off the two, Address Check Date is most important as this is what we use to make sure patrons are updating their information regularly.
These are configured in SA and are set system wide yet staff continue to change them.
If I remove the 'Patron registration: Modify permission' for member library staff, they won't be able to change other fields.
5 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 -
Return ItemRecordID in responses to BibHoldingsGet
A recent change to PAPI allows for the retrieval of, and adding to, different types of records sets, including Patrons, Bibs, and Items. Adding to Patron and Bib records sets is straight forward because there are existing endpoints within PAPI that return BibRecordID and PatronRecordID numbers. This isn't the case with Item record sets because there a currently no endpoints that provide an item's RecordID. This enhancement would add the ItemRecordID to each row in the BibHoldingsGet response.
7 votes -
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.
4 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 -
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 -
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.
6 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.
9 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.
6 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 -
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…
12 votes -
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.
11 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…
57 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
- Don't see your idea?