Diary of a Librarian: The Skills We REALLY Need

Hello, friends! It’s nearly Thanksgiving, so I’ll keep this short, sweet, and to the point. We librarians need to edumacate ourselves.

I’m not talking about increasing our focus on reference or becoming better at beeping the books. That’s the old way of thinking about specialties. These days we need to develop new skills, and that means continuing ed. Let’s pay librarians’ tuition and send them to school to develop some useful new skills! These skills don’t have to be specific to each staff member. Someone could develop two specialties or even triple up – this, after all, is libraries.

Here’s what I think we need the most right now.

Education Librarian

We’re as much teachers these days as anything else. Patrons want to learn how to download apps and use Excel. The problem is that, aside from school librarians, we generally don’t know how to teach.

The education librarian would coordinate learning events in the library and, when necessary, instruct other librarians on how to be good teachers. When someone declares that there should be a Coursera run in the library, it’ll be the education librarian who figures that out.

Internal Communication Librarian

Librarians tend to be free spirits. Individualists. A herd of cats, you could say. And that’s great! Except it also isn’t. It also means that we trip all over each other in a group. Enter the internal communication librarian!

This person takes business classes and then manages meetings, makes sure that everybody knows what’s going on, and generally makes sure Person X talks to Person Y about Person Z’s project. Maybe they’d run an internal staff blog detailing the library’s news.

Outreach Librarian

A lot of places already have this person – my place does. But too many do not! Some librarians need to take marketing classes and become library bloggers, social media experts, and advertising mavens.

IT Librarian

That’s me, guys! The IT librarian might come in with some IT background, but they could also get training as they work for the library. They don’t have to be hackers or whatever, they just need to know something about a motherboard and be ready to talk the lingo to tech support.

The IT librarian could double as the cybersecurity librarian. They’d track the institutional passwords and explain to everyone why they really do need to change every 60 days.

Elder Librarian

Seniors have particular needs. Sometimes, these involve mobility and vision accommodations that most of us don’t think of before they happen to us. At the same time, they’re big-time library patrons. Why not specialize a librarian to them the way we do with teens?

Graphic Designer Librarian

Libraries aren’t not going to need to do outreach in the future. That outreach isn’t not going to need to look good. Why not train someone to be the library’s professional artist?

This shouldn’t require an art degree, just a willingness to learn. The graphic designer would make clipart, zshuzsh up promotional materials, and keep library materials on-brand and looking neat.

Betabrarian

We need librarians whose job priority is to watch for trends in the profession and in the wider world, and then test them out to see if they could be useful in a library context.

They should go to every conference, collect every business card, and build a weekly situational report for their institution that includes new social factors (“OK Boomer,”) new tech developments (foldable smartphone,) and the results of their own R&D. For example, maybe this is the person to test NFC stickers in the library.

Special Needs Librarian

There are a lot of possible applications for this kind of expertise. Are libraries overwhelming environments for autistic people? I have no idea! I’m not autistic and have no training in that area. Are children’s books available enough to adults who read at a low Lexile? Once again, it’s a need that exists and we might be able to meet it if we train someone to be an expert on the topic.

Linguist Librarian

This intrepid person’s job will be to learn languages. They should come into the library with at least two, but over the years, they will learn more. The library will send them to school to learn Spanish, French, Arabic, Mandarin, and anything else that could possibly come in useful. It won’t be their entire job, per se, but it’ll be a big chunk.

 

Now I want to hear your ideas. Comment with the librarian specialization you think we need right now! If you think librarians already have enough going on in their lives without more stupid school, comment about that too.

Happy travel day, library friends!

Special thanks to this awesome dude for our featured image!——-> Dollar Gill


Diary Of A Librarian Addendum: When Hardware Strikes and Apology to SupportAssist

If you’re a reader of mine, then you may remember this post about how much I hate SupportAssist. Or this one, about how SupportAssist failed me for the last time.

I would like to apologize to SupportAssist. I slandered its reputation for a problem that it did not cause.

That’s not to say that SA isn’t a ridiculous piece of badly programmed junk. It totally is! This past Wednesday, it merrily failed to update any applicable drivers on our public computers, which is fine because the infinitely superior Dell Command Update does the same thing. But in the particular case of Computer 43, SA’s problematic nature had been compounded by a bad motherboard. I hope. Because 43 hasn’t frozen since receiving a new one yesterday, so maybe, if I don’t tell any lies before Christmas, the real problem won’t end up being the hard drive or the processor.

