Comments on: Design Patterns for DH Projects The Humanities and Technology Camp Tue, 08 Mar 2011 21:52:08 +0000 hourly 1 By: karindalziel Sat, 22 May 2010 19:31:34 +0000 Here are my abbreviated notes for the session, ideas to help with project preservation:

* use virtualization for older platforms
* design site as static as data allows from the beginning
* limit the number of platforms, esp. ones with data export
* design sites that degrade gracefully in loss of technology
* create a video/screenshots, etc of a site as a form of documentation – it records the site’s functionality which can be ephemeral
* think of the site as layers – separate, for instance, map stuff (KML) from presentation
* make your site available for lots of copies
* available for spidering (e.g static HTML version)
* clonable repositories
* open licensing
* Documenting – white paper at the end of a project, talking about the idea behind the project. Should be a joint effort between scholars and coders
* Use standards
* Create content people care about 😉

Also, group discussed whether every project needs preservation & why there is no digital humanities version of Yelp for projects/tools and what would have to change in order for that to change (it comes down to solving the “social capital problem”).

By: THATCamp 2010 » Blog Archive Sat, 22 May 2010 01:25:21 +0000 […] and standards remain a topic of interest to me: Hugh Cayless proposes that we take a serious look at how new design patterns could help digital humanists […]

By: Hugh Cayless Tue, 18 May 2010 01:59:43 +0000 Sounds like there’s interest in linked data and design patterns too. For what it’s worth, I wrote a fairly detailed post on the linked data stuff I did for on my blog. A lot of the things you’d want to do in preparation for linked data work are also good design patterns, like treating entities (people, places, etc.) as resources and having separate (well designed) URIs for them.

By: THATCamp 2010 » Blog Archive Mon, 17 May 2010 13:48:51 +0000 […] to digital forms later on. In many ways, this points to individual application of themes that Hugh Cayless mentioned in his post. How should the lone scholar deal with archival resources that are not […]

By: karindalziel Mon, 17 May 2010 12:04:34 +0000 This session idea ties into my (more loosely defined) session idea. In mine, I generally want to talk about what we can do to make projects sustainable in the long term, even if that means giving up some of the “cool” stuff (I’m thinking interactive maps and flash based things) in the long term but keeping the data, metadata, high res images, and databases available for download.

By: THATCamp 2010 » Blog Archive Mon, 17 May 2010 11:59:03 +0000 […] version, to be deployed in case of a loss of technology. (Also of interest is Hugh Cayless’s session proposal). Some sites don’t have such easy answers, like older GIS sites that depend on a specific […]

By: Jon Voss Sat, 15 May 2010 22:56:47 +0000 I’m very interested in the Linked Data angle of this. I’m coming it at it from a less technical background, but have been working with Freebase, Internet Archive, and the Archives of Michigan to explore using Freebase as a semantic publishing platform and building apps around Civil War metadata from national and state sources. It’s been pretty slow going, but we’re confronting a lot of useful conceptual and technical questions as we go. More info here:

By: Patrick Murray-John Fri, 14 May 2010 13:59:10 +0000 I just have to say, hooray for how far RDF/Linked Data has come since the 1st THATCamp. It was mostly a curiosity then, and it’s really exciting to see you talking about it in terms of a specific project!

In other words, I’m totally there.

So far, I spend my time in javascript and PHP, so the tools I’m familiar with are ARC ( and manipulating the RDF/JSON format (haven’t used the jQuery plugin that’s supposed to do RDF).

The nice thing about ARC is the plugin that serializes graph to the SIMILE/Exhibit format, which lets you start up visualizations and navigations pretty quickly and easily, at least for smallish datasets per page.

Would love to talk about these ideas at THATCamp!