Settings and activity
60 results found
-
70 votes
An error occurred while saving the comment 
Wes Osborn
supported this idea
·
-
53 votesWes Osborn
supported this idea
·
-
6 votesWes Osborn
shared this idea
·
-
19 votesWes Osborn
supported this idea
·
An error occurred while saving the comment Wes Osborn
commented
If this can't be implemented, the Leap patron bulk change process should make it clearer that you must change the patron's registered branch. Right now that is pretty unclear, whereas in the client it would give you a more specific error message.
-
32 votesWes Osborn
shared this idea
·
-
18 votesWes Osborn
shared this idea
·
-
18 votes
An error occurred while saving the comment Wes Osborn
commented
Although in an ideal world, I suppose it might be nice for the patron to have a preferred area for "each" branch. Just extending the single branch + preferred pickup location would be a huge help for us. In fact renaming this setting/option from preferred to default might better reflect that there can only be one per patron account.
Wes Osborn
shared this idea
·
-
14 votesWes Osborn
shared this idea
·
-
9 votesWes Osborn
shared this idea
·
-
36 votes
An error occurred while saving the comment Wes Osborn
commented
This can be done through the API and through SIP today. You need to contact Overdrive and ask them to map your current barcodes to the patron ID. You'll probably need to send them a mapping file as part of the migration process. Nothing will change for your patrons except for if they get a new barcode, when they log into libby with that new barcode, they'll see the same account information that was their from their previous account.
-
85 votes
An error occurred while saving the comment Wes Osborn
commented
Also, RFID, which is only used by a small percentage of customers has a Leap helper app. Why shouldn't printing, which is likely used by 99% of customers also have a helper app to make it better?
An error occurred while saving the comment Wes Osborn
commented
Yes!!!! This is one of the biggest hurdles to getting Leap adopted. And none of the browser solutions is ideal. If you do kiosk printing for receipts, then report printing doesn't work well. I know there was an idealized world where printing wouldn't be needed anymore but we've been testing the limits of that for the past decade and it just isn't a reality, even post COVID. It is simply the best solution in most cases to print out a hold pull list rather than lugging around a heavy AND expensive tablet/laptop. And most customers prefer a printed receipt even in a fine-free world. Please help make Leap printing better.
Wes Osborn
supported this idea
·
-
137 votesWes Osborn
supported this idea
·
-
73 votes
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
·
-
13 votes
An error occurred while saving the comment Wes Osborn
commented
How would you propose that bibs that have multiple items with different material types be handled?
-
37 votesUNDER REVIEW · 5 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Wes Osborn
commented
Just throwing this out here in case anyone sees this and is unaware, but the 970 $h allows you to match on a specific template name rather than the rather unwieldy combination of other codes. I might like to see the length of the $h expanded from 10 characters to allow for more unique template names especially in a consortia environment where the first 3 or 4 characters of the template name are typically the library abbreviation.
-
52 votes
An error occurred while saving the comment Wes Osborn
commented
Saving the information in the browser cache could lead to catastrophic data loss. This renders the offline capabilities of Leap as unusable in many organizations.
Wes Osborn
supported this idea
·
-
31 votesWes Osborn
shared this idea
·
-
99 votes
An error occurred while saving the comment Wes Osborn
commented
The amount of time this would save would almost be unbelievable to quantify. Our notes fields are littered with various date formats and staff initials. All of which could be gone in an instant if someone hits the wrong key. And they could be entered incorrectly because people are just hand typing the information.
I also think the value of blocking versus non-blocking needs to be re-examined in the Leap world where both options work similar when the staff are accessing the account.
Wes Osborn
supported this idea
·
-
30 votesWes Osborn
shared this idea
·
-
148 votesWes Osborn
supported this idea
·
This would be very important for any hosted customers who don't have direct access to SQL to perform record set cleanup.