Tag: professional

What did I do this year? 2013–14 edition

Voyant word cloud of 2013-14 activities

It’s self-evaluation time again! It’s the second year I’ve had to do this for my current job. Last year, I found it enormously helpful to quantify and visualize the activities I’d done in the given time period. I use the daily “Done today” entries I write in Evernote, a Python script I wrote last year, the BeautifulSoup Python library, and Voyant Tools to get a holistic look at what I did this year.

Voyant Tools allow different views of the data. One is Cirrus word clouds. (When used in combo with other data tools, word clouds are useful.) The image at the top of this entry is the word cloud that ignores common stop words, my colleagues’ names, and the words ref, desk, email/s/ed, met, meeting, talked, hr (hour), and sent.

Here’s the word cloud that only ignores common stop words:

Read more

Rethinking what I do as an emerging tech librarian

I get asked often what it is I do, exactly, and I still don’t have my elevator pitch down pat. I usually choose to view that as a good thing, because I value the freedom to explore new territories and direct my own projects. However, a few recent reads have given me pause, and I’m rethinking my approach to my job as the new semester looms.

But first, a general look: what are other emerging tech librarians doing?

Duties & skills

At the end of April, IFLA published a paper by Tara Radniecki titled “Study on emerging technologies librarians: how a new library position and its competencies are evolving to meet the technology and information needs of libraries and their patrons.” It’s a quantitative attempt to answer the question of what people with that title do, know, and wish they knew. Radniecki compares job ads to survey responses with interesting results. A few insights from her paper, which is certainly worth a read, interspersed with my unsolicited personal opinions:

  • 41.8% of job ads cite reference as a duty; 72% of librarians reported doing reference work. Similarly, 38.8% of job ads cite info literacy and instruction as a duty; 61% of librarians reported doing instructional work.
    • This aligns with my own experience as an ETL. I never took a reference or instruction class for my MLIS, assuming that I wouldn’t be doing traditional librarianship. Although my job’s description didn’t mention reference/instruction, I’m at the reference desk a few hours a week, and in fact I really value it — otherwise I might not work with students face-to-face at all, which would be a terrible place to start when designing systems and interfaces for them.
  • 23.9% of job ads required skills/experience in social media, web 2.0, and outreach.
    • I’m surprised it’s not a higher percentage. I’m of the opinion that all librarians ought to be familiar with social media. Look, this time last year, I would have rolled my eyes at this — it’s such an old buzzword by now — and yet I’ve seen too many academic people/departments fail to grasp online social etiquette.
  • 94% of librarians surveyed said they needed additional skills in computer programming and coding, versus only 16.4% of job ads requiring those skills and 10.4% preferring them.
    • Yes. I came into my position with years of web experience but minimal programming skills. One thing I’ve enjoyed is the impetus to get up to speed on web tech, Python, and code libraries I might not have otherwise had reason to, but it can be rough playing catch-up so much of the time.

Still, looking at numbers and general duties, it’s hard to see what ETLs do. As for me, some of my projects are the usual deliverables — design/upgrade/maintain library website, for example — and others are more playful, like tinkering with Arduino. (You can see a quick summary of my first year’s projects here.) So what exactly are others up to? I suppose that’s what discussion groups, online networks, and excitable conversations are for. And in fact, CUNY librarians, the first Emerging Tech Committee meeting of the year is coming up! 

Tech criticism

“Librarian Shipwreck” wrote a long-ish response to Radniecki’s paper in a July blog post entitled, “Will Technological Critique Emerge with Emerging Technology Librarians?” (h/t Patrick Williams). The post is pretty prickly, and sometimes unfair, and its metaphors abound — but here’s one choice quote that I’m 100% behind (after the first clause):

But for the ETL to have any value other than as another soon-to-crumble-levy against the technological tide, what is essential is that the position develop a critical stance towards technology. A stance that will benefit libraries, those libraries serve, and hopefully have an effect on the larger societal conversation about technology. […] A critical stance towards technology allows for librarians to act as good stewards not only of public resources but also of public trust.

This summer has thrown the imperative of technology criticism into sharp relief for me. At the EMDA Institute, we spent a few days examining how EEBO came to be, perhaps best described in an excellent upcoming JASIST article by Bonnie Mak, “Archaeology of a Digitization.” As a room well-populated with early modern scholars, we thought we knew what it was, but after talking about its invisible labor (TCP), obscured histories (war, microfilm), and problematic remediations, we were struck by how EEBO is just one relatively benign instance of a black box we might use daily. What does it take to really know where your resource comes from, and why it is the way it is?

