For the last two years, I have been very interested in visualizing data that emerges within my particular field: literature. This interest emerged as I read Moretti’s Graphs, Maps, Trees at the same time that I was experimenting with using GIS tools like Google Earth as a portion of the analysis in the last chapter of my dissertation. In my last year as a graduate student, a fellowship in the Emory Center for Interactive Teaching gave me additional time to begin experimenting with timelines. Timelines in literary studies were nothing new, but I wondered if it would be possible to have a class collaboratively build one in a manner similar to writing a wiki. The result was–in turn–a collaboration with Jason Jones (@jbj) where I coded a timeline, he designed an assignment, and his students created the data for a timeline of the Victorian Age. I’ve since had the chance to play with the tool in my own classes.

Jason and I both thought that timelines would be a fruitful subject for conversation THATCampers. And as many others have done, I thought I would share my original THATCamp proposal and then propose some ideas about where a discussion might go:

I would like discuss the different web-based tools and software that can be used to produce interactive and collaborative timelines. The presentation would involve demonstrating the different tools, showing the strengths and the weaknesses of each one, and producing a finished product. The tools would range from CHNM’s Timeline Builder to xtimeline and from Bee Docs Timeline 3D to the Timeline and Exhibit widgets that were developed in MIT’s Simile project. Having already spent some time with these tools, I think that the tools from Simile might be the most interesting to THATCamp participants due to their flexibility in representing data in multiple ways, including color coding events, sorting events, and with GIS data, as well as the ability to grab data from sources as diverse as a Google Docs spreadsheet or Twitter. Perhaps the best demonstration of the usefulness of a timeline would be to create–during the session/event–a timeline of THATCamp.

My current thinking:

As I’ve been preparing for THATCamp, I have gone ahead and evaluated as many of the timeline tools as I’ve had time for. I’ll be looking at another one or two tomorrow. I’ve gone ahead and created a spreadsheet listing the abilities of these different tools, along with some evaluation. Admittedly, some of the categories that I was using to evaluate the timelines stem from my deep involvement with the Simile widgets, and so the cases might not stack up as being completely fair to the competition.

Also, wanting to blend together both streams of data visualization that seemed valuable to me, I’ve also expanded on the original timelines that I designed for my courses by adding a Google Maps view this week. You can choose to either look at one view at a time or a dual view.

While a conversation could certainly be held about the different strengths and weaknesses of these different tools, most of the timeline tools that are available are going to be fairly easy for THATCampers to pick up and run with. The most complicated among them is the Simile tool, but I’ve heard there’s a fairly straightforward tutorial on building your own. Instead (or in addition to), I wonder if it could be possible to have a conversation about other possible research and pedagogical uses for timelines than those to which Jason and I have put them to use thus far. One obvious apporach would be to timeline a particular text (say, Slaughterhouse-Five) rather than a contextual time period. But what else could we do with timelines to make them valuable?

Moreover, I wonder if a discussion about visualizing time could be a part of a larger discussion about visualization that seems to be on the minds of other THATCampers (at least per their blog posts) such as Tonya Howe and Amanda Watson. How best can we use such visualizations in our research and/or teaching? At what point are there diminishing returns on such projects? Since these tools are relatively easy to learn (as opposed to programming languages), are they a good gateway tool for “traditional faculty” to begin comfortably integrating new technologies into their research/teaching? And, perhaps most broadly, what is the relationship between digital humanities and visualization

(I should meniton that while Jason and I proposed related ideas to THATCamp, this post is my own. So don’t hold him responsible for my shortcomings in expression.)

Hello, everyone! I’ve been reading over everyone’s posts and comments, and letting it all percolate – but today’s my day to finally post my own thoughts.

Here’s my original proposal:

“Digital collections of material culture – how to make them, share them, and help students actually learn something from them!

– “quick and dirty” ways for faculty to develop digital collections for the classroom, without giving up on metadata. For the recent workshop we held at Vassar, I’ve been working on demo collections (see grou.ps/digitalobjects/wiki/80338 ) to evaluate 8 different tools,  including Omeka. In each, you can view the same 8 historic costumes and their metadata, with 43 jpeg images and 1 QTVR. I’m developing my work as a template, with support documentation, for others to use.

