Settings and activity
111 results found
-
86 votes
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment 
Wes Osborn
commented
Do you have hold cancellation notices turned on in your organization? Those are slightly lacking right now because there is a no reason listed on the notices, but in theory that should be coming soon: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/1098-enter-a-reason-when-cancelling-holds-
-
19 votes
An error occurred while saving the comment Wes Osborn
commented
Also, I would caution about leaving the current field by field editor the default. I think that should be a user toggle option as to which one opens up when you go to edit a record.
An error occurred while saving the comment Wes Osborn
commented
If you want people to edit MARC records more in Leap, you're gonna need something like this. I wonder what happens when people bork the record by leaving out a space or something in a fixed field.
This would likely make it easier to support things like undos since that is built in to most web browsers in free text fields.
I don't think it has to be permissioned on our end, there are so few people editing MARC records and those who don't feel comfortable with something like this are unlikely to use it. I suppose a middle ground option would be an enable/disable at a branch level to give you some degree of control.
Wes Osborn
supported this idea
·
-
4 votes
An error occurred while saving the comment Wes Osborn
commented
Maybe adding damaged check-in the to Action menu would be another option.
-
4 votes
An error occurred while saving the comment Wes Osborn
commented
You can "send" all search results to a record set using this method: https://documentation.iii.com/leap/8.0/Default.htm#LEAP1_0/LeapCreateRecSetFTSearch2255.htm
-
4 votes
An error occurred while saving the comment Wes Osborn
commented
Find tool window expansion is coming in 8.1: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/1095-find-tool-window-expansion-
Here is the issue to vote on for printing from the find tool that you should vote & comment on: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46530688-leap-print-from-find-tool
-
20 votes
An error occurred while saving the comment Wes Osborn
commented
@Sherri: Find Tool window expansion is coming in Polaris 8.1: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/1095-find-tool-window-expansion-
An error occurred while saving the comment Wes Osborn
commented
This would be lovely to have in Leap! Along with an icon or glyph to clear the entry, which would improve upon the staff desktop client experience.
Wes Osborn
supported this idea
·
-
17 votes
An error occurred while saving the comment Wes Osborn
commented
Being able to do this via bulk update would certainly help us feel more confident about moving to hosted at some point in the future - since we'd lose our SQL write access.
Wes Osborn
supported this idea
·
-
44 votes
An error occurred while saving the comment Wes Osborn
commented
@Carl you might want to open a new Idea on that ILL Request part. Making that field editable at all is likely to be its own major project due to the interactions and implications that it might have on parts of the ILL workflow.
In the case of "normal" holds, staff could already go in and update the held until date one by one, so adding the bulk update functionality is *relatively* more straightforward.
An error occurred while saving the comment Wes Osborn
commented
This is something we regularly need to do via SQL for branches closing for expected and unexpected reasons. It would be great to see this supported via an official UI so we could feel more confident about making the change. Support for this also moves us closer to being about to seriously consider hosting.
Wes Osborn
supported this idea
·
-
21 votes
An error occurred while saving the comment Wes Osborn
commented
Also, we'd need to think about how to handle existing reports if this new method was implemented. Maybe if the saved/scheduled report already represented 100% of branches currently in the system, it would be switched to a library level report.
Wes Osborn
shared this idea
·
-
1 vote
An error occurred while saving the comment Wes Osborn
commented
The i-Tiva version 3.0 has been updated to support the existing date formats. Anyone having issues should contact i-Tiva about an update.
Wes Osborn
shared this idea
·
-
17 votes
An error occurred while saving the comment Wes Osborn
commented
We have something like this in our system but we have to maintain it by using custom tables. It is critical for our state reporting and not having something like this would prevent us from moving to hosting.
Wes Osborn
shared this idea
·
-
86 votes
An error occurred while saving the comment Wes Osborn
commented
You might consider voting and commenting for this other idea which already has a bit of traction: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46539763-book-club-holds
An error occurred while saving the comment Wes Osborn
commented
This would make so many staff happy and would be a great feature to entice people over to leap who aren't already using it.
Wes Osborn
supported this idea
·
-
3 votes
An error occurred while saving the comment Wes Osborn
commented
Just verifying, you've tried this and it doesn't work for you? https://documentation.iii.com/polaris/7.8/Default.htm#PolarisStaffHelp/UI_Ref/PRadminPat/Patron_Registration_Filter_Patron_Codes_Dialog_Box.htm
-
14 votes
An error occurred while saving the comment Wes Osborn
commented
Yeah, I was surprised too Lynn.
At least on the Sierra side it both warns and allows you to continue with the import. That way you don't have to spend a couple of weeks in back and forth with the vendor asking them what the problem is and why their file format is borked only to find out it was your ILS all along.
An error occurred while saving the comment Wes Osborn
commented
Even better would be the system not allowing an invoice from 10 years ago and another vendor to be treated as a "duplicate" for the incoming invoice.
Wes Osborn
shared this idea
·
-
13 votes
An error occurred while saving the comment Wes Osborn
commented
I'm not 100% what you're thinking about here, could it be similar to this idea? https://ideas.iii.com/forums/951742-ils-polaris/suggestions/50193054-combine-current-and-recent-workform-tracker-into-o
-
42 votes
An error occurred while saving the comment Wes Osborn
commented
If you have someone who is an IUG member, consider having them vote for this idea as part of the current MEEP voting session: https://forum.innovativeusers.org/t/polaris-8-1-meep-voting-begins-today-at-12p-eastern/2686
-
27 votes
An error occurred while saving the comment Wes Osborn
commented
Per "T's" comment - another option like sending an immediate test "Let us know if you got this text/email/phone call" could be another good approach that ensures that the notification method works without requiring the confirmation loop. And since it would be done by staff initiating something on the patron account it would allow for a more controlled rollout.
An error occurred while saving the comment Wes Osborn
commented
Although I know this would be more steps than happen today, I think that it is not an unusual flow for most accounts that people establish these days and would ultimately benefit both the patron with being assured they can get their notices and the library for having a better reputation for sending notices and lower costs (SMS/texts) for making sure those notices get through.
Wes Osborn
shared this idea
·
-
18 votesWes Osborn
supported this idea
·
-
38 votesWes Osborn
shared this idea
·
An error occurred while saving the comment Wes Osborn
commented
Summary:
It would be extremely useful to have a “Show SQL” button available for both ad-hoc and saved reports in SimplyReports.Background and Problem:
There are currently well-known workarounds that allow users to view or reconstruct the SQL generated by a report, but they’re tedious and confusing. These methods often involve extra steps like exporting report definitions or view the page source after a scary Reload warning message.Proposed Solution:
Add a “Show SQL” button directly in the report interface—both for ad-hoc reports and saved reports. When clicked, it would display the underlying SQL that SimplyReports is generating for that report.Benefits:
• Faster customization: Users could take the generated SQL and adapt it for their own use cases that SimplyReports doesn’t natively support.
• Integration with other tools: Users could copy the SQL and use it in external systems like FindTool SQL searches or other analytical environments.
• Reduced support burden: Empowering users to self-serve their SQL needs would reduce the number of requests for special report modifications.Additional Considerations:
• Ideally, it should be formatted for readability.
• An optional download or copy-to-clipboard feature would enhance usability even further.Keywords for searching: Simply Reports
Automating this or at least making the manual process easier without having to log into multiple branches would be great.