677 results found
-
Polaris should re-evaluate hold eligibility when trapping preferences are set
When a hold request is placed, Polaris performs an eligibility evaluation only once—at the moment when the request is first placed. Polaris does not re-evaluate eligibility later. So if Polaris is configured to use hold trapping preferences that prefers "my patron" but some temporary circumstance prevents the assigned library's item from filling a hold for the library's patron, the hold must now be filled by a different library. This can be mitigated if staff notice the problem and delete and replace the hold, but this is a lot of extra overhead and in all likelihood the problem will go unnoticed.…
14 votes -
Add support for direct print (QZ tray) to leap offline
Add support for Leap direct print using QZ tray to Leap offline. That way libraries don't have to figure out something special when they are in offline mode which is already a stressful time period for them.
14 votes -
Grouped Bibs
Since moving to Vega Discover, we are finding that we are having some issues there with holds queues due to the rolled up records (I've posted an idea over there too), but it's also exacerbated by the way records show in Leap.
Ultimately, it would be great if bibs rolled up in Leap in a similar way to Discover. Not the different formats per say, but if there is a softcover, hardcover, deluxe, and reissue of a book, it would be nice to be able to see those all together to determine circ stats for them in a combined view,…
14 votesI want to note that we may need to split this into several smaller requests, but we can keep this open until we have a better sense of how to best to break it down.
The BIBFRAME-based model in Vega natively handles some of this grouping. It's not really feasible for us to create BIBFRAME-based groups in Polaris right now, but some of the problems mentioned here we might be able to solve. For example, Vega Reports might offer us an opportunity to provide grouped bib stats by combining stats for MARC bibs based on Vega roll-ups.
-
Making Text in On-Order Records a Different Color
We have noticed an uptick in libraries circulating items on on-order records despite it violating consortia policy. We would like to see the text of on-order records (or even just specific fields) be in a different color to help provide a visual indicator of the record type.
14 votes -
Add Call Number to Item Information on Account Tab
Staff are requesting that the call number be added to items that are billed on the account tab in the patron page. Right now, the main item information is Barcode/Title/Organization [branch] so they have to click to the item to see the call number when they do a shelf check. Adding the call number to this page will help staff work more efficiently by skipping having to look it up on another page.
14 votes -
Links to Public Access Catalogs from Leap Item Records
In Leap, links to web-based public access catalogs are only available through bib records. It would be convenient if they can also be made accessible through item records.
14 votes -
Captcha for Self-Registration
It would be nice to be able to add captcha (or something similar) as added protection to Self-Registration through the PAC. It would ensure that a human is actually entering the information on the other end rather than a bot. An uptick of suspicious registrations is eating into valuable staff time and we would like to be able to add a layer of protection to our Self-Registration process.
14 votes -
Edit Half-Deleted Item Records
When doing clean up work we run into instances where we are not able to delete something like shelf locations because it is assigned to records that are in a deleted state. While we know we can just delete the records 1 more time, some of these records are tied to other things we track and would prefer to keep them in the system.
Currently we bulk change them at the server level but would like a way to be able to do this within the ILS.
14 votes -
Add a filter in the Leap find tool to search Hold Pickup Area's
Currently you can search hold requests by pickup location.
Libraries would also like to search the hold requests by pickup areas.14 votes -
Call Number drop into the Classification field in the Item Record
Have the Call Number (082 #a) drop into the Classification field in the Item Record when the item moves from On Order to Received.
This function would most benefit staff who catalogue (or import full catalogue records) and then manage the Purchase Order process.
The goal is to reduce the room for error when adding items.
14 votes -
Printing from Request Manager
Adding an option to export to Excel any lists from the Request Manager such as Picklist Processing and the Request Manager.
14 votes -
PAC Header URL
Currently, when a user clicks on the library’s logo in the PAC header, we can specify a URL that opens. However, when they click it, the URL defaults to opening in the same page rather than in a new tab, causing the user to lose their PAC page and possibly their search results.
It would be helpful to have a branch-level option to change that default to open a new tab instead. It could be included with the other configuration options under Profiles > PowerPAC > Page Header Options in System Administration.
Yes, it is possible to ‘force’ a new…
14 votes -
UPC Output in "Holds" Reports of Simply Reports
We often use the "Holds" reports of Simple Reports to watch demand on titles - especially the Hold Count report. It would be very helpful if UPC could be one of the output columns, so that we could copy it for media, which doesn't always have an ISBN in the vendor MARC.
Right now we have to output the bib record id, copy it and search in Polaris, then copy the UPC from there.14 votes -
Bib workform All Items list - Add navigation from open item workforms to next/prior item
Can development add a navigation option when someone has an item workform open on the All Items tab of the bibliographic workform to allow moving between item workforms without needing to close and manually open the next item?
One of the sticking points for technical services staff to adopt Leap is not being able to quickly navigate between item workforms to update barcodes while cataloging. In the desktop client, staff are able to use the View navigation options. Our current guidance is to use Bulk Change if the same revision needs to be made to multiple items or to use…13 votes -
Default bib & item records to read-only in LEAP
Create the ability to default to view-only when opening bib records and item records in LEAP. It is a major issue for acquisitions and cataloging staff importing MARC files or doing bulk edits to item records when someone else with edit permissions is just looking at a title or copy. The specific record affected doesn't even pop-up to let you know about it, instead you have to go check a separate report. For the MARC import report, that means a very long report to have to scan through each time. Having the default view be view-only, and requiring staff to…
13 votes -
Pick list prioritization based on floating load limits
Enable the pick list to prioritize filling holds in floating collections from branches where the number of items on the shelf at that location is the highest and/or over the load limit for that collection.
13 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 -
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 -
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…
13 votes -
Create custom circulation statuses
To be able to create customized circulation statuses that work for our system versus using the only given statuses. For example, the ability to create various Withdrawn - Leased, Condition, Relevancy. This would then offer additional feedback for staff when stats are ran to determine why materials were withdrawn versus they were.
13 votesFor the withdrawn example, does this really require custom circulation statuses? Or just a way to indicate/query the reason an item was withdrawn?
The reason Polaris has traditional restricted circulation statuses is because of our automated processes around certain statuses. Using the withdrawn example, our automatic Lost/Missing to Withdrawn processing would not know about custom statuses or which one to use.
If we reworked this enhancement as needing to be able to track/report on withdrawn reasons, we could plan for that within the automated processes.
- Don't see your idea?