4 results found
-
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 -
Optional PAPI parameter to NOT send confirmation email to patrons
Currently in SA->Parameters->PowerPAC->Patron access: Contact info update there is an option to turn on/off the Confirmation e-mail to patrons. This is a nice feature when patron's change their email or phone online. However, there are times when we need to change that information via PAPI and the patron doesn't need a confirmation email.
For example, we have a partnership with our local public school. If the contact information changes for a student, it needs to be updated in the library account as well. In that case, the patron does not need a confirmation email sent.1 voteThis is already supported through using the "ignoreSA" flag on the PAPI call. If that is set to "true" the email will not be sent to the patron.
-
Provide way to fetch patron's credits using Polaris API
We have Polaris integrated with Teller to process patron payments. Within Teller, we would like to use Polaris patron credits as a form of payment. We have been talking to Teller about this, and we believe this can be achieved by getting patron credit information via the API. At present, the API only returns charges owed by a patron, not any credits a patron may have.
1 vote -
Add PAPI methods to edit Patron Information
The ability to edit patron information—such as custom data fields or core registration details like name and email—without requiring the patron’s PIN or password would be highly beneficial. While using a Record Set to bulk edit standardized fields (e.g., expiration date or User1–User5) is extremely helpful, it doesn't cover all use cases.
For example, we regularly receive updated information from our partner school, including address changes. Currently, the inability to programmatically update these records creates workflow bottlenecks and limits our efficiency in maintaining accurate patron data.1 vote
- Don't see your idea?