692 results found
-
Transitioning claims returned to Lost after a set time and adding a bill
We would like to have to option for claims returned items to automatically go to Lost after a set time and adding bill to the patron.
Idea Value
This would take out the manual process of chasing up items that have been put to claims returned/never had.16 votes -
Add Custom Data Fields to Item Records
Patron records have 5 UDFs and 10 Custom Data Fields – item records have none of these. As a result, many libraries end up doing some weird stuff with the Name of Piece and Temporary Shelf Location. This idea would add 10 or so custom item record fields that libraries can choose how they would like to use.
Ideally, fields would be capable of multiple data types including freetext, Boolean, date, or numeric. In a perfect world, it could also support a drop down list like the UDFs! The fields would also be searchable in the find tool, just like…
24 votes -
Allow bib bulk change steps to be applied to import profiles
Imagine the possibilities if we could automate the process of bulk changes to bib records as part of an import profile.
Other ILS systems offer robust manipulation of bib records upon import, but this is missing from Polaris.
By allowing bib bulk changes to be stored in templates, just like item bulk changes, we can streamline the process and save valuable time. Imagine having a set of predefined steps for importing bibs from specific sources or of certain record types. It would ensure consistency and accuracy, eliminating manual effort.
- Allow bib bulk changes to be stored in templates like item…
38 votes -
Go back to same place in PO
Unless I'm doing something wrong, when I am in a PO and go into a PO LINE to check ISBN, discount or whatever, I hit save and go back and it takes me to the top of the PO. Some of my PO's are really big so I'd like to know how to just go back to the spot I was at before instead of the top.
42 votes -
Registration/Renewal period based on patron code
We would like to be able to edit the default registration/renewal period based on the patron code rather than just based on the branch. We have certain patron codes that should renew for 1 year instead of our default of 3 years, but they don't have a unique branch in Polaris so we have to change the registration period each time we create a patron, and we have to change the renewal period each time we renew them, leaving more room for error if those steps are missed.
74 votes -
Add ability to create status codes
We would like to be able to create status codes. We have renamed some we don't use to make them useful, but that is limited. We use in-repair for multiple problems and it would be better for our staff to be more specific. For example, it is used for items with bedbug damage that will definitely be leaving us and it would be good to know that at a glance, as opposed to DVDs that need to be resurfaced and are also in-repair along with books with missing pages or water damage, etc. So, instead of just the one status,…
43 votes -
Change Login Branch in Leap (without signing-out)
Currently if we need to change the branch we're logged into in Leap we need to sign-out and log back in. This can be disruptive if we have records opening we're working with that would then need to be re-opened. It would be handy if there was a way to do this without signing-out and back in, in a way that would allow records to remain open.
Admittedly I don't think this would be helpful for the majority of staff, likely more administrative roles that need to perform activity across a range of branches. But it would be a nice…
45 votes -
More granularity in record set access, modification, and deletion
As Polaris currently exists (v7.3 at my library), User 1 wants to share a bibliographic record set with User 2 and User 3. In order to do this, they have to change the record set's owner from User 1 to Organization 1. But this allows all members of Organization 1 with the permissions "Cataloging Record Sets: Modify" and "Cataloging Record Sets: Delete/Undelete" to make changes to that record set. Let's say that at some point down the road, User 4 sees this bib record set owned by Organization 1 and thinks they're being helpful by updating or deleting it. They…
42 votes -
Run date specific report on Patron activity (not last activity)
I would like to submit the idea that Polaris offers the ability to run a report based on patron activity dates, and not their LAST activity date.
Currently, we can only run a report using "Last Activity". This is not helpful if trying to determine how many patrons were active in a given period because if they have had activity after the specified period, they would no longer be counted in the report.
There is a canned report under System > statistical summary, but it only looks at borrows, and would not count ILS card activity such as from a…15 votes -
Not-Supplied status for Holds - change back to on hold if item becomes avaliable
When an item hold has the status of Not-Supplied, if this item then becomes available eg if a a lost item is returned, the not-supplied status doesn't automatically retrigger the hold.
Currently you have to go in and manually reactive the hold.109 votes -
Book Club Holds
We'd like to have a way to place multiple holds at once. The existing multiple holds option doesn't quite do that as it still requires re-entering the title and selecting it for each copy needed while in the holds area of an account. For a book club, for example, it would be much faster and easier to select a title to hold and have a way to say we want 15 copies from this bib record, rather than have to select it title 15 times.
107 votes -
Leap: Print from Find Tool
We'd like the ability to print from the Leap Find Tool, like we can from the client Find Tool.
61 votes -
Unrelease a PO in Leap
Acquisitions staff would like the ability to un-release a purchase order. Currently, once a purchase order is released, you are unable to go back and make any changes if you realize you made a mistake. Instead, acquisitions staff are having to delete the entire PO and start a new one from scratch.
57 votes -
Show branch and barcode for item-level holds in Leap
Our Cataloging staff frequently have to place item-level holds on multiple items from the same bib record when making updates to the collection. Currently in Leap, these holds display in the patron's account with only the title, format, and call number. From this information it is impossible to tell which specific items have been placed on hold. Including the barcode and the assigned branch of the item would make it easier to tell different item-level holds apart when the items all have the same title.
36 votes -
Save collection and fund when adding segments to purchase order line items in Leap
Currently, when adding segments to a purchase order line item in Leap, the collection and fund reset whenever a new destination is selected. Since we are frequently adding multiple segments with the same collection and fund but different destinations, this forces acquisitions staff to have to scroll down and select the correct collection and fund for each segment. If the first selection of collection and fund "stuck" for each purchase order line item, it would be much faster to add multiple segments for items going to different destinations.
60 votes -
Full support for emoji in Polaris Label Manager
Many libraries like to call attention to their genre fiction through the use of spine label stickers and icons. For instance, science fiction items may feature an image of a grey alien, mysteries have a magnifying glass or a skull and crossbones, and westerns use a cowboy or a horse or something similar. The thing is, there's no reason a library couldn't print the icons on the spine labels themselves using emoji.
👽 = Science Fiction
🐴 = Western
💀 = Mystery
🦄 = Fantasy
🏰 = Historical Fiction
And so on. However, the Polaris Label Manager barely supports any…
67 votes -
Polaris API Making Lists Sortable By Title
A customer contacted us recently and asked if we could possibly add a feature where lists can be sorted alphabetically by title. Since this functionality isn't currently available in the API, I wonder if it could be added?
Mark W. Jarrell
mjarrell@richlandlibrary.com
Web Applications Developer | Richland Library
1431 Assembly St. | Columbia, SC 29201
Access Freely at RichlandLibrary.com.9 votes -
Display additional record types in "Recent" workform tracker
The "Recent" tab in the Leap Workform Tracker lists recently-accessed patron, item, and bibliographic records. Now that additional record types are available in Leap, it would be helpful to have additional record types listed in the "Recent" tab, including but not limited to:InvoicesPurchase OrdersRecord Sets
Idea Value
The "Recent" tab in the workform tracker is a helpful tool that allows staff to easily reopen records that have been recently closed. Adding additional record types to the recent tab would be helpful for all staff, especially technical services staff that are transitioning to Leap.78 votes -
Prevent patron registration date from being deleted
I'm repeatedly finding instances where a patron is missing their registration date. At first, I thought it was migrated data, but after updating those records, I discovered it happening over and over. Please prevent the registration date from being deleted.
Idea Value
We have some third-party applications that break if there isn't a registration date. Also, we use that date for statistics and to narrow down results.33 votes -
Remove Branch Requirement from Patron Bulk Change
Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.
This was previously submitted in the old enhancement process:
"Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can…
24 votes
- Don't see your idea?