There are three main reasons I want to encourage noobrarians not to fall into the trap of trying to Do All the Things. First of all, you’re new! People are thrilled that you can sit at the reference desk unattended without drooling or falling asleep and that you know where to send people when they need to fax something. For the first few months, the very best thing you can be doing for your library is learn how to do your job really well. Don’t try to give yourself extra work. Once you’ve learned how to do what’s actually assigned to you, then you can branch out. You can be a tremendous librarian without putting so much stress on yourself. You don’t have to be a rockstar. A much better use of your energy is trying to be the kind of librarian you’d want to work with. Put your energy into that, my friends. And try to be the kind of librarian your patrons want. Maybe that means working on your business reference skills instead of getting on an ALA committee before your 30th birthday [Editor’s note: or even before your 40th]. So be it!

I love this post so very much. As a n00brarian for the second time over (I just started my academic library job in January), I have been trying very hard to remember that right now, the best investment of my time and energy is just in Figuring Out What I’m Supposed To Be Doing. It takes time to learn the job and the workplace culture, *especially* in environments like academia and government.

And remember, “just” doing your job is almost always more than enough to make you seem awesome to your patrons and your coworkers.

I don’t know about “original oversharers”… seems like we may have picked that up from our patrons’ tendency to ramble on about things sometimes. ;-)

But it’s definitely true that there is more and more focus on people, even as we also dabble in all things technological.

(Source: twitter.com)

"I think we’re doing really good work to move ourselves, our institution, and our services forward in meaningful ways. But despite that, we’re not building mind-controlled-robot-arm quality services and initiatives. And I think we need to be, collectively. The future is knocking, and we’re pulling the blinds and waiting for it to come back after we’ve had a chance to tidy up the parlor."

Though libraries have always enabled discovery, we didn’t call it that until it was a software layer. We had catalogs, we had indexes, we had databases, and we had too many of them. Discovery layers to the rescue! This expensive and tricky-to-implement software takes in a simple search query and retrieves sources from all of those different databases. For the busy lower-division undergraduate who doesn’t need to fine-tune a search when all he needs is five scholarly articles, it offers something as easy as Google. Only … it turns out, maybe not. Because Google puts a lot into tweaking the relevance formula;  discovery layers have a hard time being as slick. And in the end, students still have the same frustration. Turns out, it wasn’t that they couldn’t find sources. They simply weren’t finding the perfect source. And discovery layers don’t make that any easier.

This neatly summarizes my own personal skepticism about discovery layer systems. I would much rather point the students to a guide for their subject, which has stuff I’ve personally picked out with the most-likely-to-be-helpful database at the top of the list. But maybe that’s just me. :)

And, as always, the rest of the article is well worth reading.

To say that “librarians are the original search engine” is to concede that search engines do what librarians do, which would be another way of saying that there is no reason to talk to a reference librarian if you can just Google it.

If you want a slogan for a coffee mug, I would prefer to see one with an SAT-style analogy, like, “Librarians are to search engines as astronomers are to telescopes.” People who don’t know much about astronomy can get some use from a telescope, but we understand that with an astronomer’s knowledge it can become much more powerful as a tool for discovery. We would not say, “Astronomers: The original telescope,” and we wouldn’t think for a second that that a slogan like that would be flattering to astronomers or supportive of the astronomy profession.

(Source: freegovinfo.info)

Whether you’re just joining or have been part of this profession for a while, we all have our goals. Ultimately, we want to provide as much as we can in the best possible way in order to make people happy, regardless of what our title or work place looks like.
Except no matter what you do and no matter how hard you work on something, you’re sometimes going to piss people off at the same time, be it patrons or be it your colleagues. There is no way to be an effective change maker or advocate for yourself and services without making someone unhappy.


To be as good as you want to be and to further your goals in providing the best service and experience as a librarian, you have to suck it up and stick to your beliefs.
That’s not to say don’t follow the rules. Just push against them as much as you need to. That’s the only way change can happen. If it means pissing off one or two or six people for the betterment of a community? It’s worth it.

All of her tips are good things to remember.

We’ve recently been through the process of interviewing and hiring several new librarians at my library (yay!!). These were my first times on the other side of the table, so to speak, and interviewing was definitely an eye-opening process. As I was poring through resumes and cover letters and Skyping with candidates, I thought about what advice I would give to people applying for librarian jobs. A lot of this might be stuff you’ve heard elsewhere, but evidently not everyone has heard it.

