Continue reading »]]>

This session is happening! Sunday, 11:00 am – 12:15 pm, Room 92. If you’re interested, please (please please please) read and comment on the Googledocs draft session structure!!!

There are a number of ongoing projects that center around structuring, storing, sharing and visualizing data within the humanities, ranging from well-known tools such as Zotero to brand new tools stemming from recent grants that are still being prototyped. These efforts create lots of opportunities, and sharing data between these tools and initiatives benefits the whole DH community. However, designing for and implementing data structures that support this kind of sharing adds a different kind of complexity.

The question is, then, how do think about structuring, organizing, and sharing our data going forward so that our structures are both flexible enough to hook into when we build new tools but structured enough that the data sets would talk to each other? How do we tie together different kinds of data sets (for example, but not limited to: GIS, citation management, prosopography, timeline and event tracking, etc.) in a way that works across several disciplines? How do we structure the data so it integrates well with visualization tools? What are the benefits, costs, and challenges of an undertaking of this kind?

If we break it down even further, we can ask more granular questions about the data we collect when we do research. What kinds of data sets do you have? What kinds of data show up in those sets? What kinds of relationships do you want to analyze between those different kinds of data? How do these questions change (or stay the same) across disciplines?

While it’s not easy to answer questions of this scope in a single session, THATCamp’s unconference format seems like the ideal place to start!

Continue reading »]]>

Don’t talk to me about citations, what I love about Zotero is that I can write a translator that will extract useful structured data (and perhaps images or snapshots) from any old collection database and add it to my own research library. Match that EndNote! It’s Zotero’s capacity as a research manager that really excites me.

A few years ago I wrote a Zotero translator for the National Archives of Australia’s RecordSearch database. It’s been through several versions and can now do some pretty neat stuff. For example, using it and the Zotero add-on for Omeka, I was quickly able to create this mini-exhibition of some of my favourite letters in the Archives. With the arrival of the web API I can imagine even more exciting possibilities — NAA files have unique barcodes, so… barcodes, smart phones, metadata, digital images, Zotero, join the dots!

More generally, writing the translator really set me on a different path because it got me thinking about new ways of extracting, sharing and re-using collection data. With the web API and translators for archives and museums databases, for example, Zotero could become a platform for ‘routine’ crowdsourcing. Enriched metadata created and shared by researchers as part of their own projects could be harvested back into descriptive systems. Users of archives could create their own parallel finding aids alongside the institutional systems.

But there are some problems. The rigidity of the item types system is frustrating, and there really needs to be some way of creating semantic relations both between Zotero items and between an item and some external entity (it’s been talked about for a while).

I’d like a discussion about the future of Zotero that didn’t get too hung up on citations. A discussion that explores Zotero’s capacity to share, not just references, but research, that sketches some of the apps we might build and the collaborations we might create.