I’m currently taking a hardware class, so I’m enjoying the intellectual challenge of identifying what exactly went wrong. Was it the BIOS chip? The CMOS? Oh the acronyms that could have gone wrong with the motherboard! It now makes perfect sense that freezing could indicate a motherboard issue – I already knew that BIOS or UEFI can cause that problem if they don’t update correctly. It makes me wonder if I ought to have tried flashing before calling in the warranty, but c’est la vie. The computer works and that’s sufficient.

It’s a little annoying that I can’t House my way to a magic diagnosis based on the evidence, but I’m still a nascent techie in many ways and I’m not going to go too hard on myself. The main thing I’m learning from my experience as a tech librarian is that if something’s only going wrong on just one computer, I should at least consider the possibility that it’s hardware-based. This kind of thing has happened a couple times before, not necessarily with SupportAssist, but in a similar pattern. (Problem on one single computer, fix software, problem persists, switch hardware, problem solved.)

I did think it was funny at the time that none of the other computers were freezing, but I chalked it up to SA being so wonky that it was actually inconsistent across units. Apparently, SA is the red flag to my bullish IT style. A diagnostic startup scan didn’t catch any problems, either, so now I know that can happen. And I need to be aware of my software prejudices, apparently.

I’m not sure I would have done anything differently if I’d guessed that the problem was hardware-based, but I still would have felt better knowing. If nothing else, I could have prepared the staff for the possibility that the computer would continue to freeze even after the apparent software problem had been managed.

If I wanted a secondary lesson, it would be that a library technology professional’s job is mainly to communicate. That means understanding enough about the computers to explain ongoing issues in a way that both makes sense and is not scary as well as developing the ability to interface with customer service in a way that works for everybody. I do think that I’m improving. I’ll say that 50% of the reason for this is that I’m in school and actively learning about computers. Knowing a bit, while remaining humble about the vast sea of knowledge to which you do not yet have access, seems to be key to a good working relationship with tech support. I’m also continuing to grow and mature as a person and a professional, which is causing my communication skills to improve anyway, and librarians as an industry are steadily becoming more tech-savvy, although we’re still way behind where we need to be.

For now,  we have a new motherboard for good old 43 and everything seems ducky. No freezes yet. I’m almost ready to sally forth next week to a long Thanksgiving vacation with full peace of mind that this computer’s got a working motherboard.

Let’s hope it was just the motherboard.


Diary of a Librarian: Windows 10 Is Still Free. Also, more SupportAssist.

It’s true. If you have a Windows 7 machine, you can still get an upgrade for free. It’s legal, too. Go to the Microsoft website at this link and download the media creation tool. Run it. Do it now before the 7pocalypse arrives in January!

And don’t take it from me. Take it from ZDNet.

In bookish news, I’m still working on Part 3 of my DHALGREN review. (Part 1 is here.) I might have it up tomorrow, so grit your teeth and hang onto your harmonicas. For now, join me in the sweet, easy, fun library life, where we skip through fields of aahhhh who am I kidding SupportAssist did another crazy thing today.

This time, I had a computer (One! Single! Computer!) on our staff network freezing at odd times. It started yesterday with freezes that happened closer and closer to startup and did not respond to ctrl+alt+del. I crashed the poor thing and performed a system restore, feeling very technological and cool. That seemed to solve the problem.

AT FIRST!

It didn’t take long for dear little Computer 43 to fritz out again. Today, it froze after a restart, and then during a diagnostic scan. I called uncle, and Dell, too.

I avoid calling Dell because my customer service experience with this company is extraordinarily spotty. Sometimes they’re super-on. Other times, their technicians make little pew-pew noises when they think they’re on hold and then delete networked printers willy-nilly over my strident objections. This time, I was lucky. My dude figured out that SupportAssist had been causing the system to freeze up at a deep fundamental level.

via GIPHY

 

Part of the reason for this was that SA has two versions. One is a Windows app and the other is a Dell app. You can get the Dell app from the Dell website. You can get the Windows app from the Windows App Store. That one appears to be buggy. It may also be either advertising itself very aggressively or chronically reinstalling itself on some machines. This actually explains a lot about how my library’s public-facing machines have been behaving.

So he uninstalled SupportAssist, although it took him a couple of attempts, and suggested that we not use this Dell-origin piece of wrecknology anymore (thanks, Christine, for this situationally perfect word.) I’ll be passing his suggestion along. If I never had to lay eyes upon SupportAssist again, I’d be happy. I’m now 14% sure that this is how God intends to end the world.


