517 results found
-
Add a note field when resolving Lost item charges at Check-in
We would like there to be an option to add a note when resolving lost item charges, processing fees, and overdue fees when checking in a Lost item. Currently, if we want to add a note when waiving processing fees or overdue fees, we have to first charge the fees, then go to the patron record and waive from there after the fact, just so we can add the notes. It would be much easier if we could add the notes right on the screen that pops up (see screenshot).
16 votes -
Add email notices to Use Name on Identification in LEAP Registration
If the check box is checked for Use Name on Identification it only applies to print and telephone notices. It needs to apply to email notices too.
16 votes -
reading history
Reading history improvements, allow for more then 9,999 and allow reading history to be searchable on staff and patron side.
16 votes -
Web Admin - PAPI Key Management Permissions
With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).
We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in…
16 votes -
Leap Find Tool Window Expansion
It would be nice if the Leap Find Tool window could be enlarged to full screen.
15 votes -
Leap - Receipt WYSIWYG editor
Currently, there is no way to adjust receipts. We only have the option of which fields and we are not allowed to put those fields in an order that suits our workflow. We would love to see Leap have a WYSIWYG editor so each library can configure font size, fields, etc. for each receipt.
15 votes -
Checkin Lost Item as Damaged
If an item has a "lost" status, and is returned damaged we are unable to change the status to "damaged" via the check-in damaged option (must be in/out for damaged check-in to be used). This would be helpful for situations where the patron returns an item that was declared lost (either automatically by being +30 days overdue or manually) and then later found and returned to the library via drop box, to be able to demonstrate the item was returned damaged with no previous poor condition notes on the item.
15 votes -
Stacked Sorting
We would like the ability to do stacked sorting in searches and record sets. This would allow the user to sort by one aspect and then another with it stacked (eg. sorting by pub date and then call number, so you see items within a call number in pub date order). In both searches and record sets, it only seems to sort by the current choice, meaning the way it's sorted within that one type is random (or alphabetical by title, which isn’t always the most useful).
15 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 notes field to Polaris Staff Accounts
We occasionally need to document the use and purpose of special staff accounts. Mostly we do this to make sure they don't accidentally get deleted.
Historically we did this by using the email address field on the staff account. Now in PolarisAdmin (Web) it enforces email address formatting rules in that field so we can no longer use that field.
This was always a hacky work around. It would be better to have a notes field on polaris user staff accounts like patrons do. It should be up front and in your face though and not hidden behind menus. Again…
15 votes -
Customizable Check In screen
It would be awesome if we could add or adjust the information that displays on the Check In screen in Leap, for example to include an item's shelf location for easier staff sorting - and it would also help to catch Display items that have circulated on their return.
15 votes -
Ability to import files in Leap other than .dat, .mrc,.txt., .xml
We receive vendor records with file extensions .FIL and .001. We are able to import these in the Client but are not able to import them in Leap.
15 votes -
Allow Google as a sign-in method for Staff Accounts
In addition to Single Sign-On (SSO) support for Microsoft Azure and ADFS, please consider support for Google Workspace. We recently migrated all of our email for our consortium (42 members) to Google and would greatly benefit from the ability to use the already signed-in information to authenticate into Leap. See screenshots for a design/concept mock-up.
15 votes -
Align Item Editing and Manage Item Dialogs Permissions
Item editing permission organizations are based on the Owning Branch of an item. However, permissions for item editing through the checkout page ('Manage Item Dialogs') are based on the item's Assigned Branch (as well as the check-in branch matching the assigned branch).
We think it makes sense for both these permissions to be aligned to the Owning Branch, otherwise it can leave room for inappropriate changes. For instance, in our consortia some items are owned by one library but lent to others (assigned to their libraries), and this gap has led to item changes by staff that shouldn't have had…
15 votes -
API reading history sortable by title or last added
We have had multiple patron requests to be able to sort reading history delivered by API by latest added or by title. Currently reading history is displayed with the oldest first which results in a lot of scrolling by the user.
15 votes -
Add LC approved fields to Cataloging more quickly
Catalogers have been waiting since January 2020 for MARC field 532 - Accessibility Note to be included in the MARC bibliographic validation table. This MARC change was approved by LC in 2018 and has been showing up in AV records ever since. Catalogers see a "not defined" error message when saving a record which includes an unvalidated field.
Currently we may only add a local MARC tac to the validation table (eg 9XX, X9X or XX9). Otherwise, it must wait for the LC MARC bibliographic update to be implemented by Polaris development in a new Polaris version. We now hear…
14 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…
14 votes -
Floating Close button in Patron Registration
Could we have it so the close button within the Patron Registration follows you as you scroll down like the "Save", "Renew", etc do? I often find myself nowhere near the top when I am done with a customer account and have to navigate all the way back up just to close the record. I could see this also being useful in Bib records
14 votes -
"Today" on Date Picker
When using the date picker, we'd love an option to select "Today" and have it set the date automatically for us. When updating really old cards, it can be a pain to have to select a date with the picker when we have to change every field. Typing is limited in its ability to be a workaround, because it requires specific formatting in order to work.
14 votes -
Add eReceipts as an option in LX Starter.
The only option for eReceipts is plain text. It would be a fantastic feature to customers to be able to build a nice HTML email for them.
14 votes
- Don't see your idea?