626 results found
-
Add temporary shelf location to PAPI
BibHoldingsGet, SynchItemsByBibIDGet, and SynchItemByIDGet all return the shelf location of an item, but not the temporary shelf location.
3 votes -
Allow filtering bib search by stat code
When doing a bibliographic record search, you can filter by Collection (which is only assigned at the item level) but not by Statistical Code (which is also only assigned on the item level).
It would be helpful to have the option to filter by stat code as well.
5 votes -
Add "patron barcode for damaged item" option in SimplyReports
We would like to see a "Patron barcode for damaged item" option as an output column in SimplyReports, similar to the one available for Lost items called "Patron barcode for lost item". This would help us when running reports on Damaged items.
16 votes -
"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…
34 votes -
Automatic Posting and Sending of OverDues to Library Directors
Post OverDue notices to the database without printing them. We have libraries that are not regularly printing and posting to the database overdue notices so items move in the system to missing and withdrawn before some libraries ever send out a notice. Some libraries haven't sent them in 1-3 years. So, I want to post them and then email a pdf on the overdues automatically on the first of every month.
12 votes -
Display an error message when quick search cannot find anything due to network issues
When staff use the quick search box during busy times, the results come up empty. Sometimes they know they have the items and will wait to try again, but other times they assume no one owns the title and end up creating a duplicate record.
When searching is affected by network performance, Leap should be handling that exception and displaying an error to the user. Blank results are a result and it is confusing people.
7 votes -
Leap: quickly copy line items
One impediment for our processing staff in moving to Leap is the lack of the ability to quickly copy a line item in Leap (here's the process in the client: https://documentation.iii.com/polaris/7.6/#PolarisStaffHelp/Acquisitions/PAorder/Copy_a_purchase_order_line_item.htm)
The same process in Leap involves several more steps:
1.Go back to the PO
2. click new line item
3.fill out line item details
4. click on segments
5. click new segment
6. fill out Collection Code and FundA quicker way to get through a PO would be if we could add the same segment to all of the line items at once, e.g click the check…
21 votes -
Allow staff to view read-only records without needing to cancel the override pop-up
For SHRs and Authorities, if you have read-only access to those records and try to view them, you get an override pop-up. This is happening because it is attempting to open those records in Write mode. To VIEW the record, you have to hit cancel, which is confusing for staff.
For Bib records, it does not work this way. For bib records, you can view them and then if you don't have permission to write or modify them, you get the pop-up when you attempt to save the record.
In the item record if you have view only permissions, it…
17 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.
9 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.
10 votes -
Import Reports in spreadsheet format
It would be very helpful to have an option to view Import Reports for both bibliographic and authority record imports as a spreadsheet, as well as the existing PDF.
This is mostly true for the records (and associated errors, warnings, and messages) themselves, rather than the more general import information (duplicate detection criteria, MARC validation rules, etc.). This would be helpful for quickly flagging errors, duplicates, and other areas that need attention without having to scroll through a lengthy report.
3 votes -
Recall function
Create a recall function that is separate from the holds queue so Technical Services can get items back (for relabeling, for weeding, etc.). Technical Services often use internal cards to place holds on a specific barcode. This sometimes work, but has a few drawbacks:
1. The hold disrupts circulation (renewals, other holds, potentially in-transit)
2. If the item goes into a status that cannot fulfill holds (e.g. item becomes LOST), the holds will go back the queue and be reassigned to another item on the bib. Technical Services usually needs the specific barcode, not just any item on the bib.…
57 votes -
Prevent patron's with expired cards from placing holds
Currently, our patrons can still place holds when their card is expired and then come in to get their hold and don't realize they need to verify their address so we can renew their card. Blocking patrons from placing holds until their card has been renewed and giving them a pop-up explaining that their card has expired, would be great.
18 votes -
Add the Ad Hoc Bulk Change Button to POs and Invoices in Leap
Acquisitions staff frequently need to bulk change item records for a specific order. This is commonly done for orders that were placed manually instead of using EDI or if Polaris created item records using the wrong template. In the Client, it can efficiently be done as an ad hoc bulk change by opening the list of items that are linked to a PO or invoice. The ad hoc bulk change button should be added to the tab that contains the list of item records linked to the PO and Invoice in Leap in order to make this process more efficient.…
62 votes -
Option to Display Description and Comments for MARC Tooltips
It's possible the Description and Comments configured for MARC validation display somewhere else already, but it would be nice if there were a couple of buttons to display that data in the MARC tooltips. The Description would be helpful for any tags that aren't used regularly or for staff with limited familiarity with MARC formats while the Comments could be useful in communicating local cataloging policies. Bonus points if we could allow staff with the appropriate permissions to edit the Description and Comments directly in the tooltip. It's not a particularly good example, but you could include something like "Please…
9 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.
30 votes -
Configure Notification Options Based on Patron Attributes
Currently, notifications in Polaris can only be filtered by branch. For example, one branch can enable specific notifications and another can disable them. We would love the ability to apply more granular filtering to determine which patrons receive certain notifications.
A workflow for us is billing notifications. Our library policy exempts certain patrons from billing based on their Patron Code. Because Polaris does not currently allow notifications to be filtered by Patron Code, we must manually work around the existing workflow to align with our policy.
We would love the ability, within SA, to filter notifications by patron attributes such…4 votes -
Expand Bulk Change to allow editing
Currently, Bulk Change allows staff to replace existing information in free-text fields, and add to the beginning or end of the field in some cases. However, existing text cannot be edited.
For example, if a group of item records need the volume numbering changed from “v.” to “vol.,” Bulk Change cannot update all the items if they have different volume numbers. Staff have to replace “v. 1” with “vol. 1,” then do all the v. 2s, then v. 3s, and so on. Similarly, if a library discovers that some of its records have incorrect diacritics, each word must be changed…
58 votes -
Leap: Popup/Prompt for Patrons with Blocks
Currently, in the desktop client, when beginning a checkout transaction with a patron with blocks, Polaris will show the blocks in a popup menu, prompting the user to continue or cancel before the transaction can occur. There is no equivalent feature in Leap, meaning that staff can miss if a patron has blocks unless they are vigilant and view every patron's blocks before every transaction. Is it possible to have the option to display a popup/prompt for patrons with blocks, as the desktop client currently does?
2 votes -
Allow Patron Merge Directly From Duplicate Patron Records Pop-Up
Currently, Leap will surface any potential duplicate accounts when you go to save a patron record based on the configured criteria. Unfortunately, it's not particularly actionable and, while it is nice that you can click the other account names to pull up the full record, it requires a lot of back and forth to confirm information on one account or another before performing an independent Merge action... which is to say that most staff aren't likely to perform an account merge in the moment and probably won't come back to it later... I think this could be remedied by allowing…
2 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?