Diary of a Librarian: SupportAssist Is The Root Of All Evil

Technically, I’m a technology librarian. That means that I know kind of how to make the computers behave themselves under ideal circumstances. Under less-than-ideal circumstances, I can either call tech support and spend hours on the phone or gracefully give up and text our IT contractor. However, there’s a decent handful of problems that I can manage on my own.

In a strictly professional sense, SupportAssist is one of these. However, I am not emotionally qualified to handle this cringingly horrible piece of Dell bloatware. Every time it does a new weird thing, which is about once every other week, my heart falls.

Even when SupportAssist is working correctly, everything about it is annoying. For example, when it’s processing, it flashes three little waiting dots. One two three. Right? Dot 1 flashes and goes out, dot 2 flashes and goes out, dot 3 does the same, then repeat. Right? RIGHT?

WRONG.

SupportAssist’s first dot flashes correctly, but the second and third flash together. Simultaneously. Every. Single. Time. Even though it’s a stupid superficial thing that doesn’t matter at all, the obviousness of this bug galls the hell out of me. It looks so bad. Also, if your intuition tells you that someone who missed that glaring issue might have missed others, then give that intuition of your a big wet smack on the lips, because it’s a winner.

Problems with SupportAssist abound. I could schpiel on for days about the nonsense I’ve endured with this damnable program, from times I’ve tried to remove it (it reinstalled itself) to times I’ve tried to update it because it was being an enormous heckin’ vulnerability. (Incidentally, during that fascinating episode, SupportAssist actually refused to install. What a world!)

For the past several weeks, I’ve been trying to stop SupportAssist from forcing popup notifications on our patrons. These are just update requests, but they require an admin password, and patrons, skittish darlings that they are, aren’t equipped to deal. Anyway, making any change to these computers requires turning off our disk imager, DeepFreeze, before I make any changes. There are a couple of restarts involved. The process is a bit of a slog, but it’s worth it because DeepFreeze is a great piece of software that keeps everybody’s filthy data off our nice clean library machines.

So I’m not sorry that I’ve been unfreezing and freezing our DeepFreeze clients for the last month, trying to figure out how to make SupportAssist stop yelling at our patrons. That’s just part of the game. I’m also thrilled that our IT consultant figured out a lasting fix – yay! What maddens me is that today, when I tried to apply said fix, I discovered that the issue had begun because SupportAssist had either a. tried to update itself and installed a bad version; b. become universally corrupted on all computers and decided to watch the world burn instead of working; c. decided to ask the user before updating its own bad self while also not being capable of doing that because it was too broken; d. all of the above.

I’m going to go with d. Somehow, it’s d.

That meant that I had to reinstall SupportAssist on each machine just so that I could tell it to never notify the user about its need for updates, driver or otherwise, ever again. It took…a while. I spent a lot of time watching its little waiting dots.

On the bright side, it does seem to have worked. As a certain TV hero once said, I love it when a fix comes together, at least long enough for the program to un-toggle it and/or go wonky so that I have to go back in and start all over again.

Until next month, SupportAssist.


Audiobook Apps And Why They Bring Me Joy

I’m in an enviable position right now. I have too many audiobooks on my phone.

I should back up and say that I have at least two audiobook apps on my phone at all times. Libby is my go-to and my sweet summer darling. I’ve got an eternal fountain of audiobook holds backlisted in OverDrive just so that my Libby cup never runneth dry. And so far, it has not.

Librivox is another one, but I have a tense relationship with the app. LibriVox is a free, nonprofit, public domain book recording and distribution website. I’m not sure if they also created the app. I’m guessing not. The app is free and works well, but it’s ad-supported. All right. OK. We do what we must to keep the lights on, and after all, the books are free.

The ads are for e-cigs.

Not sure where BookDesign got their demographic info if any research went into that decision. Maybe they just couldn’t get any other advertisers. I don’t know. It doesn’t really matter. Listening to a random woman gush about e-cigs after every chapter puts my teeth on edge. Call me an elitist if you must, but e-cigs are the filtereds of our generation and I do not at all believe that they help you to quit smoking. Neither does WebMD. However, there’s also no better way to burn through the classics than with the Librivox app. It even has Apple CarPlay compatibility. If I take up e-cigs, you’ll know why.

