I’ve been home from the digital humanities institute for about a week and a half now. I spent part of that time just adjusting back to civilian life, including doing all the laundry I brought back from Fairfax, getting used to cooking for four again, filing papers, and pulling weeds (literally and figuratively). But I’ve also been trying to wrap my brain around the two biggest events of the summer–the DH institute in July and the trip to Turkey in June–in a way that will help integrate those experiences into the places they belong (and that in itself is a question), while also reflecting on them in a way that hopefully embeds them into my lifelong experience. Although I covet the regularity of the research/writing rut that I anticipate will be the general character of this sabbatical, I don’t want to lose, and forget, what has happened during this amazing summer.
I started in a very practical way, using my newly-won DH skills, such as they are, to organize my Turkish experiences and materials for a future presentation at the Niagara Foundation (organizer of that tour) and also for my future classes. I’ve got a joint StoryMap/ThingLink project underway for the Ottoman patrons, but that is taking more time and brain cells than I have had to devote to the project (so, more on that later). An easier task was to use the Google Maps Engine to work up a map of my first course in architectural history. ARC 231 covers the ancient and medieval periods, and I began with the simple idea of putting together a map that showed the location of sites that the course includes, in part to show the extent to which Turkey was included in the class by means of comparison with the adjustments after the Turkey trip. Although it wasn’t the quickest thing to draw up the Excel sheet that listed all the buildings with their metadata (a word I wouldn’t have used a month ago, BTW), once the spreadsheet was “tidy” the map pretty much made itself. Because of the limitations of the free version of Google Maps Engine, I had to break the class in half; the point “0” that separates BCE and CE/AD timeframes seemed a reasonable place. Then, each map is further divided into three layers that show successive chunks of time. By clicking in the menu that appears in the map, you can turn on/off the successive layers; zooming in and clicking on a pin will access the site’s data and access to a few pictures of each building or site.
If the Google system was a little more flexible (which maybe it is if you’re willing to pony up for the not-free version), and the pictures were a bit bigger, this would be a killer study tool for my students. As is, it is still pretty great in simply locating the buildings and gathering basic info on them. But more importantly, the map project accomplishes several goals that are at the heart of DH work: the map makes it much easier to literally see the big sweep of settlement patterns, understand adjacencies and, with a little more work, knit it all together through trade routes and other information networks.
Yet at the same time the maps, like all visualization techniques, have a truthiness problem. In the institute we read from a great little book, How to Lie with Maps. One might see my maps giving a false impression about Where People Built Stuff–whole continents appear barren, which is, of course, not the case. Even zooming in to well-pinned countries or regions show that there are very few things that appear to be worthy of note. But therein lies the not-lie of these maps, because they are telling the very important truth of history’s long biases in favor of and against different cultures. And that, perhaps, is where I see these maps having truly transformative effect in my classes. Sure it will be handy for students to click around and find tidy dates for all the most famous things in Rome or wherever, but when we start the semester by looking at these maps and asking what they show, and what they don’t show, and WHY: well then. I might just trick those sophomores into thinking like historians if they’re not careful.
Note: the map above is linked to the Google Map for the second half of ARC 231 (ancient/medieval architecture after the year 1 AD). Click on it to go to the map, have a look around, and please let me know what you think!