695 results found
-
Ad hoc Patron Bulk Changes From Find Tool
Similar to the change in 7.6 for Item Changes, it would be beneficial to be able to make the ad hoc changes to patron records. Our libraries could easily change their Juvenile patrons to Adult patrons using the Find tool.
15 votes -
Polaris transactions will "run out" of space due to being an "int" data type
The Polaris Transactions database TransactionID is an int data type. This 2,147,483,647 means the biggest number supported by the database. In our busy system, we're about halfway through the available TransactionIDs as we're about to reach 1 billion. This field should be moved up to a bigint data type. Otherwise inserting new data will fail.
15 votes -
Search LEAP by username
LFPL would like the ability to search for patrons by their username in LEAP without having to use the SQL search
15 votes -
Run date specific report on Patron activity (not last activity)
I would like to submit the idea that Polaris offers the ability to run a report based on patron activity dates, and not their LAST activity date.
Currently, we can only run a report using "Last Activity". This is not helpful if trying to determine how many patrons were active in a given period because if they have had activity after the specified period, they would no longer be counted in the report.
There is a canned report under System > statistical summary, but it only looks at borrows, and would not count ILS card activity such as from a…15 votes -
Remain on current bib after refreshing Compare Tool
When you have several bibs to compare and have moved from the first one to a subsequent one and made changes, hitting the refresh button moves you back to the first bib for comparison. It would be helpful to stay with the bib you had open most recently on the compare side.
14 votes -
Easier checkout option of unclaimed items.
At times we have unclaimed items that the patron actually already picked up. It would be great if we could checkout out these items in "unclaimed" status directly from the patron's holds page on their account. This would be easier and less opportunity for error.
14 votes -
Prevent PatronRegistrationCreate from Reusing a Postal Code Record with the Wrong County
When
PatronRegistrationCreateis configured to allow creation of new postal code entries, the API should consider an explicitly supplied COUNTY when determining whether an existing postal code record is an appropriate match.Currently, if a ZIP code, city, and state already exist in the
PostalCodestable, the API will reuse that record even when the COUNTY supplied in the registration request is different.If a county is explicitly supplied, the matching process should require the county to match in addition to ZIP code, city, and state. If no EXACT combination exists, the system should create a new postal code record…
14 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?
14 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…
14 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…
14 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.
14 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.
14 votes -
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 -
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.
-
Flag a dated note to float to top
We would like to set a dated note to auto float to the top. In the old notes we always put important notes on top so that it catches a staff members eyes quicker than reading through all the notes. We would also like to flag it in a way that indicates it shouldn't be deleted.
Examples:
We note accounts to indicate someone is a current employee or former employee with staff privileges.We note to not waive fines on patrons that we have had a lot of issues with. No one needs to read through all of their notes…
14 votes -
Clean any invalid characters on import of MARC records
Recently, Ingram sent us a MARC record that caused the record to both not show up in LEAP and not be available for API calls, so it didn't show up in our discovery layer either.
It ended up being that there was an invalid character ([ERR] FOR XML could not serialize the data for node 'data()' because it contains a character (0x0019) which is not allowed in XML.) in the MARC record causing this.
It would be helpful if Polaris would clean any incoming MARC record of characters it knows will cause issues.
14 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.
14 votes -
Ability for staff to bulk change a patron's pickup branch
Staff would like to be able to bulk change a patron's pickup branch for selected (or all) holds on the patron's account. Be they holds already trapped, suspended or active. We often have patrons that move from one part of the area to another and need to change their holds to reflect their new pickup branch. Having to change one hold at a time is tedious.
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 -
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…
14 votes
- Don't see your idea?