Settings and activity
27 results found
-
13 votes
Wes Osborn
shared this idea
·
-
20 votes
An error occurred while saving the comment Wes Osborn
supported this idea
·
-
2 votes
An error occurred while saving the comment Wes Osborn
commented
You might also want to add this comment here on the product board: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/753-expresscheck-update
-
11 votes
An error occurred while saving the comment Wes Osborn
commented
Not forcing a log out of the identity provider is huge. Especially for organizations where the SSO is used to sign people in/out of the time keeping software is also SSO. So they sign out of leap, which signs them out of SSO, then they have to log back into SSO just to punch out for the day.
The option should be to sign out of Leap ONLY, just like non-SSOs sign out of Leap only.
Wes Osborn
supported this idea
·
-
3 votesWes Osborn
shared this idea
·
-
10 votesWes Osborn
supported this idea
·
An error occurred while saving the comment Wes Osborn
commented
Also, the API key itself shouldn't be visible to ANYONE.
Modern security practice is that you get ONE chance to see the actual key during the creation step and then after that all you can do is disable/delete it.
-
60 votes
An error occurred while saving the comment Wes Osborn
commented
This would be very important for any hosted customers who don't have direct access to SQL to perform record set cleanup.
Wes Osborn
supported this idea
·
-
48 votesWes Osborn
supported this idea
·
-
6 votesWes Osborn
shared this idea
·
-
15 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.
-
30 votesWes Osborn
shared this idea
·
-
11 votesWes Osborn
shared this idea
·
-
11 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
·
-
10 votesWes Osborn
shared this idea
·
-
9 votesWes Osborn
shared this idea
·
-
32 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.
-
78 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
·
-
27 votesWes Osborn
supported this idea
·
-
105 votesWes Osborn
supported this idea
·
-
63 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
·
We are evaluating discovery layers and having this in Vega would help put it on par with competitors (coming in Bibliocommons).