November 19th, 2014 Brian Herzog
I don't often give presentation-based programs for patrons at my library, but last week I assisted one of my coworkers with a "Using Library Ebooks" program at our local Senior Center. A few things stood out to me during this program that I didn't anticipate, so I thought it might be worthwhile to share them here.
(But again, I don't do this very often, so it might be old news to people that do.)
First of all, we were invited to do this tech program at the Senior Center - they're always happy to have speakers visit them, and seniors seem to be the demographic that we help the most with ebooks and mobile devices. It seemed like a win-win.
The plan was to do a short presentation with slides, then live demonstrations downloading to devices, and finally hands-on helping the seniors with their devices they brought with them. Unfortunately, the Senior Center's wi-fi was down, which pretty much killed any live demo or helping we planned because no one could get online.
My coworker stretched out her slides as long as she could, and then we just talked with the seniors and answered the questions. Although things didn't go as planned, I felt it went really well. The thing about just sitting around talking is that the people felt comfortable enough to ask us just about anything.
So, based on this experience, here's what I learned for next time:
- Don't count on wi-fi - this is true for any presentation really, and having backup slides is just good practice. But in our case, having slides that had screenshots of the different websites we were talking about was invaluable, because we could still show what the sites looked like, where important links were, etc.
- Make a Large Print Presentation - many seniors read Large Print books for a reason, so it makes sense that they'd be more comfortable with Large Print slides too. Even though it's projected up on a wall, it's still easy to accidentally make the type small to cram a lot of information on a slide. In a few cases I noticed the seniors leaning in towards the screen to read the slides, so this is definitely something I'll keep in mind for future presentations to seniors.
A little harder to manage are screenshots, because you can only get so big with those. But one option is to pull a zoomed shot of the part of the page you want to highlight, so people can read it - but to also show the full page and where that zoomed shot fits in. I could see just a series of enlarged fragments being confusing.
- Do these talks before Christmas - conventional wisdom over the last few years has been to offer ebook workshops right after the holidays, in order to help all those people who just received devices as gifts. This program was in early November, and something interesting came up: it was perfect timing, because it caught all of these seniors before they went South to Florida for the winter.
That hadn't really occurred to me before, and if we waited until January for this program we would have missed them. Obviously not everyone goes to Florida for the winter, but in our case it really is a strategy to accommodate.
Another nice benefit of mobile seniors is that they aren't limited to just what this library offers. Chances are the library in where ever they're going also offers ebooks, and it's worth their time to stop in there to ask about it. Some of the seniors in our program own property in Florida and some only rented, so they may or may not be able to get library cards down there depending on library policy. But we can help them with the Collier County Public Library's Overdrive catalog as easily as we can our own, and they seemed to appreciate it.
- Be ready to talk about anything - this isn't really something you can prepare for, but it's good to allow time for wide-ranging conversations. In our case, when my coworker mentioned using Adobe Digital Editions, one senior gentleman said he must not be able to use ebooks after all because his computer at home has been telling him to update is Adobe and he can't.
That led to a bit of an explanation on the differences between Adobe the company, Adobe Flash, Adobe Reader, and Adobe Digital Editions. It took some time, but in the end the seniors seem to understand why all of those are different things and not really related, and a problem with Flash doesn't mean he can't read ebooks. Of course I'd talk about this with anyone who asked, but having the freedom to spend some time on this seemed to benefit everyone.
- If at all possible, work on their devices - I think every one of our attendees brought their own device, and they also each had unique questions about their experience (and problems) so far. I felt bad that we couldn't get online and address each one of them, because people in general aren't usually interested in the overall Way Things Should Be, they're interested in the very specific Ways It Is For Them.
- Bring handouts - my coworker brought copies of her slides as handouts, but what we forgot were the ebook step-by-step booklets we have at the library. I also forgot to bring business cards with my contact information so people could easily contact us for one-on-one tech help appointments. Everyone was very interested in those, and said they'd be stopping by the library for more personal assistance. Which is great, but I feel bad that we didn't think ahead to make it easier for them to do so.
Overall I think it was a very successful program. The six or so attendees really seemed to benefit, and my coworker and I enjoyed the casual instruction. If anyone else has helpful tips to make programs better, please let me know in the comments.
November 15th, 2014 Brian Herzog
This was kind of a funny question, right up until I realized I had created a monster.
A patron, who is somewhat new to email, walked up to the desk and said,
Patron: I think some of my friends' email accounts have all been hacked by the same person, and he's sending me messages.
Me: Oh really, why?
Patron: Because at the end of a lot of messages - not all of them, but some of them - it is signed with just the initial J. Someone named J must have hacked their accounts and is sending messages to me, but they don't know they've been hacked because sometimes the messages really come from my friends.
I love a good conspiracy, but in this case I explained what emoticons are and how people sometimes use them in email to display smiling or frowning faces. Some people just used keyboard characters, some use a special font, and some use images.
In this case the patron's friends must be using Outlook, which uses Wingdings font to display emoji. If other email programs don't use that technique, it will just show that character in the default font, which is usually a J for a smiley face.
We then went back over to his computer which still had his Yahoo mail up, and I showed him how he could add emojis to his message. He was thrilled, and I think now all of his friends are going to get sick of it very quickly.
Even though the patron was happy, I still much prefer the idea of a mysterious person named J hacking all his friends' accounts just to send him messages.
November 12th, 2014 Brian Herzog
My library is in the very beginning stage of redesigning our website, so I've been collecting various links on the subject. I thought this infographic was funny, and maybe actually useful too.
The "translations" down the right side are actually a nice little collection of sample ideas. And of course, when our design team starts getting input on early drafts from staff and patrons, the translations themselves will surely be invaluable.
November 8th, 2014 Brian Herzog
I like reference interactions where the initial question really just ends up being an ice-breaker for a series of bonus tangents. Well, sometimes I like those.
In this case, a patron came up to the desk carrying a back issue of the Wall Street Journal and asked,
Can I check this out? I want to take it home to compare it to the online version, because I think they're not giving me everything online that they are in the newspaper. I cancelled my newspaper subscription and just do the online now, but an online subscription is the same price as the newspaper and I don't think they include all the articles that are in the real paper.
I don't know the specifics of the WSJ's pricing structure, but I suspect that this patron is correct. I noticed this years ago with our online subscription the Lowell Sun database - articles people swore they saw in the print paper were not coming up in the database (and it wasn't hard for me to verify).
At the time, I called Newsbank to ask them about it, and they said that yes, that is correct. They only have the rights to put Lowell Sun-generated content into their database - so, any syndicated content like AP articles, comics, puzzles, etc, will not appear online. This was a few years ago and in a different context, but the Newsbank person said we'd never see an online version of anything that has everything the print edition has.
I relayed this to the patron, and he appeared to feel vindicated.
He also was extremely interested in the previously-unknown-to-him fact that we had online access to the Lowell Sun - and the Boston Globe, and the New York Times. I showed him how to log in from home with his library card, so that was a happy little tangent. Then he had another tangent for me:
Well, that's okay anyway about the Wall Street Journal articles. Sometimes what I can do is look at the headlines on the Wall Street Journal website, and if an article I want to read is one you have to pay for, then I just search for that headline in Google and usually it links to the full article for free. I don't know why, and it's not all the time, but usually.
So then we had a little talk about paywalls and Google access, for which I had no good answer. But while listening to him, I suspect that some of the articles he links to from Google weren't actually on the WSJ website, just news articles from other sources that had very similar headlines.
What I did not tell him about was the Element Inspector trick - a method for editing a website's code to remove the "sign in to read the full article" blocking mechanism. However, after the patron left I did try out both that trick and his search-for-the-headline-on-Google technique, and I couldn't get either of them to work for WSJ.com articles. Which isn't too surprising - if anyone is going to put a lot of effort into making sure casual circumvention can't be used to access their content, it'll be online newspapers.
Anyway, so instead of taking the back issue of the newspaper home, he just sat down at one of our computers and spent some time comparing the print headlines to the articles available on WSJ.com. I didn't talk to him again though, so I don't know what he discovered.
But another delightful bonus from this question is the idea of letting patrons take home old issues of newspapers. We don't catalog them at all, so all our newspapers are in-library only. I've never been asked this before, but it's certainly a good one for our No Log, to see if we get to yes on it. We already use the honor system for our collection of Cliff Notes, so it might work for old newspapers too.
Tags: access, content, database, libraries, Library, newspaper, online, public, Reference Question, wall street journal, wsj
November 6th, 2014 Brian Herzog
So, social media, wireless printing, circulating telescopes, blah blah blah - you know what else we've got? Carbon paper!
To go along with our public typewriter and public fax machine, my library has recently started using carbon paper again (well, actually, carbonless paper).
We got the idea while revamping our behavior warning slip - when a noteworthy incident occurred, staff would fill out a warning slip, and then have to go in the back room to make a photocopy for the patron to take with them. To streamline the process, we thought we'd redesign the form with carbon paper technology in mind, and now we're rolling out the result.
Our new form is three "pages" - really it's one, but with Admin, Desk, and Patron copies for the white, yellow, and pink paper. That way, staff can fill it out on the spot and have all the copies they need right there. One for the patron, one on file in the Admin office, and one to keep at the desk so other staff will know what's going on.
Hopefully, this will make things easier. It took some trial and error to make sure we were printing the pages correctly so the writing would transfer, but once we got it right, the forms seem to work very well. We shall see.
October 29th, 2014 Brian Herzog
Last week, a patron came in and asked for help using the scanner. No problem.
But while I was helping her, she explained that she has an all-in-one copier/printer/scanner that used to work great but is now giving her trouble, hence the trip to the library. She tried describing to me what the problem was, and it seemed like it should be diagnosable and solvable, but I was just not getting it.
One great thing about the emergence of mobile devices, and increasing prevalence of laptops, is that people can bring them into the library for tech support. But with desktops, and in this case copier/printer/scanners, even something that would be simple to correct continues to plague them because it's too difficult to communicate either the problem or the solution remotely.
So, the idea struck me - why not start a program offering in-home tech support? I think it would be unrealistic to send library staff out to patrons' homes, but how about this: we have a special "tech support tablet" that patrons can check out, and then when they get home, use Skype or some other video chat service. That way, I could actually see what the problem was, read the error messages on their screen, see what lights were flashing, tell them which menus to click, etc.
Really, it'd be offering the same service we currently provide to patrons who can bring their devices to the library, so why not offer it remotely too?
Well, any number of reasons, if you think about it. First, this would still be difficult, and not like being there in person. Second, and maybe more frighteningly, who knows what else might show up on the screen besides tech problems. This was basically the reason this idea went no further.
I mean, I still like this idea, and think it could help people. But it would be tricky, and has a lot of downside potential, so for the time being this is just going to be filed under "maybe someday."