Settings and activity
38 results found
-
4 votes
An error occurred while saving the comment Christy Sayre shared this idea ·
-
45 votes
An error occurred while saving the comment Christy Sayre commented
Some patron-identifying fields would be helpful in our consortium, particularly Patron code, but possibly patron assigned branch. This would help libraries decide whether to fill the hold and could ultimately lead to better service.
Christy Sayre supported this idea ·
-
26 votes
Christy Sayre supported this idea ·
-
29 votes
Christy Sayre supported this idea ·
-
31 votes
Christy Sayre supported this idea ·
-
33 votes
Christy Sayre supported this idea ·
-
62 votes
An error occurred while saving the comment Christy Sayre commented
I recently had a request for this from staff in one of our libraries, and discovered there's not an ideal way to add this info, so I would like to see a data well for this.
Christy Sayre supported this idea ·
-
64 votes
This idea is outside of our agreed upon Idea Graduation Workflow, but because it was just raised in the most recent rount of MEEP voting, I'm going to keep it open for another cycle. Moving to "Under Review" status.
Christy Sayre supported this idea ·
-
82 votes
Christy Sayre supported this idea ·
-
83 votes
Christy Sayre supported this idea ·
-
9 votes
This idea will be reviewed by the product management team for consideration in an upcoming release.
An error occurred while saving the comment Christy Sayre commented
As an administrator, this would be a huge time-saver. It's very difficult to line up a real-time test of a service like this.
Christy Sayre supported this idea ·
-
4 votes
An error occurred while saving the comment Christy Sayre commented
We have a growing number of app users, and it would be a nice additional way for staff to push out quick messages to individual patrons -- "we've been trying to reach you!" "You left your library card here, we're keeping it safe"
Christy Sayre supported this idea ·
-
73 votes
An error occurred while saving the comment Christy Sayre commented
The notices in their current form, while nice to look at, are very confusing and we receive constant questions about it.
Christy Sayre supported this idea ·
-
13 votes
An error occurred while saving the comment Christy Sayre commented
Borrowers rarely claim they returned something until they receive notification that they've been billed for a Lost item. In Leap, changing a Lost item to a Claim is a very messy and step-heavy process. One has to copy the barcode of the lost item, which opens up the item window. Then come back to the patron record, and check out the lost item again (without checking it in). That removes the lost status and removes the bill, often one of the goals. Once the item is checked out to the patron and appears in the Out/Overdue view, the staff can select the item and make it a Claim. The process of all of this leaves a history of being checked back in and checked out again, which, when viewed by others, makes it seem as though staff was tampering with the record.
By contrast, it's very simple to change a Claim to a Lost item, and the trail is "clean." So please consider providing staff with a clean and simple way to change a Lost item to a Claim.
Christy Sayre supported this idea ·
-
115 votes
Christy Sayre supported this idea ·
-
88 votes
Christy Sayre supported this idea ·
-
96 votes
Christy Sayre supported this idea ·
-
103 votes
An error occurred while saving the comment Christy Sayre commented
I can see how this would be useful for any kind of device that requires re-charging.
Christy Sayre supported this idea ·
-
37 votes
An error occurred while saving the comment Christy Sayre commented
Our libraries are clamoring for this!
Christy Sayre supported this idea ·
-
8 votes
An error occurred while saving the comment Christy Sayre commented
In a consortium of 43 libraries, it's nigh impossible to consider adding additional patron codes. With the hold setting in the item record limiting holds to patrons from this library and branches, it seems like the architecture is already in place to add a similar capability for limiting checkouts--this would be a truly elegant solution and could make managing our circulation much simpler.
Christy Sayre supported this idea ·
Hi Gabrielle, thanks for pointing that out--we hadn't seen that option. Just requiring a birthdate may be the answer, and it's not a bad piece to require anyway.