106 results found
-
Place hold on bib from find tool or record set
It would be useful to be able to select a bib record from a record set or from Find Tool results and place a hold from there. Possibly add this function to the More Actions menu.
2 votes -
Clearer indication of errors in background processing
In Bulk Change and Import, the process can complete even if individual records could not be updated (because they are locked or for some other reason). It would be helpful if the errors were made more obvious upon completion of the process, possibly through adding a column to the Background Processing table to indicate how many records were not successfully modified. This would indicate to staff that they need to open the report to find the issues. Even better would be a succinct error report.
4 votes -
Improve LEAP's Find Tool - Record Set management options: Quick Delete & Merge
It would be nice to add a function where you can merge multiple record sets when using the Find Tool-Record Set without having to manually go into the record set and copy records over.
Similarly, the ability to click the check boxes for multiple record sets and delete them from the results page without having to enter each individually would speed the clean up process after projects are complete.
3 votes -
Add the ability to schedule bulk updates
Periodically we might need to update a large number of records. Like changing 10,000 item records to not display in PAC. When we have done that during the library hours it negatively impacts response time. What would be desired would be an option to schedule the update for after hours.
23 votes -
How to add released PO Items to an Item Record Set
In some cases, we would like to monitor the items we have ordered. If these items can be loaded into an Item Record Set, it would make them easier to access and track.
In Polaris, users can add items from a released Purchase Order (PO) to an Item Record Set.
Is there a similar function available in LEAP?
9 votes -
Prevent Out Items from Being Changed to Withdrawn When Approving Weeding Record Sets
When staff bulk change items in an item record set, items with a status of Out are not changed to Withdrawn. We would like weeding record sets to follow the same logic during approval.
When a weeding record set is approved:
-Items that are currently Out should not be changed to Withdrawn.
-The remaining eligible items should be processed normally.
-Staff should receive a block stating that “[number] item(s) were not approved because they are Out.”Use case:
Several items were checked out between being added to a library’s weeding record set and the set’s approval. During approval, they were…
9 votes -
LEAP - Ability to edit invoice header charges
The functionality to edit fund or charge type in header charges would help streamline acquisitions workflows. At this time, we have to delete and redo the charge when we only want to update the fund, creating more room for error.
14 votes -
We would like to have our Tech Logic Inventory Wand connect directly Leap to do a live inventory. Instead of uploading a file.
Right now we take our want out into the stacks and run it with the Tech Logic software on the laptop. Once we are done with the section we want to inventory, we then save and upload a document to Polaris or Simply Reports to update our materials with the new inventory date. It would be nice to have our Inventory Wand link directly to Leap and update the inventory date live in our system and cut out the middle step of saving and uploading the file.
5 votesWe are adding a PAPI endpoint to allow vendors to update the inventory date on items in Polaris 8.2.
TechLogic has already been in contact with me about connection to the API. There may be some work on their end needed to consume this endpoint, but the infrastructure to support this will be in Polaris with Polaris 8.2.
-
Link from POLI to INLI (Leap)
Direct links from a POLI to it's invoice line item would be helpful and match client functionality. Linking to an invoice that may have many line items requires more scrolling and double checking.
16 votes -
Allow staff to add supplier records without allowing them to modify the Postal Codes table
When staff add Supplier records, they currently are required to have the "Modify Postal Address Fields" permission. This means that they can add any postal code/city combination into the address and, if it is not already in the Postal Codes table, it will automatically be added there. This allows staff to add incorrect data into the Postal Codes table, which then allows circulation staff to accidentally select those options when adding new patron accounts. We would like to see Supplier records have the same option as Patron records, where we can lock staff down so that they can only select…
12 votes -
Add POLI record ID to header (Leap)
Currently the POLI record ID is only visible as part of the url in the browser. It would help staff to more easily differentiate between multiple POLIs for the same title if the unique ID was included in the POLI header and as a column in the PO.
14 votes -
Preview Bib for SHR and Hold creation
It would be useful if Leap had an equivalent for the following client functionality:
Right click on bib search results to see a preview of the record. This is a time-saver when creating new serial holdings records and when placing holds in cases where titles may be similar.10 votes -
LEAP: Supplier Record Reminder - Needed for Miscellaneous-Type Invoices
Miscellaneous invoices are created and used to pay for materials that are not linked to bib records. These invoices always need to have a Supplier record chosen for our finance purposes. Misc. invoices can be saved and payed without a supplier, however, Polaris always gave a reminder prompt if one is not chosen. In LEAP there is no reminder. We would like the same prompt to be added to LEAP. Making these invoices happens infrequently for some staff, so the reminder is helpful.
9 votes -
Leap: Create item record from serial issue record
In the Polaris Toolbar, when handling serial issue records, there was a direct action (called "Create Item Record") that would create an item record from a serial issue record. This is helpful for our staff for copying over enumeration and designation information.
That same action is not present in Leap. Our staff would appreciate having this feature in Leap.
8 votes -
Need Supplier Templates drop-down at Bulk-Add to New PO screen
Supplier Templates are not available to choose from in the Bulk-Add to New PO screen. It would be helpful to have that drop-down menu available to us, like it is in the client app, and like it is for creating a New Purchase Order manually.
5 votes -
Link Invoices to Each Other in Leap
We would like the option to link invoices together in Leap like we can in the client. We use this feature to keep track of credit memos by linking the credit memo to the original invoice.
22 votes -
Leap - Copy fund allocations
I am writing to request an enhancement for the Leap Acquisitions module. Currently, the system does not allow users to copy fund allocation numbers.
When adjusting funds, the Encumbrance and Expenditure Fund Balance Limits often do not update automatically. This requires me to manually re-type the "Total Allocated" amount into six different limit fields. Manually entering the same 6-digit or 7-digit numbers multiple times is not only time-consuming but also creates a significant opportunity for manual entry errors.
Could you please update the system to allow copying from the "Total Allocated" line and pasting into the limit fields? This small…
13 votes -
Bulk Change Serials Issue Records Status
Offer the ability to bulk update Serials issue records to a new status. We order multiple copies of most serials, and currently we have to open each issue to change it from "Claimed" or "Pending Claim" to "Not Available" when the vendor cannot supply it.
16 votes -
020 Field Character Limit Should Exceed 50 Characters & Not Reject Placing an Item On Order
We are having manually placed orders rejected because the 020 field for large print books sometimes exceeds the 50 character limit. Polaris/Leap will accept 020 fields that are up to 49 characters, but not for OCLC MARC records that have extended to 54 characters. This happens whether we are attaching to an existing record in Polaris/Leap or for a new one imported from OCLC/Connexion. It seems completely arbitrary that 49 characters are accepted, but 54 characters -- just a few over the limit -- are not. Thanks for looking into & considering this request.
13 votes -
Leap: include examples for pub pattern creation
Staff find the examples provided in the client helpful when creating a new pub pattern. It would be great to see the same in Leap.
14 votes
- Don't see your idea?