8 results found
-
Polaris 7.7 - shelf-location output option, simplyreports
We currently run our lost and not paid reports under Patron Account > Patron Account List Reports in SimplyReports. Because shelf-location is not an output option, we manually enter it for each item in order for our shelvers to more easily complete shelf-checks. Can "shelf-location" be added as a report output option?
4 votes -
Polaris 7.5 - Multiple pickup location options for a single branch
Support for patrons to designate a pickup area or a location within the library where the patron would like to retrieve their holds (e.g., curbside, smart locker, drive thru). Current workflows require creating a new branch for tracking additional pickup locations.
3 votes -
Polaris 7.5 - Inactivity logout for Leap
We use shared Windows logins at our service points so it's easy for a staff member who was working in the back or out on the floor to quickly hop on a desk and help a patron. However, for obvious reasons each staff member has their own Polaris credentials. Staff are constantly tempted to perform transactions while logged in as a colleague because they have a patron standing in front of them waiting. It would be nice if an inactivity timeout could be added to Leap so that staff would be forced to sign in as themselves in situations like…
3 votes -
Polaris 7.7 - Provide a Load All option for record sets in Leap
I cannot think of a situation where, if I have a record set containing more than 250 items, it would be okay to proceed with doing things in that record set without loading in all of the items. It is typical to need to take a similar action on all items in large record sets but very challenging due to the 250 at a time limit. I just had to scroll and click more 27 times before I could embark on a bulk change. There should be a load all button.
8 votes -
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.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.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?