102 results found
-
leap acquisition
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…
2 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.
2 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.
4 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.
4 votes -
Leap: edit POLI segments
Add editing of the fund, destination, and collection of POLI segments to match the client functionality.
8 votes -
Leap: link from invoice line item to holds queue
The client has a direct link from the invoice line items to the holds queue. In Leap, getting to the queue requires going through the item (and sometimes bib).
8 votes -
Leap: links from funds
In the client, funds link directly to invoices, POs, POLIs, and other related records. Funds in Leap have very few links. Direct linking to working acq records facilitates tech services workflows.
11 votes -
Leap: cancel from POLI workform
In the client, a POLI can be cancelled from the PO, POLI view or from within the POLI workform. In Leap, it can only be cancelled from the PO, POLI tab. Adding the ability to cancel from the POLI workform would reduce steps and reduce the likelihood of staff selecting the wrong POLI to cancel. This would help with the transition of tech services to Leap.
9 votes -
Merge Claimed and Received Issues in Leap
Can the Serials Check-In Utility in Leap allow the merging of claimed and received issues? This functionality currently exists in the desktop client. This is a barrier to getting staff in both tech services and service desks to move Serials work over to Leap.
3 votes -
Invoice links to POLIs
In the client, staff often use the link to individual purchase order line items, but this is not yet available in Leap. Because an invoice may have many linked POs, and POs may have many POLIs, it can be difficult to find the correct POLI without access to direct links.
Adding POLI links would reduce friction for tech services staff making the move to Leap.
12 votes -
Bulk delete predicted serials issues in Leap
Can the Serials Check-In utility be updated to allow bulk deletion of predicted serials issues? When a weekly/bi-weekly publication changes the day of the week that issues are released, it is easier to update predicted issues in the desktop client* but staff without authorization to create prediction patterns cannot complete this work in Leap. This slows down access for community members.
*In the desktop client, staff can bulk delete all but one predicted issue, edit the remaining predicted issue to match the new publication date, and then bulk predict issues to match the new day of week without closing and…11 votes -
LEAP - Add Received Date and User to POLI segment view
By adding received date and user to the POLI segment view, we would be able to quickly troubleshoot issues without needing to run reports.
8 votes -
Consistent Collection Name Display in Cataloging and Acquisitions Modules
We would like to submit an enhancement request regarding the display of collection names in the system.
Currently, the Cataloging module displays the collection name together with its abbreviation, while the Acquisitions module only shows the first part of the collection name in the dropdown list. This difference in display may cause confusion for staff when selecting or identifying the correct collection.
We would like to propose an enhancement so that the collection name display is consistent across both modules, ideally showing the full collection name together with its abbreviation, similar to the display in the Cataloging module.
This improvement…
8 votes -
Cancel Purchase Order Line Item Segment - LEAP
One way that our ability to transition to fully utilize LEAP for acquisitions is limited is the inability to cancel a segment of a Purchase Order Line Item. There are times when vendors only send us a partial fulfillment due to backorder cancellations or other issues. At this time, we have to use the client for this issue.
20 votes -
POLI ISBN search via remote databases in LEAP
When manually entering POs and POLIs in Leap, I want to be able to do an ISBN search via remote databases to pull in an on-order MARC as I do in the client.
9 votes -
Create item record from invoice line
We would like the ability to create an item record from an invoice line in Leap. This is especially useful when manually building invoices, and can be done in the staff client.
14 votes -
Greater specificity in Weeding Record set red toasts
When scanning materials into a weeding-type record set, the system throws (broadly) two types of toasts - yellow and red. The yellow toasts very helpfully specify in what exact manner the given item does not match weeding criteria filters. However, the red toasts (excluding "Barcode is invalid" and the indication an item is already in a weeding record set) do not specify in what exact manner the given item falls outside the inclusion criteria.
For especially complex weeding criteria, this can make for one heck of a slog through the item record, and subsequently the attached bibliographic record, to identify…
6 votes -
Place multiple holds for one patron in a purchase order
It would be very helpful if Polaris had an option to be able to highlight multiple titles in a purchase order whether in the pending process or released process by being able to select multiple titles, right click, and PLACE multiple holds for one patron.
9 votes -
When receiving items in ASN, check immediately if there's an invoice to generate
When receiving cartons in ASN, it would be nice if Polaris would check immediately if there's an invoice to generate instead of either a. going to the process EDI invoices work form to find and generate it manually, or b. waiting until the next day when the EDIAgent runs again.
2 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.
19 votes
- Don't see your idea?