Settings and activity
326 results found
-
7 votes
Shawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
9 votes
An error occurred while saving the comment An error occurred while saving the comment Shawn P. Farrell
commented
As Ray notes, this can happen again, as it did outside of our recent upgrade, only yesterday, with a batch of failed notices appearing at random. Not only did these (& those in the example in the original post) fail to send, there's no identifying data attached to the reporting.
Shawn P. Farrell
shared this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
3 votes
An error occurred while saving the comment Shawn P. Farrell
commented
An automated redirect would be terrific! I've been working at Millennium/Sierra libraries that have floated collections for 16 years now & the potential for pooling multiple copies for the reasons Elizabeth mentions is considerable. Staff have resorted to workarounds by noting titles & the number of duplicates available in shared spreadsheets so other branches can view at a glance & request them & for a while, duplicates would just be sent to a large room at NYPL's Library Services Center, where branch staff could visit & "shop" for titles they wanted at their branch.
Automating the refusal of a float-in would eliminate so much extra work for staff. Do you see it as being entirely automated, or coming with some sort of prompt at check-in like "X copies currently available at Branch. Do you wish to check-in or return to pool?"
Shawn P. Farrell
supported this idea
·
-
6 votesShawn P. Farrell
supported this idea
·
-
21 votes
An error occurred while saving the comment Shawn P. Farrell
commented
I like the idea of these temporary locations. Several years ago, NYPL was looking for the means to remedy something similar. Their flagship 5th Avenue location had a Scholar program, where select patrons doing longterm research/writing projects could basically have things pulled from the stacks on a longterm basis & sit in a special area for their ready access. They may not use them every day, & the potential existed that another patron might want to access them for in-library use only for a single day, before they go back to their temporary shelving status.
Will share this idea with them & see if they still might find this useful. It definitely has a lot of other ptoential use for display items, etc.
Shawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
22 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Shawn P. Farrell
commented
We just came across an instance of the wrong cover art appearing because of this & would also like to see it addressed.
Shawn P. Farrell
supported this idea
·
-
9 votesShawn P. Farrell
supported this idea
·
-
6 votesShawn P. Farrell
supported this idea
·
-
35 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
16 votesShawn P. Farrell
supported this idea
·
-
12 votesShawn P. Farrell
shared this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.
Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a box next to listed sessions to restart several at once, but it's much easier to say, "Restart everything from line 30-142."
Shawn P. Farrell
shared this idea
·
-
9 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
This happened again with notices sent yesterday. Out of 8458 circulation notices sent via e-mail, 3307 showed up in LX Starter's reporting as 'Failed to Send.' Even if we weren't sending notices at this volume & seeing a 40% failure rate, a fix for this failure feels critical.