Skip to content

Author: Iris

THATcamp Denver Takeaways

Published by Iris on Monday, November 19th, 2012

I’ve been watching blog posts trickle out of THATcamps for years, and this fall I finally got a chance to attend one. As luck would have it, just as Carleton signed onto a Mellon Digital Humanities planning grant with Macalester and St. Olaf, a THATcamp popped up focused specifically on Digital Humanities and Libraries.

What a rich experience. It was populated by such a range of participants: people from large research universities, university presses, centers for digital humanities, OCLC research, major digital libraries, regular old librarians like me, and some disciplinary faculty, and some graduate students. It was a great opportunity to hear from people who are a few years ahead of where we are, to hear what questions they have now, what confusions exist that maybe we can head off before they become issues here, what workflows they’ve arrived at, what kinds of projects may be coming down the pike.

It was also an exhausting experience because the whole time I had to listen not so much to what, exactly, people were saying (since that was usually mostly irrelevant to me) but to patterns underlying the conversations: what kinds of services do institutions provide, are people mostly working in teams or alone, are the teams institutionalized or ad hoc, how do they negotiate the class differences between disciplinary faculty and library or IT partners, where do student research assistants fit into current work, what terminology do people use and where do confusions in terms exist… So many things to listen for and translate into my own context. And often I’d realize that information I’d dismissed earlier as totally irrelevant to me suddenly fit into a new pattern I was noticing, so by the end of the day I was pretty fried.

So what were some of the things that stood out as interesting or important themes or patterns? Well…

Have a Process — Allow for Exceptions

One session was about libraries becoming more involved as publishers since they often house the tools or manage the preservation and access to digital humanities projects. In my case, those tools would probably come from our IT department rather than the library. It was still really interesting, though, to hear the conversation slowly gravitate toward the consensus that in an ideal world institutions would have both a formal publication/preservation process and then also a sort of sandbox publishing process. This second process would accommodate projects that didn’t fit well into the formal containers (journals, books, wikis) or that couldn’t be evaluated in the same way prior to publication (peer review, for example). As one person said, often you have to build a thing before you know if it’s going to be worth anything, so the before-hand evaluation for publication process is largely impossible in these cases.

And in fact this became one of the major themes of the day for me. It seems that in order to support digital humanities projects, the goal is always to have the project based in tools, support structures, and data that are already present and ready for that kind of project. But there are also a lot of projects that simply won’t fit into existing structures, and so many programs provided capacity to work on these “boutique” projects. One woman had a phrase I really liked, saying that she looked at these as “first of a kind projects, rather than one of a kind projects.” The idea is to use these boutique projects to develop tools or services that the become part of the standard suite of support options, therefore taking less effort the next time.

Collaboration is Difficult and Necessary

This has been a theme not just of this gathering, but of every digital-humanities-related gathering I’ve attended or heard of. One humanist at St. Olaf said point blank that the humanities have traditionally been a realm of solo work so humanists don’t really know how to play well with others. They lose control of the process, the timeline, and the outcome, and the conclusions aren’t necessarily fully their own. Another humanist at a conference hosted this fall at Carleton spoke bluntly about how this “go it alone” attitude can easily translated into almost a master/servant relationship when collaborations mix faculty and staff because this relationship fits more easily into disciplinary practices that privilege solo work. “This is my project. Please make this thing happen in the way I want.”

Library Disciplinarity

While I was at THATcamp, I started thinking that one way to think about these projects so that they maintained their collaborative nature would be to think of it almost as interdisciplinary work, where the library is a discipline more than it is a service. The library has hundreds of years of disciplinary experience with finding, organizing, using, preserving, and making accessible digital and physical items. We study the rich complexity of the interstitial spaces between discrete pieces of instantiated knowledge. We study the socio-cultural practices that develop in these spaces and that draw dynamic connections between the items. To think of ourselves as “just” a service organization is to sell ourselves short and to relegate ourselves to perpetual outsiders in these ideally collaborative pursuits.

For this reason, I also really appreciated the ways that some institutions have “Digital Scholarship” programs rather than “Digital Humanities” programs. From the CS and Library perspectives, we bring very similar portions of our disciplinary training to projects from the Humanities and the Social Sciences, so there is really no need to have separate programs to support the various disciplines. (No need, that is, after the humanities have had a chance to acclimatize themselves to this new realm of scholarship. I can absolutely see how having dedicated energies directed to the humanities is important when first getting digital humanities off the ground.)

Some Practicalities

People at THATcamp were justifiably concerned about the sustainability and scalability of their programs. Some had decided that they would provide consulting support only or that they would cap the number of active digital humanities projects they could support at any given time (with a wait list for people once an active project graduated or died). Several found that they were in high demand to help scholars develop data management plans now that humanities scholars were applying for grants that require those, and that this had been an unanticipated and heavy demand on their time. And other libraries pointed out that rather than being all things to all projects, they would specialize — so Library A might specialize in text analysis and Library B might specialize in GIS applications for humanities. Most make use of graduate student work (we intend to employ undergraduates here).

It also became clear that initial conversations in the planning stages for a project should include some discussion of how permanent the end result is intended to be. Is this something closer to an item in our “circulating collection” that can be weeded when use dwindles and space gets tight? Or is this more like an item in “special collections” that requires greater commitment to long-term care? Who will be responsible for the server space and upgrades? Who is the intended audience and how will we get it to them? If it is interactive, how much of a change log should be available, and how much control do we exert over the kind and type of interactivity? Questions like this are not just procedural, it turns out, but can actually shape the project itself on a fundamental level.

And finally, it turns out that most projects need (but do not have) good graphic design. This is especially important for projects that involve crowdsourcing. And if you’re after interactivity, you’d best have thought about how to get people to participate (I’m reminded of Riedl’s research for this problem).

Comments closed

Becoming a Linguistics Librarian

Published by Iris on Monday, October 29th, 2012

When I started here I had degrees in English and a degree in Library and Information Science. But I was also the librarian for languages, music, linguistics, and American Studies. A while ago I wrote about important things I learned about being a music librarian (part 1 and part 2), and about being a librarian for language departments. Well, for the last week or so, I’ve been sitting in on a linguistics class, and over the last year or so I’ve been working more closely with their upper division classes, and here are a few things I’ve learned in the process.

The Field

From the perspective of the interested outsider and the helper of undergraduates, the field is easiest for me to think of if I liken each branch of it to other fields. So there are the neuroscience-linguists, and the psychologist-linguists, and the sociologist-linguists. And lo and behold, that helps when picking databases and search terms. Happy librarian! PsycINFO and Sociological Abstracts can come in really handy to flesh out the Primary Duo (i.e. Linguistics & Language Behavior Abstracts and the MLA International Bibliography).

Linguistic Data

Linguists talk all the time about data and about datasets. When they do this, they mean “example sentences” or “example sounds.” So a grammar of Turkish is full of data on the Turkish language (which is distinct from a book on the grammar of Turkish, which may or may not be all that full of data). So if students want data on Turkish, I’d look for a grammar, I’d look for articles on a particular construction or sound in Turkish, and I’d look for researcher websites (using the “site:.edu” limiter in google, usually) where researchers put up their linguistic datasets.

If I were going after a much lesser known/studied language, SIL and researcher websites are probably the best bet. I find SIL’s website hard to navigate, so I search it using Google.

If there’s “nothing on my topic” I’d use Ethnologue and find related languages and see if they can be useful by analogy.

Currency Oddity

Linguistics is odd in that some of the sources need to be very current indeed, particularly the parts having to do with brain science. Meanwhile, other parts of the field rely heavily on books that are 50, 60, or 80 years old. Typically, complete descriptions of languages are only done once and then amended in the literature, so it shouldn’t be very surprising if the primary source of primary data comes from a well worn book written by some African explorer in the 1920s.

Navigating the Jargon (with undergrads)

Linguistics is jargon-heavy. I often can’t even make out the wikipedia articles on the topics I’m supporting. But just like being a librarian for foreign languages, this is a good reminder for me to keep my consultations highly collaborative with the student. They supply the terms, I suggest ways to come up with terms (“what kind of a thing is a genitive? a Case? Ok, so what if we look for Russian cases if we’re not finding what we want when searching for Russian Genitives?”). They interpret the results while I give them pointers about categories of things to watch for in the results.

Jargon is also your friend because it makes keyword searching so much easier than in the humanities. “Ergative-Absolutive” is far more likely to return accurate results than “performance of self” regardless of my level of understanding.

My next steps

I’ve been pretty happy with my research guide for Linguistics, and they’ve said that it’s very useful. But now that I’ve sat in on a couple of class sessions I think I’ll add a tab on gathering linguistic data. And if I can, I’ll try to sit in on some different classes next term.

4 Comments

Good searching really isn’t about searching

Published by Iris on Wednesday, October 10th, 2012

I’m a librarian. My brand is Search. And I do a lot of searching every day, and I know a lot of fancy ways of making that search go well for me (much of the time). But today a chance comment underscored something I think I’ve always known: good searching really isn’t about Search, or at least not in the way that people think of Search.

Here’s what happened this morning. I’m part of a grant-funded “iPad Learning Community” on campus. We get iPads (woo!) and we commit to attending learning community sessions several times during fall term to build a better understanding of how iPads work with higher education. So I’ve been doing a lot of experimenting with iPads lately, and one of my favorite things to do on an iPad is read and annotate PDFs (I’ve been using iAnnotate, though I just got Good Reader to play with, too). The thing is, it gets very tiring to write without letting your palm hit the iPad surface, and if your palm hits the iPad surface it can suddenly not tell where the tip of your finger or stylus is and so annotation goes all wonky.

So I fired up my trusty Google, and typed in iPad stylus wrist guard thinking that these were probably terrible search terms but thinking that any page that used all of those terms would probably talk about the problem I was having. Even if all I found was someone else talking about the problem, I might learn better ways to ask the question, or see someone’s answer to the question. Meanwhile, Google suggested as I typed, and thought maybe I should search for iPad stylus wrist protection, which seemed reasonable to me, so I hit “search.”

I don’t remember the next steps very clearly because this was yesterday, and yesterday is a long time ago, and I did it all really fast and without thinking too hard because this is what I do for a living — find stuff when I don’t really know what I’m looking for or how to ask the question. But eventually I learned that there’s a useful term, “palm rejection,” which is the name of a feature that people aim for in tablet applications. So I searched for iPad palm rejection and came up with some pretty useful results, including a site recommending a glove that I’m going to try out.

When I got to the learning community thing this morning, I said I’d found this glove and one of the technologists asked “how did you figure out that it was called palm rejection?” (None of us had heard the term before.) I said, kind of flippantly, “I’m a librarian!”

But then I realized that yes, it was because I had a different goal in mind for searching in the first place. I was first searching for terminology that would help me do a good search. And that’s what I do with students all the time — work with them to figure out what some key terminology might be so that they can make those search boxes work for them.

So I guess good searching, at least in the case of novices looking for information, is often more about learning to look for clues than it is about fancy search strings.

3 Comments
Why yes, I have been teaching in my office lately

Why yes, I have been teaching in my office lately

Published by Iris on Monday, October 1st, 2012

It’s been and instruction filled couple of weeks in my neck of the woods, both in classrooms and in my office.

Here you see snippets of me teaching indexing rules for the MLA International Bibliography, mind mapping a couple of students’ topics with them, and teaching AND and OR.

20121001-140211.jpg

Comments closed