28 results found
-
Polaris 7.7 - Store item due date in the check-in transaction
This might be a little specific, but I am proposing that the item due date should be stored as part of the check-in transaction in the Transactions Database in SQL.
Idea Value
This seems like a relatively small change to the SQL tables, but it would allow some information to be more easily gathered. For instance, I recently received a question where I was trying to determine if there's any trend in what triggers the return of overdue material (e.g. first/second notice, the bill, or collections). If the due date was included in the check-in transaction, I think I would…17 votes -
Polaris 7.5 - "Declared Damaged" option needed YES.....
Patrons often have an item that is damaged and want to pay to have it replaced. At the moment the only choice we have is to declare the item is lost, so the patron can be charged and pay for it right then and there. The "Declare Lost" option is technically not true since they do have the item in their hands. I would like to have a choice of both "Declare Damaged" and "Declare Lost."
Idea Value
The option "Declare Damaged" in the case of a damaged item would be more accurate since the item is truly NOT LOST,…42 votesDeclare Damaged feature included in Polaris 7.5 release
-
Polaris 7.7 - Provide a way to check out/in items to a patron through the Polaris API
Ability to check out items to patrons; check in items
The Polaris API does not provide methods for checking out (issuing/charging) items to patrons.
It also doesn't provide methods to check in (return/discharge) items after being returned to the library.
Requested improvement:provide a way to check out an item to a patron through the Polaris APIprovide a way to check in an item through the Polaris API
Idea Value
This would allow libraries to interface with 3rd party apps which provide check out and check in functionality. These types of services are more relevant than ever now that libraries are…29 votes -
Polaris 7.7 - Make filter sticky when searching Leap
When searching in Leap, any applied filters are automatically discarded when the search box is closed. It would be beneficial to have the option to make filters stick from search to search. A good example is in the case of consortia - it would be extremely helpful if the patron assigned library filter would stick so staff would always begin an initial search for patrons with their library filter in place.
Idea Value
Time savings would be gained if staff did not have to select a specific filter each time a search was conducted - such as selecting the patron…66 votes -
Polaris 7.7 - Ability to select multiple items/chunks of items in LEAP
When working with a list of bibs, items or patrons, ability use ctrl and shift keys to select a chunk of sorted records (without having to checkmark each item) to add them to a record set. If other web tools like gmail can do this for email deletions, it seems we could do this with LEAP too.
Idea Value
Saves time.85 votes -
Polaris 7.6 - Bulk waiving of old fines
We have a lot of very old charges for fines on patron accounts. We know we're never collecting on these and would like to waive a bunch at once - hundreds, maybe thousands. So we could never open each patron record individually and waive the fines manually. It would be very helpful if there were a batch process of some kind that would allow us to waive fines based on certain criteria:Reason for the charge - late fee (fine) vs. lost or damaged item, etc.Date the charge was incurredPatron code of the customer (adult, teen, child, etc.)There are probably other…
49 votes -
Polaris 7.7 - Make 'non-blocking' circulation blocks optional
Many of the blocks that pop-up during transactions at the circulation desk are more informational than related to rules. Separating 'blocking blocks' (patron is over the fines threshold) from 'informational blocks' (patron has a hold available) and making the latter optional would help libraries improve accuracy and efficiency at the circulation desk.
Idea Value
Having unnecessary blocks popping up during circulation transactions takes staff and patron time and trains staff to click past blocks without reading them closely, making it more likely that important messages will be missed and ruled will be overridden. Giving libraries the option to include or…43 votes -
Polaris 7.5 - Enable volume-level holds for serials
For serial bib records (e.g. travel guides) if the items have their volume information in the Volume field, only item-level holds are possible. We need volume-level holds. For monograph bibs, volume-level holds can be placed with no problem. We've heard other libraries use workarounds to deal with this: coding the bib's leader as monograph instead, or only using monograph bibs for serial titles. Either would cause its own problems, so we'd like to see volume-level holds work the same for serials as they do for multivolume monographs.
Idea Value
Especially in a consortium like ours, this would help users get…22 votesVolume-level holds for non-integrated serials feature included in Polaris 7.5 release
- Don't see your idea?