-how students can use digital collections and contribute to them, without requiring a huge technological learning curve, especially for students with non-traditional learning styles

-the potential of union catalogs”

Of course these issues cross over in many ways with issues that have already been posted. So, I’m not sure if this needs to be a session, or if it’s more about bringing this material culture perspective to other relevant sessions. That probably depends on how many other material culture people are coming – anyone?

Deep Digital Collections / The Thing-ness of Things

Projects that successfully represent 3D objects are still pretty rare. Current systems of image representation are not sufficient – 1 image per object is not enough. Artifacts also continue to defy controlled vocabularies and metadata schema. For example, one of my current projects involves studying a historic dress inside and out – I have over 100 detail images and complex data (see a sample blog post that shows the complexity of the object).

I’m working to create digital access to the Vassar College Costume Collection, our collection of historic clothing, with about 540 objects dating from the 1820’s to today. Just to clarify, in the field of costume history, the term “costume” refers to all clothing, not theatrical costume.  For about 7 years I’ve been exploring different ways of digitizing this collection, giving students access to a database of the objects, and then sharing their research projects, in a variety of digital formats, as virtual exhibitions.

“Quick and Dirty” Classroom Tools / Low Tech Digital Humanities

In my demos, you can view the same 8 historic costumes and their metadata, with 43 jpeg images and 1 QTVR, in Omeka, CollectiveAccess, Greenstone, Luna Insight, ContentDM, VCat, Filemaker, Excel, and GoogleDocs.

My inquiry has developed beyond the initial comparison of different available tools, to explore a kind of “division of labor” in the process. My approach has been very much on the DIY side, but couched in a collaborative experience. I initially created my demos for a NITLE sponsored workshop at Vassar this past March (entitled “Digital Objects in the Classroom”). Our workshop emphasized the importance of collaboration, and we asked participating institutions to send teams of faculty, librarians, instructional technologists, and media specialists. Perhaps ironically, the demos have mostly been my own work (with wonderful help from Vassar’s Systems Administrator and Visual Resources Librarian). I continue to search for the perfect compromise – for faculty and students to be able to quickly and independently get resources both into and out of collections, while administrators feel comfortable with the security and maintenance of the technology involved.

Student Contributions

Even if you’re not working in a traditional academic setting, I encourage you to view your audience as students. We can use technology as part of a suite of pedagogical tools to provide differentiated instruction for different styles of learners.  What I imagine is a way for students to add to the conversation in ways beyond tagging and commenting – to contribute their own images and research.  Our work in the last couple of years has reinforced this in a backward kind of way. We envisioned a large grant might allow us to carefully photograph and catalog much of the collection, which we could then present to students (on a platter?). Such a grant hasn’t come through yet, but the students have kept on coming! So, each semester brings us a new project, with new research about some of the objects, new photographs that students have taken to support their research, new citations of and links to supporting references. And the database grows. And I wonder, if we did present the virtual collection to students on a platter, would they be as inspired to work with the objects doing their own research? Would it seem as fresh to them? We need to keep the focus on our students and not on technology for its own sake.

Union Catalogs / Federated Searches

For each of our collections we’re working hard to structure our metadata and to define controlled vocabularies. But most of the time we aren’t taking advantage of the sharing that structured metadata allows. Either collections aren’t having their data harvested, or if they are, they’re going into giant collections like OAIster where it can be hard to find them. We need more union catalogs for material culture objects that are oriented for specific disciplines. By harvesting for a more specific kind of union catalog, we can transcend the “dumbing down” of data for Dublin Core standards and create variations that allow for richer data in each of our fields. We don’t have to reinvent the wheel, but building on Dublin Core or VRA or CDWA can really benefit our specific fields. For collections that have a strong visual component, some form of image needs to be a part of what is harvested and shows up in the federated search.

I look forward to reading your comments – and to meeting you all in person later this month!