May 14th, 2010 | hugh cayless
In my proposal, I listed 3 ideas:
1) I’ve recently started work on linked data for papyri.info, using data harvested from different parts of the collection and an RDF triplestore that provides entry points to the data from many angles. I’m very interested in tools and methods for doing this kind of work.
2) I’m co-PI on a project focused on linking text with digital images of text, and annotations, possible topics there include tools for working online with digital images, SVG, TEI facsimile, and/or transcription theory.
3) System design principles for digital humanities projects. I’d like to talk about ways of modeling information and delivery systems so that they are loosely coupled, RESTful, sustainable, easier to archive, and easier to integrate with other projects.
After a bit of reflection, I think these are all going in the same general direction, which is probably closest to #3. We’ve been doing online DH projects long enough that maybe we can start to distil useful patterns for representing types of data, handling the linkages between entities, formats and methods for encoding information, and interfaces for managing and interacting with information.
Can we come up with patterns for handling things like:
- Digitized manuscripts
- Geographic visualizations
- Data aggregation
- Search interfaces
I’m not so much talking about the implementation details here as the affordances. What ought you to be able to do with a project that exposes a lot of images, for example? I think the images should be available at high resolution, but should also be viewable in a browser in such a way that you can zoom, pan, and link to a particular view. That’s what I mean by a design pattern. Questions of “how” including toolsets, frameworks, and formats are interesting too, but those are often going to be dictated by the environment.
A few more patterns/practices off the top of my head:
- License with CC-BY
- Make data available as a single download
- Pay attention to URI design
What do you think?