(Source: twitter.com)

…Librarians begin to believe their value as a wallet and a shopping assistant is an expression of a philosophical value, “to provide the information our community members need.” But that’s a function, not a value. That’s like taking “the customer is always right” as a higher calling. The practices that assume satisfying individual needs are what a library is for runs counter to the communal nature of a library and the deeper values of librarianship.

Here’s my conclusion: ebook models make us choose.  And I don’t mean choosing which catalog, or interface, or set of contract terms we want — though we do make those choices, and they matter. I mean that we choose which values to advance, and which to sacrifice.  We’re making those values choices every time we sign a contract, whether we talk about it or not.

(Source: twitter.com)

While there was a big outcry against SOPA that included protest from many well-known Internet giants like Wikipedia and Reddit, the backlash against CISPA hasn’t had quite as many champions. Some sites that came out against SOPA, like Facebook, are actually pro-CISPA for very self-interested but logical reasons. Along with the American Civil Liberties Union (ACLU) and the Electronic Frontier Foundation (EFF), whose opposition to the bill is frankly no surprise, the American Library Association (ALA) has also come out against CISPA, and in doing so have suddenly become my heroes. Here’s why.

(Source: twitter.com)

Okay, so… I don’t know if this will be of use anyone but me, but I was trying to go over the Computers in Libraries sessions (both those I attended and those I didn’t) to find what I could of the presentation slides/handouts/blog posts and I was getting bogged down in links and files, so I made these lists of links. If anyone knows of stuff that could be on here that I missed, do let me know (use the ‘ask me anything’ link).

Wednesday

Read More

Librarianship is an awareness — a hypervigilance to any needs of a community. Everything we see or come in contact with is collected and disseminated to those who seek that information. On another level, though, we also retain that idea, and can share it with someone else. In that way, librarians are libraries, indexes, databases; polymaths. “Jack of all trades; master of none” no longer applies–librarians are constantly educating themselves and mastering the next big thing. Good librarians are interdisciplinary, as challenging as it is to sustain.

(Source: twitter.com)

Oh, look, it’s actually Thursday now! :)  It’s also the last day I have this week to really get stuff done—tomorrow I’m only working a half-day and have a ref desk shift and an all-hands meeting, so I won’t have much time to focus.

  • Paperwork is first on the agenda: printed expense report in order to be reimbursed for the travel cost of working in the other office yesterday (which required rebooting our massive copy/print/fax machine, which takes FOREVER), tallied up reference question stats for January and collected that sheet and my timesheets to turn in for the month, started new stat sheet for February.
  • Email management: skimmed/deleted new messages, did the filing I couldn’t do yesterday. Checked email periodically throughout the day.
  • Reference monthly report: evidently I’m the first person to put stuff in for the January report, so I created the file and pasted in my bits under the appropriate headings—this involves checking my calendar for committee/inter-unit work, picking a few ‘interesting’ reference questions to mention, and checking my finished tasks for things like training/prof dev items to include. January was a pretty quiet month, in retrospect.
  • First check of my Twitter feed and gmail, but skipped greader for now in favor of getting something done before my 10:30a refdesk shift (it’s easy to skim feeds while on the refdesk).
  • Worked on the announcement that I’ve been poking at for two days. Debating whether to present the improvements as bulleted list or group them into like-items and write a short paragraph about each group. Have now written drafts both ways and I don’t know which is preferable. [I’m probably spending way too much time on this, but it’s the first thing like this that I’ve done, so there’s a lot of agonizing time involved. :) ]
  • Sent both variants (plus a detail question) to the systems guy who did the improvements for an initial critique to make sure I’ve represented things accurately.
  • Two hours on the refdesk. Mostly a quiet shift, but I had one of those exceedingly well-timed interactions where a coworker and I had been discussing who was handling an email about a certain topic (I hadn’t seen it yet, so I skimmed it while we were talking) and right afterward I got a phone reference question on a very closely related topic. So I was able to use some of the information from that email to help the patron. :) Also skimmed Twitter and Tumblr during the shift.
  • Did my Twitter stats wrangling for January while on the refdesk.
  • Upon returning to my desk, I sent the final drafts (haha, talk about a contradiction in terms!) of that new features announcement to the systems guy and the head guy; after this they’ll send it to the entire team for review/critique.
  • Responded to an opinion question about checkboxes within the system’s search results (i.e. when you select a citation, how long should that selection persist? Across pages is obvious, but what if you run a new search? Should they stay or go?).
  • Read some of the articles I found on Twitter and Tumblr during my refdesk shift; added a few things to my Tumblr queue.
  • Reviewed the funds summary report to see if I’m one of the subjects that is guilty of not having made any selections yet this fiscal year—looks like I’ve ordered a few books, whew, but I should find some more. Added that to my to-do list for Monday to consider when I’m reviewing the weekend notifications of new items in GOBI3. (I primarily select for library and computer science but also get item notifications for biotechnology.)
  • Over lunch (which didn’t occur until nearly 2pm, haha, but that’s pretty typical for me) I added notable new Twitter followers to my masterlist. I really ought to convert the list into a database or something rather than the massively messy word doc that it is, but when I started it I don’t think I expected the library account to have so many followers. :)
  • Composed and sent the Twitter summary emails; one general summary goes to most of the library staff—and provides the deadline for the next month’s tweets—then more specific summaries are sent to each of the contact people from the areas that contribute content to the account.
  • Finally tackled my RSS feeds, checked in on Twitter again.
  • Worked a bit on the library tweets for February; scheduled tweets for tues/wed and added a note to my calendar for Monday to check up on the tweets still awaiting approval if I haven’t gotten a response by then (need to have a response in order to go any further with the scheduling). Did as much as I could to work around the missing tweets, including tweaking a few #followfriday posts and adding them to the schedule. Verified links for the tweets I scheduled.

