27 results found
-
Polaris 7.8 - More Hold Routing Sequences
Add more (optional) Holds Request to Fill Routing Sequence tables.
Idea Value
As libraries work together more and more in order to provide the best possible services, it's important that Polaris provide needed flexibility in holds routing. This is especially important for consortia (many of which are growing as independent libraries experience budget crunches and are looking for efficiencies). The current primary/secondary RTF and different grouping options are good, but insufficient as material delivery challenges make moving holds across libraries more costly/difficult (especially if there are large areas involved).25 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 8.0 - Better Handling of "Display" Items
: In its current configuration, a "display" shelf location can be used to indicate an item has been placed on display. However, changing this shelf location is a semi-permanent change and when the display comes down staff must change the location codes, either manually or through a record set, to the original location. Because displays are often very popular, this often results in items being checked out and returned. Without markings on the books that indicate they're on a temporary display, these items are often reshelved in their original location while their Polaris record indicates they're still on display, hindering…
153 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.8 - Count Renewals Separately- how many patrons actually checked out an item
For collection development purposes, we need to know how popular an item is. Right now, renewals from the same patron counts as a circ. It would help to have renewals counted separately so that we can have an accurate circulation stat. For example, our YA Manga (33090005890258) shows that lifetime circulation is 5 but it's actually 2 patron checkouts with 3 renewals. This number makes it seem that this manga is more popular than it is. New items are easier to count right now but as time passes, looking at the history will become more time consuming.
Idea Value
Time…89 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?