I am increasingly convinced that #DigitalHumanities cannot and should not be operated as a service—of the library or any other unit. We should not be hiring people to help others do #DH. We should hire people to do #DH themselves. Those people should be faculty, yes, but also librarians, archivists, developers, designers, and managers. And they should be empowered to range the campus to build teams of their own making to work on ideas of their own devising.

Putting people in service to others’ work doesn’t scale, isn’t sustainable, and, most importantly, produces bad work. When administrators (especially library directors) recruit a “digital scholarship librarian” or similar to support digital humanities on their campuses, they’re setting them up to fail. @dh

@dh @foundhistory As a DH librarian hired to create a library space for a burgeoning community, it often feels like I’ve been set up to fail. But I’ve also worked to shape the space not as a “service point” and more as a values-based place for exploration, collaboration and partnership. I’m at an R2 with an insufficiently funded library (what academic library isn’t?) and I wonder if this institutional context necessitates an approach that emphasizes capacity building over services. DH in our library is me (w a FTE staff line to be filled) so we don’t have a team of experts who can do things for faculty. Very few of our faculty approach me with that expectation (it helps that librarians on my campus are faculty in full standing). The tension in part is that admin thinks of what I do as a service and I think of it as a partnership. Either way, what we’ve built is currently unsustainable 😔