676 results found
-
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…
13 votes -
Filter by Patron Selection Only in Outreach Services Utility
It would help speed things up if the way we can filter by Active and Inactive patrons for Outreach could also be done with the Patron Selection Only checkbox with something like a yes/no drop down. We could more easily focus on patrons that need the extra attention.
3 votes -
Patron Import Process (LEAP) adding Polaris Username field
Adding the ability to add / update the Polaris username field as an alternative barcode for students/patrons would be hugely beneficial in the import process. This would allow us to have a student ID as a barcode and a former library barcode for patrons to use at the expresscheck.
11 votes -
Add Patron Name to item history
Make it easier for staff to quickly view the borrowing history of an item by including a column that shows the customer's name. Having to click on the PATRONID is meaningless to staff and an additional unnecessary click.
5 votes -
Hold History report where you could enter a Bibliographic Record ID
If Simply Reports had a Hold History report, where you could enter a Bibliographic Record ID and then see the history of hold requests created for that bibliographic record -- it would be most helpful when trying to see why an item wasn't automatically renewed, or was blocked from renewing.
12 votes -
Add an Invoice Status of 'Ready to pay'
Add an Invoice Status of 'Ready to pay' or 'All items received' in the Find Tool - Invoice - search filter. This will allow EDI invoices to be filtered to ones where all items have been 'received' and make the invoices ready to 'pay' easier to find
9 votes -
Parent/responsible party information in registration
We would like an optional field for parent or guardian information in the registration form.
We don't require parents to have library cards if they only want their children to have cards, and we have instances where only children can qualify for free cards (school district vs county lines). It would be great to include a parent name, DOB, and DL# in the child's registration without using fields that prompt duplication notices.
6 votes -
Place Holds from File
Items can be added to a record set via a text file. This is very convenient and quick. It would be helpful to be able to place multiple holds via a text file. I would like to be able to upload a text file via the more menu (just like adding to a record set), which would then place a hold on each item in the text file.
This way a group of items a user wants to put on hold doesn't need to be put in a record set first, cutting out an entire step.
6 votes -
Autowaive Fine for Returned Withdrawn Items
We would like, when items with a Withdrawn status are returned by patrons in a good enough condition to still circulate, for the replacement fees associated with the item to auto-waive in the same way that items with a Lost status can auto-waive. This would prevent confusion at the circulation desk and streamline the check-in process.
11 votes -
If Leap quick search doesn't find a record, don't clear the text
A staff member asked us to post this. When using the quick search in leap and typing in a query does not lead to a record, the text should stay inputted so the staff member can edit their query as opposed to having to retype it all over again when trying again.
32 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 -
Ability to limit the "Number of days past first available" setting to the branch level only.
The "Number of days past first available" setting was developed specifically for the issue where libraries would like the new item's hold requests to be limited to only patrons registered at the item’s assigned branch and other branches associated with the same parent library for a specified number of days. We would like to try this workflow, however, it won't work in our system as all of our branches are under the same library organization.
3 votes -
Add Item Ad Hoc Bulk Change to Polaris client toolbar
Currently Item Ad Hoc Bulk Change is only available on mouse right-click. Please add a toolbar button and/or a keystroke shortcut.
9 votes -
Vendor-Profile SIP2 Due Date Formatting
In the i-tiva 3.0 dial-in process, there are menu navigation issues caused by a SIP2 Due Date (AH field) formatting issue. These issues cause the dial-in process to fail.
In SIP2 message 18 (Item Information), Polaris is currently returning the Due Date in the following format:
DD/MM/YYYY HH:MM:SS
Because the SIP2 standard does not define or enforce a required date format, i-tiva relies on vendor-compatible parsing. i-tiva has confirmed that this specific format is not parsed correctly and results in call-flow failures.
i-tiva supports the following date formats, any of which would resolve the issue:
• DD/MM/YYYY
• D-M-YY
•…2 votes -
Add 'Hold Activated/Created" to item history
It would be useful to have in the item history when a hold was activated. I had an instance where an item was put on hold for the wrong account, and it would have been useful to see who had placed the hold or where it had been added. I figure you can see this from the hold record, but the staff member who had received the accidental holds cancelled them before we got a chance to look at it.
10 votes -
Include ‘Patron Statistical Code’ in Leap Patron Information Panel
Current Situation:
We currently have an unwieldy number of Patron Codes, which we aim to streamline by shifting toward greater use of Patron Statistical Classes. This is possible because many of our existing Patron Codes have minimal or no functional differences. However, Patron Statistical Classes are not currently displayed within Leap’s Patron Info (‘I’ button) panel, requiring extra steps for staff who frequently need quick access to this detail regardless of which patron registration view they are currently in.Suggested Enhancement:
Add the Patron Statistical Code directly below the Patron Code within the Leap patron information (‘I’) panel. This would…9 votes -
Add a copy button to supplier records in Leap
The ability to copy existing records makes record creation more efficient. In the Client, staff have the ability to copy an existing supplier record to create another one with similar information. This happens when staff have multiple supplier records for the same vendor because they have separate account numbers. A copy button is not in the supplier record workform in Leap yet. It should be added to the actions drop-down menu of the supplier record like it is in other record types. This will allow staff to feel like the transition to Leap will be easier since it is a…
46 votes -
Ability to Suppress Custom Data Fields
In Polaris System Administration, there is existing functionality to suppress UDF 1–5 in the Web App (Leap), which allow the fields to be written to, but prevents staff from viewing or editing them.
We would like to request that the same suppression functionality be extended to Patron Custom Data Fields. Currently, the only available option is to enable these fields, which simply turns them on or off. This lacks the flexibility we need.Adding suppression capability to Patron Custom Data Fields would greatly enhance our ability to manage sensitive or system-used data more effectively.
3 votes -
Make it easier to filter the list of SQL Searches in Find Tool
We have dozens of SQL searches, however it can be hard to find them. They are presented in an alphabetical list, but over the years our naming isn't always consistent. It would be great if you could filter the name drop-down like you filter can in other areas of Leap.
So, for example, if I typed "volume" it would show many any SQL search with Volume in the name. Bonus points might be if we could also be searching some of the SQL search contents itself because maybe I want to find all SQL searches that query a particular field…
9 votes -
Ability to Merge Supplier Records
I have occasionally found multiple supplier records for a single supplier account, whether added by mistake or under multiple names (Thomas Klise and Crimson, for example). When these supplier records are accidental duplicates, I believe it would be helpful to have the ability to merge them (retaining all linked POs and invoices) to maintain one supplier record per account.
29 votes
- Don't see your idea?