Moreover, the summer of surveillance leaks is exacerbating our collective ignorance of and anxieties about the technologies we rely on every day. I suspect few of us are changing our web habits at all, despite the furor. I talk about it daily, yet I struggle to understand what’s really going on — let alone how I should respond professionally. Originally, I viewed my function at John Jay as a maker, creator, connector of technologies. But technology is never neutral, and I’m starting to see pause and critique as part of my charge, too.

Digital literacy

When our digital world works, it’s beautiful. When it doesn’t, it’s a black box — a black hole — that can frustrate conspicuously or break invisibly. How can we, for instance, impart to students the level of digital literacy required to understand how a personalized search engine works and how it might fail them, when it so frictionlessly serves up top results they’ll use without scrolling below the fold? Marc Scott penned a popular July blog post titled “Kids can’t use computers… and this is why it should worry you.” I won’t summarize — you should read it. Twice.

Librarians have taught students information literacy for a long time. While knowing how to spot a scholarly resource from a dud is essential, understanding systems is now equally necessary, but harder to teach — and harder to grasp, too.


So there’s where I am: trying to understand the ethics of being an emerging technologies librarian; overplanning making things and delivering on projects; prioritizing instructing students, colleagues, and peers about things I struggle to comprehend or explain; simultaneously expecting myself to embody a defensive paranoia and a wild exploratory spirit.

What did I do this year?

180+ notes
180+ notes

I’ve mentioned before that I keep a professional journal as a quick way to keep tabs on the projects I’m doing and what I should be focusing on. It takes the form of a 3-part note in Evernote: Done, To Do, and Backburner.

My annual evaluation is coming up, for which I have to write a self-evaluation summarizing all the things I did this year. It’s hard to slow down and think big-picture, and it’s hard to remember what exactly my priorities were last fall when I’m so caught up in what I’m doing now.

Output as HTML
Output as HTML

To get a jump-start, I wrote a tiny Python script to iterate through my notes (exported to HTML). Using BeautifulSoup to climb the trees of my messy and non-standardized notes, it lists out all the things I marked “Done” since September.

I fed the plain text into Voyant Tools, “a web-based reading and analysis environment for digital texts.” It’s probably more interesting and helpful if you use a larger text, but my 8,900-word text had analyses of interest too.

Word cloud using Cirrus in Voyant Tools
Word cloud using Cirrus in Voyant Tools. Stopwords: Taporware & names of colleagues

Some of these aren’t so surprising. Oh, really, I went to lots of meetings and sent lots of emails? But it’s also easy to see that my priorities for most of the year centered on building the new library website (usability, git, drupal, database) with some side projects thrown in (signs, guides, newsletter, IA).

Here are the word frequency data from Voyant for words occurring more than 25 times (stop words included):

Words in the Entire Corpus. Corpus Term Frequencies provides an ordered list for all the terms’ frequencies appearing in a corpus. As well additional columns can be toggled to show other statistical information, including a small line graph for term frequency across the corpus.

Voyant Tools, Stéfan Sinclair & Geoffrey Rockwell (©2013) Privacy v. 3.0 beta (4583)

word count z-score mean
to 286 23.51 321.1
and 241 19.77 270.6
with 205 16.77 230.2
for 178 14.52 199.9
about 155 12.60 174.0
on 131 10.60 147.1
the 96 7.69 107.8
in 92 7.36 103.3
up 81 6.44 90.9
of 79 6.27 88.7
bonnie 72 5.69 80.8
meeting 59 4.61 66.2
sent 59 4.61 66.2
a 54 4.19 60.6
page 53 4.11 59.5
new 47 3.61 52.8
talked 47 3.61 52.8
email 43 3.27 48.3
emailed 43 3.27 48.3
mandy 43 3.27 48.3
ref 41 3.11 46.0
desk 40 3.02 44.9
all 38 2.86 42.7
blog 36 2.69 40.4
out 36 2.69 40.4
at 35 2.61 39.3
will 35 2.61 39.3
made 34 2.53 38.2
site 34 2.53 38.2
library 32 2.36 35.9
from 31 2.28 34.8
met 31 2.28 34.8
it 30 2.19 33.7
usability 30 2.19 33.7
be 29 2.11 32.6
signs 29 2.11 32.6
1 28 2.03 31.4
is 28 2.03 31.4
marta 28 2.03 31.4
post 28 2.03 31.4
database 27 1.94 30.3
faculty 27 1.94 30.3
more 27 1.94 30.3
not 27 1.94 30.3
test 27 1.94 30.3
2 26 1.86 29.2
added 25 1.78 28.1
asked 25 1.78 28.1
drupal 25 1.78 28.1
fixed 25 1.78 28.1


Word counts aren’t the whole story, obvs, but it’s a good place to start for my self-evaluation!