518 results found
-
"Patron has holds" popup when check out workform OPENS instead of when first item is scanned
We are upgrading to 7.7 and have just decided to NOT turn on the new feature that suppresses non-blocking 'blocks' such as the 'patron has holds' popup block.
Ellie K. submitted a related request here: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/49700207-remove-pop-up-about-holds-on-shelf-when-checking-o to suppress the block if the first item being scanned for checkout is a hold from the current branch.
We'd like to take this a step further and suggest the block appear when the check out workform is opened. This achieves the purpose of the block (triggering staff to alert the patron that holds are available) without even getting into whether the transaction that…
12 votes -
Hold History report where you could enter a Bibliographic Record ID
If Simply Reports had a Hold History report, where you could enter a Bibliographic Record ID and then see the history of hold requests created for that bibliographic record -- it would be most helpful when trying to see why an item wasn't automatically renewed, or was blocked from renewing.
9 votes -
Leap Find Tool Window Expansion
It would be nice if the Leap Find Tool window could be enlarged to full screen.
15 votes -
Call Number Scheme Menu in Item Records
We use only two call number schemes in item records, either “Dewey Decimal” or “Other”. I wonder if it is possible to hide the rest of the schemes from the dropdown menu in item records. This will reduce the chances of accidental selection of an incorrect scheme.
6 votes -
Provide additional details to PowerPAC usage statistics
The PowerPAC usage statistics provide a minimal view of the patron's use of our PowerPAC. We also use Vega Discover and cannot accurately compile information between them and with other platforms.
Examples to include/add: Total visits, total unique visitors, total searches submitted.
4 votes -
Item counts on PO and Invoice Headers
It would be beneficial to have a total item count in the header of POs and Invoices for quick reference. Currently there is no easy way to get this count from a PO or Invoice because there is not even a row count column under the items view.
11 votes -
Send record sets to Label Manager in Leap
The desktop client has the ability to send a record set to Label Manager; Leap does not. Without this feature, mass relabelling projects such as adding a new section are an enormous drain on staff time.
22 votes -
Bibliographic consistency check when editing bibs
In cleaning up bibliographic data after years of laissez faire cataloguing practice, we have run into a consistent stumbling block that requires us to backtrack. Certain bytes, especially in the 007 and 008 fields appear to require consistency across them to properly read at an item level (we became aware of this when getting red toasts scanning items for a weeding record set, that appeared initially to be in the inclusion criteria).
By way of example: If you input in 007 an 01 byte of 'd - Videodisc', than the 04 byte would have to be 'g' 'h' 's' or…
4 votes -
Staff choice in error report output from "add from" function
In playing around with Weeding-type record sets, we have noted the following: using the action "add from Item Record set" yields, as its error report output, a list of item-level control numbers.
If you "add from file", the error report output is item barcodes - a way of searching for items that comes a bit more intuitively to our desk staff.
It would save us a couple processing steps to avoid importing from files, so we would love to use the "add from item record set" feature - however, the control number output for problem items (those that are outside…
2 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.
2 votes -
Notes Alert on Polaris Client Checkout Window
We would like the notes icon on the patron Check Out – [patronID] - Normal – Polaris window to have the alert color change like you see on The Patron Status - [patronID] – General – Polaris window and other Patron record windows? We see that Leap has the color change of its Notes icon on its checkout page. Our landing window for opening a patron record is the Check Out – Normal – Polaris window and it would be helpful to have that notes icon change color like the other patron record windows.
2 votes -
Report for staff user or workstation transactions
We could use a report based on staff user and/or workstation listing all transactions made for a given date range. Most importantly for us, cataloging information which could provide date and time of bib records being created and/or modified as well as circulation information for staff who work the circ desk.
3 votes -
Hold type Record Set
I would love to be able to create a Record Set of Holds. There are times when we need to bulk edit hold data because of library closures, etc. Being able to bulk change that data and store that data would be immensely helpful.
13 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 -
Add 'Hold Activated/Created" to item history
It would be useful to have in the item history when a hold was activated. I had an instance where an item was put on hold for the wrong account, and it would have been useful to see who had placed the hold or where it had been added. I figure you can see this from the hold record, but the staff member who had received the accidental holds cancelled them before we got a chance to look at it.
8 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 -
System auto-capping late fees/fines
Our system does not currently have late fees on most of the collection. But for the collections we do, we have a max that we will charge in late fees for items returned on the same day per patron. It would be nice if we could set up for the system to automatically waive fees for overdue items that exceed that amount.
2 votes -
Improving full-screen editing for MARC records
Make full-screen editing more easily usable. One example: deleting multiple fields at once.
Make it possible to add fields ANYWHERE, not only after a similar type of field (i.e. fixed fields--why can't I add them anywhere?).
8 votes -
Make it possible to save / share Power Searches in Leap outside of the individual level
Enhance operational efficiency and standardization by allowing the saving of Leap power searches beyond individual staff profiles. Currently, saved power searches reside only at the personal level, hindering consistent workflows and leading to duplicated effort. Enabling system- or library-level saving for power searches will allow libraries to establish shared, robust searches, improving consistency and ensuring critical search capabilities remain accessible regardless of staff changes.
13 votes -
Improve the Request Manager
Our staff complete weekly and monthly checks on hold requests to ensure our customer holds are being fulfilled in a timely manner.
To do so, staff check the hold status (Active vs Inactive), age of the hold against the hold type (item or bib level), number of available copies, and number of holds in the bib level queue. This requires staff to open item/bib records and return to the Request Manager list frequently, and can mean the review lasts over several days, making it hard to track where they were in the queue when they had to pause in the…
9 votes
- Don't see your idea?