521 results found
-
Add a transmission method of 'E-Mail' to invoice creation
Add a Transmission Method of 'E-Mail' when creating an invoice. The current options are Paper, Fax, and Electronic. Many vendors now send invoices by E-Mail, not the US Postal Service. Invoices created by EDI transmissions are tagged as 'Electronic' as they should be, even if the vendor emails the invoice to us. What I would like to do is be able to identify an invoice that was emailed to us by a non-EDI vendor. I know it's technically a paper invoice once I print it; but it was received by email and should be identified as such.
3 votes -
Leap lockouts due to incorrect password entry should have a unique error message
We had a front-line staff member contact us because he was getting a "The domain, username or password is incorrect" error message when he tried to log in to Leap. Support was able to tell us that he was locked out because he had incorrectly typed his password five times. They confirmed that the error message that will be shown when this happens is "The domain, username or password is incorrect." Not only is that error message text factually untrue, it is identical to the error message that a staff person sees if their password actually IS being entered incorrectly.…
23 votes -
Weeding template criteria should include Last circ date option
In our consortium, libraries weed items based on their circulation almost exclusively, not based on how new or old they are or how many lifetime circs they had. The most important piece of information to them, the Last circ date, however, is missing from the weeding template criteria. We are aware that you can add dates to the power search for inclusion criteria, but those have to be specific dates, so they can't be reused as criteria several months or years later - you'd have to continue remaking the criteria with new dates each time, which isn't convenient or efficient.…
34 votes -
Enhanced Patron Privacy (UDF)
Patron Privacy is becoming a much larger issue. We currently use a UDF to hold our Patron ID.
We'd like to suggest that having the ability to create some way to collect and keep private patron data such as an ID or other PII would be ideal. And having this information encrypted in the database would be preferable as well.
Being able to prevent this information from always showing, would be a benefit and even having the ability to only show a part of that information, such as the last four digits or something similar, would be useful.
5 votes -
Collapse Name on Identification Fields
Staff have suggested that the Name on Identification area of the Leap registration form be collapsable, so that it will only be accessed if absolutely necessary. This measure would be an extra step in ensuring a patron's privacy, if a staff member accessing the record doesn't need that particular information.
4 votes -
Select multiple items to delete
From the Leap Serials Check In screen, include the ability to select multiple dates for deletion.
14 votes -
Add support for a patron's preferred pickup area in Polaris
Polaris supports a preferred pickup branch for patrons. This request is to extend that support to allow the patron to set a preferred pickup area.
Many patrons prefer to 100% always use a particular pickup area, for example outside lockers. So, they shouldn't have to select that area everytime they make a request.
This would allow them to set their own preferred pickup area the way they can set a preferred pickup branch. This preferred pickup area should also be used when the staff bulk places a title on hold for a batch of patrons, again the same way the…
19 votes -
Allow Username to begin with number
It seems unnecessary to force the Polaris Username field to begin with a letter. We would love for the Username field to have the ability to begin with any character.
3 votes -
Fund Hierarchy Report
Currently, the fund hierarchy report organizes at the Organization level by Org ID. This means that as new organization levels are added they drop to the bottom of the list, and I'm often looking at this from an alphabetical perspective. It would be helpful to have the option to organize the output alphabetically instead.
9 votes -
Reverting to what the bibliographic record (or any authority record for that matter) was when it was last saved
When you want to get rid of a bunch of edits, but only the ones made since the last save, it saves time to have just one button to click on. For example, when you want to validate juvenile headings, you need to take out |v Fiction for each heading. If they are all good, you want it back in each heading.
13 votes -
Expose web-based System Administration APIs
For larger library systems that need to continually create new staff members, being able to access the APIs would be a big time saver. That would allow, among other things, to automate that task.
3 votes -
Add last patron modification date and modifier name to Patron Reporting
Adding the patron modification date and the name of the last modifier of a patron record would allow staff to narrow down when records were modified and by whom. The ability to track these changes would be particularly useful to Outreach staff who may need the statistical information about patron records they modified while working off site. Ideally, this addition should be added to the report outputs in SimplyReports and added to Leap as well so that public service staff can easily access this information. In Leap, adding Last Modification Date and User to the list of keyword fields in…
10 votes -
Generate Alert when Applying An Adult Patron Code for Minor Applicant
When creating a new account in Leap, it would be helpful if when the date of birth was less than 18 years from the registration date AND a patron code for adult patrons was selected, that an alert would display prior to saving, as we see for missing DOBs or other fields.
It should not be a hard block, as it is possible for someone under 18 to register as an adult, but the alert would catch attention to remind staff to confirm/correct during the registration process.
7 votes -
System auto-capping late fees/fines
Our system does not currently have late fees on most of the collection. But for the collections we do, we have a max that we will charge in late fees for items returned on the same day per patron. It would be nice if we could set up for the system to automatically waive fees for overdue items that exceed that amount.
2 votes -
Add ability to remove vendors
We have a long list of vendors and would like to clean it up, removing any who we no longer purchase from. This can't be done because of the links and layers in Acquisitions to attached purchase orders and invoices. It would help with clutter if there was a way to delete these suppliers or hide them in some way.
36 votes -
Weeding Record Sets need to have Picklist Functionality
Currently, when we turn over weeding lists to staff to pull, they manually mark 'not on shelf - NOS' if they don't find the item. In order to make the new weeding list functional in LEAP, we need the weeding record sets to have the same sort of functionality as a PickList - a column where staff can either mark the item as 'Not Found' or "missing". Ideally the circulation status could be changed to missing at this point, removing the need to manually change these items in the system and remove them from the record set.
Related to idea …
32 votes -
neunaberb@nampalibrary.org
Acquisitions - need the ability to limit/filter search to Fiscal Year of Suppliers for Invoices or Purchase Orders. Currently, if we look at a Suppliers order history, or invoices, we see everything since we migrated to Polaris.
Sometimes, we need to see how much we are spending with a specific vendor and/or need to see an on-order list with a supplier.7 votes -
subject headings to browse
Polaris Leap--Be able to use subject headings to browse/search while in Leap without having to go into the PAC.
13 votes -
Leap - Item specific hold, checkout pop-up
Currently in Leap when checking out an item - if that item has an item specific hold on it for a patron - it does not provide a pop up or warning if you try to check out that item to another patron. In Polaris it would warn you that there was an existing hold on that copy. This was a very useful notice for circulation staff.
10 votes -
Ability to Undo Record Merge
This undo function would provide the ability to separate two records that were accidentally combined so they go back to being attached to their original, individual POs, have their original items attached, and have their original hold lists attached.
Example: If a regular print record and a large print record for a title with a list of holds on each were accidentally combined, catalogers would have to split the large print items out by creating a second record and move the appropriate “on order” items to that record. The newly created record wouldn’t be able to be linked back to…
42 votes
- Don't see your idea?