621 results found
-
Update SIP to handle foreign characters (diacritics)
SIP should handle foreign characters (diacritics) correctly. When a patron's name or an item's title has a diacritic then it throws an error. For some vendors, it breaks the application and prevents customers from logging in and/or accessing their checked out or held items.
1 vote -
Ability to limit the "Number of days past first available" setting to the branch level only.
The "Number of days past first available" setting was developed specifically for the issue where libraries would like the new item's hold requests to be limited to only patrons registered at the item’s assigned branch and other branches associated with the same parent library for a specified number of days. We would like to try this workflow, however, it won't work in our system as all of our branches are under the same library organization.
1 vote -
Bulk waive criteria should allow user to specify maximum or minimum amount of charge to be waived
The new(ish) bulk waive options in Leap are extremely useful, but library administrators often want to waive charges of a certain amount - usually "waive all charges of less than X dollars." The current interface, however, doesn't allow the user to specify an amount for the charge to be waived. This would be very useful and would avoid the need for creating a SQL statement to identify such charges. The scenario of waiving all charges greater than a given amount is less likely, but if you're adding the ability to specify a maximum, why not add the option for a…
1 vote -
Add the ability to round all prices to nearest nickel
With the production of pennies ending, we've had some discussion around prices in Polaris. Ideally, we would like to see some method of optionally having all prices (item prices and fines) rounded to the nearest nickel. We haven't run into any problems yet, but as pennies eventually become more scarce, we suspect that we'll have trouble with cash payments.
2 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
•…1 vote -
LEAP: Change status from checkout to Lost or Damage in an item's record
A patron doesn't have their library card number on hand, can there be a way to change the circ status to lost from the item record so the replacement cost can be automatically be charged to the current patron's record? At least from the owning library's side, I understand messing with anything in the 'Details' tab shouldn't be done by another library. Hopefully, it can be done with less hoops to jump through by going through the item history and making sure to select the correct patron or hitting any of the other tabs.
1 vote -
Auto-Renew on Collection Level
We are removing overdue fines for our Children and Teen collections and wanted to enable auto-renew for the collection codes that are related to the Children and Teen collections, but realized auto-renew can only be enabled on an organizational level. It would be great if there was the ability to enable it on a collection level, especially for children's materials as, I'm sure we're all familiar, children are really bad at remembering to renew or return
4 votes -
Add Temporary shelf location to picklist
Make temporary shelf location visible on picklist. Adding this to the picklist will allow staff to quickly locate items that might be on display or some other temporary shelf location.
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.
2 votes -
Navigation buttons at the top and bottom of All Items list on LEAP bibliographic records
On the All Items tab of LEAP bib records, it would be helpful to have page turning buttons at both the top and bottom of the list for ease of navigation
5 votes -
Reporting Groups for Collection Codes / Material Types (reporting only)
Add a reporting-only way to map Collection Codes and/or Material Types into any number of user-defined reporting groups, with many-to-many membership. Grouping logic should live in a maintained mapping table (not hardcoded in reports) so changes update all dependent reports automatically.
Problem
Only staff with database access can currently create sequel/SQL mapping tables (e.g., MapCollection, MapMaterialType) for flexible rollups. Others must regroup exports manually, which is inconsistent and fragile.
Provide a UI-managed “Reporting Groups” feature that acts like a built-in mapping/lookup table:
• Many-to-many: one code can belong to multiple groups; groups can contain multiple codes.
• Reporting-only: no impact…13 votes -
Add 'Canceled' as a Payment Status for PO Line Items
In the PO Line Item screen, when the Status is set to 'Canceled', the Segment Status correctly shows 'Canceled', but the Payment Status still displays as 'Open'. We would like to see a 'Canceled' Payment Status option added so the record more accurately reflects the true state of the transaction. This enhancement would provide clearer, more consistent data for our reporting and workflow.
4 votes -
Please add Mackin to Polaris Libraries EDI suppliers
Kitsap Regional Library wish to engage in EDI based acquisitions with this supplier
1 vote -
Auto assign Patron Code based on age
In our system we have different Patron Codes for different ages. This allows us to differentiate services in the library to patrons of different ages. Occasionally, during the registration process (we exclusively use Leap) staff will forget to assign the correct Patron Code based on the new patron's age. If the system was able to auto-assign Patron Codes based on the inputted Birthdate, it would greatly reduce human error.
3 votes -
Ability to bulk update the expiration date to a relative date
Most of our libraries have changed their expiration date to 2 years. For new patrons this is fine, but for most existing patrons, their expiration date will still expire within the original 1 year expiration period. It would be helpful to be able to bulk update patron's expiration date, for a particular branch to a relative date. For example, 2 years from the date of registration.
3 votes -
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.0 votes -
Placing multiple holds
When staff need to place multiple holds on the same title for a book club, we have to still search for the item individually and select it until we've selected enough copies of that title. If there were a way to simply search once for the title and select whichever bib record you want and be able to indicate how many copies you want from that bib record, it would be easier and more helpful. Not sure if this is possible, but it would be nice.
2 votes -
Ability to suppress patron codes at registration
Our system uses over 20 patron codes but less than half are used when first registering an account. We'd appreciate the ability to suppress some patron codes from the patron code dropdown menu in the NEW patron workform (but not when displaying an existing patron account that has already been saved and had a patron ID assigned). This would cut down on staff accidentally selecting the incorrect patron code when registering accounts.
2 votes -
Control staff access to the Label Manager in Leap
Label printing can be a limited function in a large library system, using specialized printers to perform the task. Consistency is also important in the spine label. By being able to control access to this utility, it will ensure a better spine label product across a library system.
1 vote -
Item and Patron barcode printing
We would like the ability to print an item's barcode while in Leap. We have items that either require multiple barcodes for processing or items that have lost their barcode and it would be nice to print these directly from Leap to the printer of our choice.
Currently staff need to grab the barcode from Leap and then open a different software to print the barcode label.
This idea would also be nice if we can expand to a patron's barcode. Patrons come in and don't have their card for that visit but need it to access the computer. Rather…
3 votes
- Don't see your idea?