And that’s it for me today.

Today’s soundtrack:

Today I staffed our one-librarian satellite office downtown, so it was pretty much like being on the reference desk all day. With computer problems. It wasn’t even 9 a.m. when I decided the day’s word was probably going to be *headdesk* (or ARGH).

  • Computer at the desk didn’t want to let me log in. Tried restarting it, so of course it had to install Windows Updates (of course!). While it did that, I turned on a different staff computer to see if the problem was systemic; I logged into that one just fine.
  • Computer was still installing updates, so I turned my attention to the reluctantly-opening door. Fortunately, it was an easy fix: the button to automatically open the door got stuck while pushed in, so I pulled it out again and the door returned to its usual self. (I’ve had this problem before when I’ve been here, though that time the door was stuck all the way open. :) )
  • Computer was finally done restarting, and deigned to allow me to log in.
  • So, of course, I couldn’t get Outlook to let me in. Used the web access instead while I attempted to troubleshoot the Outlook settings… key word being ‘attempt’.
  • Oh, look, the computer wants to install *more* updates. All right, all right, install those updates while Outlook tries and fails to connect.
  • Huh, Outlook actually loaded my recent mail. Will this continue? …no, probably not. Attempting to forward a message has frozen it up quite badly.
  • Put Outlook out of its misery and resolve to use the web interface for the day. Some of the windows updates failed, too. Today is just not a good day for this computer, I guess.
  • Start skimming Google Reader items while all of the above stuff was attempting to process. Finish that and go through Twitter feed and Tumblr dashboard.
  • Discovered that the downside to using the work webmail is that most of my email folders aren’t accessible (being in a file on my network drive, not on the email server). Guess I’ll have to let my inbox be a mess today and straighten it out when I’m back at my usual desk tomorrow.
  • Spent a few indecisive moments deciding what to do with myself next. Realized that one potential task would be better held off until I’m back at my desk or else I’ll have to spend a lot of time messing with formatting (going back and forth between Office 03 and Office 07 can be a pain). So I did what I could (collected most recent mentions/retweets for the library Twitter account and added them to the working spreadsheet) and moved that task to tomorrow.
  • Poked at the announcement I’m supposed to be writing. Still not pleased with it yet.
  • Webmail keeps logging me out. Logged back in again… and again… and again…
  • Handled several calls about scheduling meetings in the conference room contained within the library’s area (it’s a popular spot). There were four meetings scheduled there for today, but the folks using it didn’t need my assistance.
  • Had a few reference question calls throughout the day.

Soundtrack of the day: