asking for it

A report published this week by OCLC Research asks the burning question of no one, no where: “Does every research library need a digital humanities center?” The answer, of course, is of course not.

Of course, I’m being rude. The click-bait question, as posed, had a foregone conclusion — but there’s much to recommend in the report, even if it fails to define a “DH center” in any clear way, makes an unwarranted assumption that “DH academics” and librarians exist in mutually-exclusive categories, and bases too much of its understanding of faculty and researcher perceptions on the inadequate sample of some conference-going and a couple of focus groups (however carefully convened and accurately reported).

The chief value of the report may lie in its stated and implied purposes: providing library directors with a set of options to consider (stated) and an easy citation — a bit of OCLC back-up — (implied) for the local arguments they must formulate in the event their provosts or presidents catch Library-based DH Center-itis and seem completely unwilling to entertain a model customized to the needs of the institution. Wait a minute. That will never happen.

Okay, the chief value of the report is in its clear reinforcement of the notion that a one-size-fits-all approach to digital scholarship support never fits all. Continue reading “asking for it”

how we learned to start/stop “speaking in code”

[UPDATE: #codespeak is over and was a smashing success. See a post on outcomes, including a kit for hosting similar gatherings, here. This entry is cross-posted from the Re:Thinking blog at CLIR, the Council on Library and Information Resources, where I’m honored to be serving as Distinguished Presidential Fellow. Check out all the great content at CLIR!]

Here’s a consummation devoutly to be wished: digital humanities research and practice becomes its best self, and finds scholars and technology staff engaging as peers in mutually intelligible conversation. It sounds like a modest hope, until you reflect on how far we are from achieving that vision.

Communications gaps are deep and broad, even among humanities-trained software developers and the scholars with whom they collaborate. Much (not all) knowledge advances in software development through hands-on, journeyman learning experiences and the iterative, often-collaborative development of built objects and systems. Much (not all) knowledge advances in humanities scholarship through fixed and fluid kinds of academic discourse: referential, prosy, often agonistic. A real division exists in style and practice, even when the subjects and objects of humanities inquiry are the same. What might bridge a gap like that? And can we move past an historical moment in the academy, in which the onus is almost entirely placed on archivally and theoretically trained humanities scholars to become tech-savvy digital humanists—to build a concomitant sense of momentum, responsibility, and opportunity in our community of DH software engineers? Can we build greater community itself, just by making a space in which such problems are addressed? Continue reading “how we learned to start/stop “speaking in code””

too small to fail

[This (minus the ad-libbing, and skipping a pre-amble) is the text of a keynote talk I gave last month, at the second annual conference of the Japanese Association for Digital Humanities. I was invited to Tokyo to speak on the history and ethos of the Scholars’ Lab at UVa. I offer here… the whole scoop, and pretty much my entire playbook!]

The Scholars’ Lab is unusual in many ways—not least in the fact that we are simultaneously almost new and twenty years old. Paradoxes abound: we operate with a great deal of independence, and yet are more deeply and fundamentally inter-connected with other administrative divisions of our institution than many North American DH centers can claim (or perhaps would desire) to be. And, in a way, we’re not a center at all. We are a small department of the University of Virginia Library.

That position in our institutional org chart leads to a further incongruity: in a library that prides itself above all things on providing the highest possible level of service to researchers, we are—with the big, circular reference desk and bright, open, publicly-available computer lab that define our space—a service-oriented department. Yet we also work hard to call under-examined notions of digital humanities “service” into question, as our staff (primarily available to students and scholars for consultation and project development) also develop and communicate their own intellectual, artistic, and scholarly research agendas—and as we conduct collective experiments and host ongoing discussions on the changing nature of knowledge work in the academy.

But let’s not leave the paradoxes just yet—because, when it comes to the Scholars’ Lab, I can also assert that we are big and little at the same time. Thus the title of my talk: “Too Small to Fail.”

This is of course a play on a message we heard around the world in the wake of the global financial crisis, offered in justification of government bank bail-out schemes: a notion that certain corporations dominating our economy have become giants among men. They have been made “too big to fail.” It is an approach some digital humanities centers try to emulate, on their local scenes. But the Scholars’ Lab occupies a different space. Today I’ll give examples of the way we meditate on smallness as a virtue. But more importantly, I’ll discuss our attitude toward the other half of the “too big” equation—toward failure. At the SLab, we like to think we’re always ready to fail well, which is to say, that we’re capable of enabling and celebrating failures that have been executed on the proper scale and with the proper attitude.

Continue reading “too small to fail”

praxis, through prisms

This is just a quick post to share two bits of news about our Praxis Program at the Scholars’ Lab. The first is that I’ve written an op-ed on Praxis and our Fellows’ practicum project for this year’s Digital Campus special issue of the Chronicle of Higher Education.

The piece was originally titled “Praxis, Through Prisms” — now “A Digital Boot Camp for Grad Students in the Humanities.” It’s pay-walled, for now, but I’ll re-publish it in open access format in 30 days. [UPDATE: now available in PDF format in UVa’s institutional repository.]

prismatic badge
by Chad Hagen for The Chronicle
Check it out to learn more about the program, get a sneak peek at Prism (launching this Tuesday, which is the second newsflash! congrats, team!) and find out what I see as the great project of humanities computing / digital humanities. Spoiler: it’s “the development of a hermeneutic — a concept and practice of interpretation — parallel to that of the dominant, postwar, theory-driven humanities: a way of performing cultural and aesthetic criticism less through solitary points of view expressed in language, and more in team-based acts of building.”

Or, in other words, the kind of thing our amazing grad students and diverse crew of scholar-practitioners are working on at Praxis. Through Prism(s).

Continue reading “praxis, through prisms”