Finally, I listen to Libro.fm. I discussed this app when I reviewed Bill Bryson’s THE BODY a few posts ago. It’s the only platform I currently use where I’d pay for books, if that were something that I could afford to do on the regular. Luckily, I’m a librarian who writes voluminously about literature, and therefore, I get advance listener copies from Libro.fm for free. This is new and really, really something. I don’t even know that to do with myself, I’m so excited about it. I have Erin Morgenstern’s The Starless Sea: A Novel ready to go just as soon as I finish Dhalgren. (And oh, my friends, you’d better believe there will be a Dhalgren review.)

Paris Review - Samuel R. Delany, The Art of Fiction No. 210

This man is Samuel R. Delaney, author of Dhalgren. He has taken over my life with his book.

I must have five audiobooks all queued up and ready to inundate my ears. We’re talking solid days of literary wonder. That said, it’s worth mentioning why I listen to so much audio.

I don’t really have time to read.

That’s right! The book woman doesn’t have a minute to crack a cover. This is in part because I spend two-plus hours on the road each weekday driving to and from the library where I work. It also has plenty to do with my secondary job, vis a vis writing, which takes a lot of time. I’d scale back, but we do have this thing we like to do every month called “pay rent.” And, honestly, I love to write. I’d write all day if I could. If I could write about reading all day, I’d do that. And then I’d read too.

yesss baby | Meme Generator

He can’t even read and he’s still psyched.

As things stand, I am but a hardworking librarian with a hefty side hustle, a situation that’s not unusual these days. What I’d really like to know is how many people find themselves in my position. Are we becoming a nation not just of overworked millennials, but of overworked millennial audiobook fans? Are changes in how we work leading to changes in how we read?

It makes you want to sit down with a nice e-cigarette and have a good, long think.


Diary of a Librarian: The Charging Cord Blues

I’ve had a lot of burners on the stove lately. In addition to the biggies, which I won’t discuss because they will bore you, I must keep my Libby-based digital audiobook stash fresh. This means zooming through The Cuckoo’s Calling at 2.5x normal speed so I can read whatever’s just downloaded from my holds list.

The things that stress out librarians.

Also stressing me out is the cost of replacing our charging cords. At my library, we hand out charging cords in exchange for a collateral ID card. Usually, the people who need charging cords are kids, and usually, they don’t have any ID on them.

What am I going to say? No, foolish child! Go file for a state ID and then come see me about this $30 cord after a seven-to-ten day wait for shipping! Ugh. Obviously I let the kids take the cord, and they’re generally pretty honest. I have them write down their name and phone number just in case they forget to bring the cord back, but that would be tough these days. I’ve figured out a way to wire a laminated tag to the plug housing in such a way that it can’t be gotten off without breaking one of the wires.

From now on, any disappearances are definitely theft. Conceptually, disappearances might have been happening before now, but one cord looks very much like another and we’d incorporate enough found cords into our little collection that our supply remained fairly stable. Not that it’s not theft to swap out your busted cord for our nice one. I wouldn’t be 100% surprised if this is why our cords have been aging so fast, because they have been aging fast. One day, the cord is brand-new; the next, it will not charge for god or country.

On the other hand, we also get cord donations occasionally. I’m fairly sure that these are well-meaning, but it results in a couple negative eventualities:

  • The used cords become busted cords more quickly anyway, and since we don’t know the cord’s age we can’t really guess when that will happen
  • We end up with irregular and off-brand cords that don’t work as well as quality ones
  • As bad as lookism is, it’s nice to have a consistent brand, and a random hot green cord disrupts our branding game
  • We always have a ton of Android cords and never have enough iPhone cords.

We’ve flirted with the idea of getting dedicated charging stations for the library before, and although they are fairly expensive, I think they’d solve some of the squirrelly minor issues with lending charging cords. Now that we’ve got to revamp our entire reference floor anyway, it seems like it might finally happen. That said, I sincerely hope that we get one for each floor so that people don’t have to glom onto just one unit.

We’re going to have to be conscious of replaceability if we go with a standalone charging unit a la conference or mall charging kiosk. The other reason that our cords might be aging out so fast might have to do with how patrons are using them. As usual, the root problem is data collection. We don’t really know what the patrons are doing to our equipment, though the imagination paints some interesting pictures, and if we don’t know that, we don’t know nothin’.

On the other hand, we could just gin up some shoeboxes with power strips inside. Added bonus: we could decorate those any way we wanted. Housing options are essentially unlimited. We could use a bread box, a basket – god, one trip to A.C. Moore multiplies the possibilities. There are myriad ways to hide a bus. Maybe we could borrow a few extra dollars from the replace-iPhone-cords discretionary fund for security measures. I figure a few wall anchors, some tastefully disguised chicken wire, and a padlock ought to do the trick.