658 results found
-
Please add Mackin to Polaris Libraries EDI suppliers
Kitsap Regional Library wish to engage in EDI based acquisitions with this supplier
10 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.
10 votes -
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.
10 votes -
Save patron name when deleted on holds to action
- Patron has a held item
- Held item is cancelled
- Then the patron record is deleted
- The hold on the holds to action will have no patron name shown.
This means that staff have no real way to know where their hold is on the hold shelf (holds are arranged on the shelf by patron name) to be removed. This was originally entered as a bug, but it was closed as a bug because it was working as designed.
10 votes -
Show workstation and staff information for posted patron notices
When some notice types are posted, they show up in the item record history. But not all notices show up there, for example, printed hold notices do not show up there. It is also difficult, for example, if you want to find out who printed a fine notice to be able to locate that information because it isn't always tied to an item record.
This request is to add to the notice history information on the user and workstation that posted the notices to the database. There is very miniscule information in the notice history already.
This additional information would…
10 votes -
Allow libraries to reset staff accounts that are locked out
There are a few scenarios where staff don't remember their exact password and get themselves locked out of LEAP: they are adjunct staff who work infrequently, they have just returned from a long vacation, or simply have brain freeze. In these cases, they open a support ticket, and I would like to be able to reset their account so that they can log in immediately, the same way I can now clear an object lock on an item that someone needs to use. Thanks for considering!
10 votes -
Allow favicon to be set for leap as a staff visual cue
You can set the title bar color and the login message for Leap. However, it would also be nice to have the option to set the favicon so when you have a test, development, and production server open, you could use a favicon to more quickly distinguish between them in your open tabs.
10 votes -
Improve Leap quick search for complex patron names
The Leap quick search could do a better job of searching Hispanic names. Often, patrons consider their first two names as given names, not as first and middle, which makes it difficult to search for them when they come in without their cards. For example, if I search for Luis Miguel Paco Sanchez using all four names, LEAP finds the patron. If I search for Luis Paco Sanchez or Luis + either last name individually, LEAP will not find the patron. If I search for Miguel Paco Sanchez, LEAP finds the patron. In this example, Luis Miguel is the first…
10 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 -
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.
10 votes -
Update Language Field in Item Bulk Change
The Language field was added to Polaris in 7.4 (I believe). The only way to update the Language field is to manually update each item record manually. As you can imagine, that is very time-consuming. It would be ideal if our Collection Management department could pull the appropriate item records into a record set and then do a batch update of the Language field.
10 votes -
Update Bulk Waive schedule in LEAP - add reoccurring
Provide an option to schedule bulk fee waive in records on a reoccurring basis, such as daily, monthly, or other specified intervals. At the moment you can only select one date and run it once.
10 votes -
Allow PolarisAdmin sidebar to be pinned
Unlike the Leap sidebars, you can NOT pin the PolarisAdmin sidebar, making it more difficult to move around the system versus the desktop SA.
10 votes -
Clearer messaging when an invalid barcode is used in a password reset
A patron was using their former barcode to try to do a password reset, and before we realized what the issue was, the system told them they 'had no email address' associated with that account. It would be more helpful if the system told them the barcode was invalid or, even better, that they were using an old barcode.
10 votes -
Ability to create reports with charts and graphs
I came across this report using a bar chart to reflect the Total Number of Items Added. Our staff would love the ability to create statistical reports and display them as bar, line, and or pie charts.
10 votes -
Include patron preferences such as billing notifications in PAPI patron update/create
The Jacksonville Public Library leverages the Polaris API to manage student records. Currently we have to take an extra step in the LEAP UI to set the communication preferences. We don't bill students or send their accounts to collections, so we have to do a bulk update of all the records with the UI after already touching every record with the API. This is cumbersome because there are over 100,000 student records that need to be updated. Most updates are smaller, but at the start of the school year we do a full refresh.
We would like to be able…
10 votes -
Improve Hold Duplicate Detection
Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.
This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like…
10 votes -
Allow volume level AND item level requests
We were told that in order to activate volume level requests in the PAC and in Vega, we would have to turn off the ability for item level requests to be placed, since it's an either or setting (see attached). However, we need to be able to offer our patrons both options. In the case of volume level requests, we can't have patrons getting a random volume that they might not even want when they place a title level hold. Since we also have patrons that use item level requesting, we can't just turn that off in favor of volume…
10 votes -
Addition of "PA" Extension in Item Info Response
I propose an enhancement to the SIP2 protocol: including the "PA[PickupAreaDescription]" extension in the Item Info response (18). Currently, this valuable extension is only available in the check-in response. The key issue with the current setup is that when systems attempt a check-in to obtain the "PA" value, the check-in process completes, which can prematurely finalize item handling without allowing the system to decide if a check-in should be initiated based on the item's status or location.
Integrating the "PA" extension into the Item Info response would allow library systems to efficiently determine whether a check-in is necessary for items…
10 votes -
Update Block in PAC/SIP to include fine limits
Currently, when the If patron is blocked: Block in PAC/SIP option under the Staff Client and PAC tab of the Hold Options parameter is enabled, patrons are only blocked from placing a request if they exceed the hold limits for their Patron Code.
We would like for this blocking to also include the 2nd level fine amount, similar to how their request would be blocked in the staff client/Leap when the Block in Staff Client option is enabled.
10 votes
- Don't see your idea?