My public notes from today’s session: tinyurl.com/ch9e37f   We discussed possibly forming a Google Group to share instructional materials … Comment here and I can create the group or determine other forms of alt-communication.  Snack time!

Here are my notes for the second session on collaborations between faculty and librarians on digital humanities projects:   bit.ly/Wk1wOz

I should note that we broke out into three sub-groups, and these notes are primarily from my sub-group.  So I encourage the notetakers from the other sub-groups to post your notes in this post as well!

This proposal is less a calculated intervention and more (in the spirit of THATCamp?) a loose whirlwind of things I’ve been thinking about. Also, I notice we have a number of good proposals for discussion sessions—I’m looking forward to Re-Skilling for Research and one on doing DH instruction—so I thought, in the interest of balance, I would try to come up with a session based around making something (or at least trying to).

There are two proximate inspirations for this proposal. The first is the brilliant and beautiful new Web site unveiled by the Rijks Museum (may we all be so good as to copy it): www.rijksmuseum.nl/en. One of the best things about the site is that everyone is encouraged to download hi-res versions of images and to re-use them—and it is dead simple to do. The second inspiration is the great work that Tim Sherratt (@wragge) has done and continues to do with digital collections at a variety of Australian institutions. (Seriously, someone give this man a job.) I particularly recommend looking carefully at the work Sherratt has done with digitized collections from the National Archives of Australia in projects like Invisible Australians.

As I’m sure is the case at everyone’s institutions, we have digitized some wonderful things at Maryland (childrens’ books printed during the American occupation of Japan after World War II, anyone?) but how hard does a prospective (prospecting?) digital humanist have to work to get access to these things? In many places (including MPOW), they have to work way too hard. Bravo to those who have APIs or download functions as easy as the Rijks Museum. For the most part, my hunch is that whether it’s Fedora, DSpace, ContentDM, etc., etc. — we’re often putting collections out there in ways that make them easy (or easier) to search and browse, but not to download, remix, re-make, re-present, and create with.

So, with all that said, what I propose is to devote a session and a small share of our insider knowledge (as the custodians of these access systems and discovery layers) to figuring out how to pull down some of this cool digital stuff and get it ready to use in ways that digital humanists might be apt to want to do. How long does it take? Are the terms and conditions clear? What might it be possible to make or at least concretely imagine making with the goods we can “liberate” from our collective digital collections?

Maybe that all sounds too messy or too hard to do in an unconference session but I’d at least like to try. I think we’ll find out some interesting things by dumping all the crayons on the table and making a mess.

What knowledge, skills and experience are needed by library staff to support Digital Humanities initiatives at the university?  This is different from actually “doing” digital humanities in the academic library.  -Deb Morley, MIT Libraries

Hello all,

I’m interested in hearing how people are collaborating with faculty on digital humanities research projects. My experiences have been limited to obtaining data sets for them, introducing them to DH tools, and/or connecting them to campus centers that have the computing tools they need. But with the rise in libraries becoming research partners who are being written into grants and all, I’d like to learn more about strategies for partnering with faculty on research projects.

How have DH projects evolved from “boutique” to modular/sustainable over the years? What are faculty, librarians, and academic technologists at your institution or organization doing to create sustainable, adaptable models that can be used by multiple DH projects? Why have some of the DH projects (Bamboo, etc.) not gained more momentum? How do we share common frameworks and components to make DH projects simpler to build and maintain? How do we resource projects that require maintenance and enhancement over time, and how do we reduce costs by leveraging existing tools and standards?