Settings and activity
341 results found
-
1 vote
Shawn P. Farrell
shared this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
5 votesShawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
12 votesShawn P. Farrell
supported this idea
·
-
1 vote
An error occurred while saving the comment -
2 votesShawn P. Farrell
supported this idea
·
-
1 vote
An error occurred while saving the comment Shawn P. Farrell
commented
I'm wondering if this might be a localized error for you? I just called in to our instance (as a Sierra library) & heard "is" before any items not yet due.
-
6 votes
An error occurred while saving the comment Shawn P. Farrell
commented
This would be a fantastic addition to LX Starter & make it preferrable to any number of competing options.
Shawn P. Farrell
supported this idea
·
-
13 votes
An error occurred while saving the comment Shawn P. Farrell
commented
An option to receive more than one notice type would be terrific for those patrons who rely on these notices to manage their account!
We have so many patrons who have had either telephone notices or e-mail notices, only to see them inexplicably bounce or get blocked by some app or filter that they're unable to control or even aware of. It' becomes a paint point for frontline staff dealing with patrons who haven't received their notices & I think I've developed tennis elbow just from writing & rewriting the explanation of "INCOMPLETE LOGGED" in the Teleforms history.
If patrons could elect to receive notices of more than one type, they'd have a failsafe, which is kind of how we're currently planning to promote text messaging, as we launch Vega Interact SMS.
Shawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
19 votesShawn P. Farrell
supported this idea
·
-
7 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
16 votes
An error occurred while saving the comment Shawn P. Farrell
commented
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.
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
·
-
10 votesShawn P. Farrell
supported this idea
·
-
4 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
·
I think this idea belongs in the Vega Mobile forum, not the Vega Mobile Worklists forum?