683 results found
-
Allow multiple statistical classes to be assigned to patron records
Currently only one Statistical class can be assigned to the patron record. It would be helpful to allow multiple statistical classes to be assigned. Sometimes a patron can be registered while multiple programs occur, such as when a child is registered for a 0-5 campaign, and then later they may participate in another reading program. Both codes would be used to track each type of program. Currently, we have to use the notes field to do some tracking, and the notes field isn't as friendly since it is free text.
5 votes -
Implement EDI Claiming From Sierra/Millennium
We’ve long benefited from Sierra’s well-supported EDI claims functionality, which has enabled seamless communication and efficient claims processing with our library partners. However, we’ve observed that Polaris currently lacks equivalent support for sending claims via EDI in the same format.
Can you please port over the EDI Claiming Format From Sierra & Millennium to Polaris? This would make it easier for libraries migrating to Polaris from these products.
5 votes -
Improve usability of Collections and Mat Types fields when searching the PowerPAC
Specifically, in 7.7, in the options to display facets within the Administration Explorer: Dashboards: Narrow Your Search & Related Searches, allow the opportunity to display the checkboxes for the Collection Codes and/or Mat Type for an improved patron experience.
Many of our patrons prefer the PowerPAC experience (over Vega Discover Premium), and they would like to search within our specific collections. When they use the "More Search Options" feature, the viewable area per section is only four items, and scrolling is challenging. Depending on the screen size and text/accessibility settings, one facet could use a significant portion of the screen,…5 votes -
Provide Payment Type Edit option after submission
When we apply customer payments in Polaris, staff select payment type from a customer (cash/check/CC). Payment type is recorded in payment reports to reconcile our credit card statements each month. Sometimes a person will mistakenly record a payment as cash when it should have been CC. Once recorded, a mistakenly selected payment type cannot be corrected in Polaris. It would save significant time if an edit/correction option was available.
5 votes -
Add an Invoice Status of 'Ready to pay'
Add an Invoice Status of 'Ready to pay' or 'All items received' in the Find Tool - Invoice - search filter. This will allow EDI invoices to be filtered to ones where all items have been 'received' and make the invoices ready to 'pay' easier to find
5 votes -
Parent/responsible party information in registration
We would like an optional field for parent or guardian information in the registration form.
We don't require parents to have library cards if they only want their children to have cards, and we have instances where only children can qualify for free cards (school district vs county lines). It would be great to include a parent name, DOB, and DL# in the child's registration without using fields that prompt duplication notices.
5 votes -
Add support for automated clearing of the [PolarisTransactions].[Polaris].[NotificationLog]
The PolarisTransactions].[Polaris].[NotificationLog] has Personally Identifiable Information (PII) in it. That table is never cleared, even if you select to clear the PatronID from the PolarisTransactions.
Ideally, we'd like an option for this data to just be cleared out after a certain period of time. If that is not possible, then NULLing the patron id when that option is enabled for the PolarisTransactions should work here too.
5 votes -
Provide alert when staffer selects a location different from that a workstation is associated with when logging into Leap.
Despite constant reminders, we have issues with substitute staff who cover at various locations logging in under the wrong branch. It would be great if Leap could have a pop up box, requiring confirmation to proceed, that alerts the staffer if the workstation they are logging in on is associated with a location other than the login branch.
5 votes -
Putting hindered holds more prominent so all holds get processed in a timely manner
There are lots of things that can go wrong with holds fulfillment. From things remaining too long in the RTF, to holds that were item specific, and now the item record has been deleted, holds on bibs where all items are restricted from filling bibs, holds where the item has been shipped months ago, holds where the volume-level hold information is incorrect.
While there are reports that some libraries run for this, those are not "front and center" in most workflows for ALL libraries to be aware of them and be taking action to handle them.
About the best solution…
5 votes -
Search Sorting
As we move libraries away from the client to Leap, they are finding a few things that are missing that made their lives easier. One is to be able to choose how a search is sorted prior to the search happening.
5 votes -
Ability to input OCLC number directly into hold to be converted to ILL
When inputting information for an ILL request for a patron, our ILL clerk would like there to be a field where she can input the OCLC number of the item she is wanting directly into the hold request. That way when she exports the request, it will directly sync with the item she wants, without having to use ISBN.
5 votes -
Make the chronology date field manually adjustable in serial check-in boxes
When a serial holdings record includes a pattern for a completely irregular issue, and the only chronology date on the issue is the year, the chronology day and month chosen when the publication pattern was set up is used for all following issues checked in using that pattern. The ability to manually adjust the chronology date would be very helpful, and would ensure that issues display in the correct order.
In the attached image, the expected date shows the date that the issue was actually received. However, because the chronology date for the first completely irregular issue we received was…5 votes -
Bulk delete ILL-requests in Leap
When searching by ILL-Request in Leap for a specific date range, I would like to be able to Shift + Click to highlight and add to a record set to perform a bulk delete.
5 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 -
Allow Username to begin with number
It seems unnecessary to force the Polaris Username field to begin with a letter. We would love for the Username field to have the ability to begin with any character.
5 votes -
Allow setting continuity pattern at the first level of enumeration
We have some serials that only have one level of enumeration, that resets annually (i.e. no. 1 is published in January and no. 12 is published in December and there is no volume number). It would be nice to have option to set the number of units and the continuity at this level.
5 votes -
Enhanced Patron Privacy (UDF)
Patron Privacy is becoming a much larger issue. We currently use a UDF to hold our Patron ID.
We'd like to suggest that having the ability to create some way to collect and keep private patron data such as an ID or other PII would be ideal. And having this information encrypted in the database would be preferable as well.
Being able to prevent this information from always showing, would be a benefit and even having the ability to only show a part of that information, such as the last four digits or something similar, would be useful.
5 votes -
Registration Drop Down Box
Please add a drop-down box for the profile section of registration. There is a drop-down box for the address section labeled term but there is not one for the profile section. It makes it easier for staff to choose the correct date. In the Polaris toolbar, there is a drop-down box for patron info and address.
5 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 -
Leap Offline patron data tables should be purged - PII Concern
When leap offline data is uploaded, it goes into [LeapOfflineTransactionDataID]. This contains PII information of the items & patrons that performed CKOs. However, this data is never cleared by the system, even after it is processed.
I can see keeping it around for awhile, but maybe have it follow one of the other settings in SA for purging data or set up a new SA setting for purging this PII data.
5 votes
.png){kind=link}
- Don't see your idea?