Visual data

Diagnostic tools – or – the pretty visualization is not the end

Anelise Hanson Shrout

As the semester and my first graduate digital history class wind down, I’ve been thinking a lot about building DH things for investigation vs. argument.  There’s a lot of good work on tools-as-theory, and whether a digital thing can be a satisfying argument, and an upcoming conference on argumentation in the digital humanities – so I’m not the only one.

I also just finished writing 1-2 pages – maybe 1,000 words – based on a diagnostic tool that it took me over a month to build.  I’m hoping to spin what it tells me out into a longer article in future, but for now I thought I’d share it here, with some commentary on how I made it, what it told me, and why it is not an effective argument.

One of my book chapters is on a group of enslaved and free people in Richmond who raised funds for victims of famine in Ireland.  The First African Baptist Church of Richmond raised just under $35 in 1847. While the amount per congregant was low (the church listed thousands of active members, but many of them were not able to regularly attend because of their enslavement) the donation itself was relatively unique in the church’s history.  This was one of the first times that this congregation raised funds for people not connected with the church.  I have a much longer argument on the political work that this donation did, but I wanted to be able to make some concrete statements about congregants’ experiences in the 1840s.

This was helped by the church minute books, which recorded the names of baptized, excluded and restored members (there were a lot of exclusions for adultery in the 1840s) as well as the names of the men and women who owned the congregants who were enslaved.  So I built a network (using Gephi, which benefits tremendously from the recent update) that showed only relationships characterized by slavery, to see if any white Richmonders were particularly over-represented. (made with sigma.js and the Gephi plugin created by OII)

While some men and women owned more than one congregant, by and large this network was fairly diffuse.  Congregants obviously shared the religious and physical space of the church, but their relationships outside of the church did not seem to be conditioned by their enslavement by particular men and women. (There is an excellent and robust literature on enslaved people in urban spaces, resistance and community building, which I won’t recap here – but suffice it to say that scholars have charted many other ways of relating beyond ownership by the same person, and I assume those modes were at play in 1840s Richmond).

As I put together the database of congregants, I realized that many and unusual names (Chamberlayne, Poindexter, Frayzer, Polland, among others) recurred among both slaveholding and enslaved people.  So I made another network, this one assuming that people who shared a surname had some kind of relationship (this is not a 100% defensible assumption – some of the more common names might have been happenstance).  With those kinds of connections, the network (which includes all of the same people as above) becomes much more dense, with clusters that signify relationships based both in slavery and (most often coerced) sex.

It’s interactive!  It’s dynamic!  It’s a network!

It is not an argument.

At best, this is a tool that lets me locate an individual and see connections.  It relies on two kinds of relationships (and likely overstates the certainly of genetic relationships or previous ownership based on shared surnames).  It helped me to write two pages about the density of connections among black and white Richmonders, and bolster claims about the broader relationships that the First African Baptist Church was embedded in.  It remains an investigative tool.

I think it could be helpful, which is why I am putting it on the internet, but it does not constitute argument.  It does not even constitute analysis (that happened behind the scenes in R).  It did take – from the start of transcription to now – over a month to build.

Was it worth it?  Well, I was able to see connections among the 800+ congregants mentioned in the minute books from 1845-1847 that I would not have been able to see just by reading the names.  I was able to place individuals in a broader social context.  I wrote two pages.  I think that work like this can be tremendously generative, but either happens behind the scenes and only lives on a researcher’s computer, or is presented as the end of an investigative process. This is firmly in the middle of the investigation, but I suppose that has value too.

Quick note: Timeline of famine philanthropy

Anelise Hanson Shrout

I’m sitting down to tackle my introduction, and wanted to say something specific about the timeline for famine philanthropy. Tableau helped to track the total number of donors by organization.  This is a better measure than the total amount of donations – at least until I go back and standardize British pounds and U.S. dollars, but it gives a good sense of time timeline of relief.

 

Teaching theory in history (part two of some) – or – In Theory podcast meets Typhoid Mary

Anelise Hanson Shrout

Big theoretical concepts can help us to see the world in new ways.  Big theoretical concepts can help us  see historical events in new ways.  This is especially important for methods classes like the one I am teaching now, since these courses seek to bridge the gap between history as a set of stories that someone else tells, and history as a practice that students themselves can engage in.  We want students to leave these classes loving history as much as when they came in, but we also want to destabilize the idea that there is one, “objective,” “true” narrative to be told about each historical event.  We want them to think about how to select evidence, put that evidence in conversation with other scholars, and offer an interpretative framework for that evidence that nets something beyond arguing that a thing happened in a place and at a time.  Theory helps with that framework.

Undergrad-me would not have believed that current-me would someday be singing the praises of theory.  Luckily, a compatriot of undergrad-me was more prescient than I – Maria Cecire and Noorain Khan are responsible for the In Theory Podcast, which seeks to “raid academia for the the most fascinating and relevant social, cultural, and scientific theories, and use them to help make sense of this beautiful mess of a world we live in.”  It is excellent.  You should listen to it.

I’ve especially enjoyed using In Theory in the classroom.  I’ve generally found teaching theory in history to be one of the more challenging parts of undergraduate pedagogy.  This isn’t because students are incapable of understanding, or even enjoying, theory.  However, I do think that it is difficult to understand the value of theory in the abstract (at least, this was true of me in my theory-adverse undergraduate days).  This course features several weeks on classic theory for history, but this semester I found that pairing the In Theory podcast with a classic in historical scholarship – Judith Walzer Leavitt’s Typhoid Mary – helped to illustrate the ways in which theory can be useful generally, and useful in historical scholarship in particular.

How it worked:

First: I assigned pairs of students different episodes of In Theory.  As they listened, they were asked to identify (1) the theories engaged with in the episode (2) how the podcasters apply those theories to everyday life and (3) other things to which they might apply that theory.

Second: In class, the groups diagrammed their notes on the board, focusing on one particular theoretical concept from the assigned episodes.

Third: Each group presented on their theory of choice, and then each student went around the room and commented on how they might use one of the theoretical concepts outlined in class to further their own research.

Fourth: For the next class, students were assigned chapters from Judith Walzer Leavitt’s Typhoid Mary.   Each chapter takes a different perspective on Mary Mallon (the first silent carrier of typhoid fever, colloquially named “Typhoid Mary,” and imprisoned by the state of New York until her death).

Fifth: Armed with their knowledge of how different theories help us to understand different aspects of the world we live in, students dove into Typhoid Mary and undertook the same kind of diagramming they had done for the In Theory podcast.

Sixth: Each student once again commented on how they might use the theoretical concepts used in Typhoid Mary to further their own research.

By the end of this two class arc, students had two different examples of the application of theory in concrete ways.  Next time I teach this class I am going to have a more defined section on theory, and probably build in an additional class and assignment that recapitulates the different theories the students have been exposed to.  Nevertheless, I think the concrete application of theory evinced in the In Theory podcast and in Typhoid Mary really helped to clarify theory for students.

Teaching theory in history (part one of some)

Anelise Hanson Shrout

I’ve recently had conversations with several colleagues about teaching theory in history.  As a discipline, we’re not as obviously theory heavy as some of our compatriots in the social sciences, and much of the theory we use is grounded, or embedded in assumptions we make about sources, voices and narrative.  Given the importance, but relative invisibility of theory in history writing (and given that students – especially new majors in historical methods classes – are likely to be a little allergic to heavily theorized writing anyway) I’ve been trying to figure out how to teach students how to identify and make us of theoretical frameworks for history.

This question has been bugging me for the past year or so.  It first became apparent in a class on the intertwined histories of gender and technology, and I also see it in my current undergrad historical methods and Atlantic history classes.  This is not, I think, merely a consequence of mulling more on theory than I used to.  By design, none of these courses clear narrative path.  Gender and Technology took on several themes during the semester, often circling back to the same time, but a very different place or perception.  Atlantic history is arranged roughly chronologically, but approaches the Atlantic from a series of different spaces, and via different peoples, so we are often jumping in space and time.  Historical methods is loosely organized around the theme of American disasters, but we also skip around temporally, and often head down methodological or historiographical culs-de-sac before returning to the topical meat of the course. This shred lack of a singular storyline meant that theory was all the more important – it was the thing that could get the courses to hang together.

I wanted an assignment that allowed students to make connections from class to class, which emphasized theoretical framings, demonstrated the value of theories as organizing frameworks, and which wouldn’t rely on me lecturing at students.*

I’ve come up with something that I call “theory exercise.”  Each class uses a different variation on the same theme:

First: students review their notes and memories and write down one or two important framing concepts from the previous class.  Earlier in the semester these can be a bit vague, but I make sure that we identify important ideas in reading discussion, so that they can (hopefully) just go back to notes.

Second: some students come up to the board and write one important framing concept.  The only rules are (1) no duplicates and (2) you can amend what someone else writes

Third: the remaining students come up to the board and write down one topic from earlier in the semester, or from the reading for that day’s class that connects with those big ideas.  The same rules apply as in the second phase.

The final product
The final product

As a result of all of this whiteboard writing, we have a map of the main points of the previous class, and a visual representation of connections throughout the course.

This works with individual students working on their own, pairs of students, or even groups that have to consult and come up with one big idea or one connection.  I’ve been experimenting recently with randomly assigning students to big idea or connection and with allowing it to be more of a free for all.

I’ve learned a few things:

  • In classes where I’ve been using this exercise since the beginning of the semester, weekly reading responses do a much better job making links between a given reading and themes from earlier in the semester.  In making those links, students also invoke theoretical frameworks.  Some of these are more explicit than others, but the very act of linking disparate examples requires a theoretical underpinning.
  • In classes that don’t have a clear narrative (and this is probably true of most upper level classes) this exercise also helps students to make their own meaning out of the material covered, and to remember material from earlier in the semester.
  • On exams that ask students to identify and demonstrate the utility of theoretical frameworks, the classes that have been doing this kind of work do better than the classes that haven’t.
  • Having this material written on the board is a great way to mark the start of class with activity, rather than my recap; it also models note-taking strategies for students who aren’t familiar with documenting their participation in discussion based classes.

*I developed this assignment after many talks with Caroline Weist, pedagogue extraordinaire.

d3.js + R > Gephi (or, why network analysis helps with history)

Anelise Hanson Shrout

Gephi is a very useful tool.  I’m very much looking forward to the new release that seems always on the horizon.  In the meantime, though, every time I open Gephi it crashes, and then I dive down a long rabbit hole of trying to re-write the program code, and then I get angry and go home.  So I’ve been delighted to find that a combination of R (for manipulating and analyzing the data) and d3.js (for visualizing the data) does most of the work of Gephi with much less frustration.

I’ve been using Kieran Healy’s work on Paul Revere and network centrality and applying it to a cohort of men who served on the boards of philanthropic organizations in New York in the 1840s. I am particularly in the officers General Relief Committee for the Relief of Irish Distress of the City of New York. These men – Myndert Van Schiack, John Jay, Jacob Harvey, George Griffin, Theodore Sedgewick, Robert B. Minturn, George Barclay, Alfred Pell, James Reyburn, William Redmond and George McBride Jr. – were deeply politically connected, but don’t seem to have had much of a relationship to one another.

Healy’s script, and Mike Bostock’s d3 blocks helped me to build a matrix which tracked relationships between philanthropists via organizations, making note of the number of organizational connections that different pairs of men shared; and another matrix which tracked relationships between philanthropic organizations and social clubs via philanthropists, making note of the number of men that each organization shared.  I used the former to build a force-directed network diagram, which, in combination with some R based analysis, suggests that while the New York Famine Relief Committee officers didn’t often serve on other committees together, they shared other social connections.

For example Jonathan Goodhue was not a member of the famine relief committee, but served on other committees with nearly every General Relief Committee officer.  Of the New York famine relief committee members, Jacob Harvey was the most centrally connected member.  This data has pointed me in some new archival directions, but also give a much better sense of the ways in which people were connected to one another than comparable textual descriptions might do.

 

 

I also built a network diagram showing relationships among different newspapers reporting on the famine, which cluster newspapers more inclined to cite each other.

 

Nodes!

Anelise Hanson Shrout

I’m taking a look again at the citation networks that famine newspapers were embedded in.  In the past four years, dynamic network visualization has become much easier, leading to things like this, thanks to Google Fusion Tables:

Previously, the closest I could get was a visualization that this (this one is based on co-occuring words in the bibliography of the diss):

Shrout references

Times, changing.

Imaginotrasnference technology -or- books as technology

Anelise Hanson Shrout

I’m teaching a class on early American communication technology/introduction to digital history next (almost this!) semester.  For one of the early classes, I wanted to drive home how books (and pens and paper and presses etc.) fit into a history of technology.  While there are some great theoretical articles on book-as-tech, I ended up going with an extended quotation from Jasper Fforde’s The Well of Lost Plots, on the genealogy of books – and then I made an infographic:

Book technology infographic-01

“First there was OralTrad, upgraded ten thousand years later by the rhyming (for easier recall) OralTradPlus. For thousands of years this was the only Story Operating System and it is still in use today. The system branched in two about twenty thousand years ago; on one side with CaveDaub Pro (forerunner of Paint Plus V2.3, GrecianUrn VI.2, Sculpt- Marble VI.4 and the latest, all-encompassing Super Artistic Expression-5). The other strand, the Picto-Phonetic Storytelling Systems, started with ClayTablet V2.1 and went through several competing systems (Wax-Tablet, Papyrus, VellumPlus) before merging into the award-winning SCROLL, which was upgraded eight times to V3.5 before being swept aside by the all new and clearly superior BOOK VI. Stable, easy to store and transport, compact and with a workable index, BOOK has led the way for nearly eighteen hundred years.

When we first came up with the ‘page’ concept in BOOK VI, we thought we’d reached the zenith of story containment — compact, easy to read, and by using integrated PageNumberTM and SpineTitleTM technologies, we had a system of indexing far superior to anything SCROLL could offer. Over the years . . . . we have been refining the BOOK system. Illustrations were the first upgrade at 1.1, standardized spelling at V3.1 and vowel and irregular verb stability in V4.2. Today we use BOOK V8.3, one of the most stable and complex imaginotransference technologies ever devised — the smooth transfer of the written word into the reader’s imagination has never been faster.”

 

 

Fire! July 19th, 1845 – The Financial District

Anelise Hanson Shrout

On July 19th, 1845, New York City caught fire.  It started in a whale oil warehouse in lower Manhattan and spread quickly, eventually engulfing warehouses full of explosives.  The fire burned for over eight hours, and when it was finally put out, 30 people had died.

The fire was commemorated in popular prints in the 1880s, two of which currently held by the New York Public Library:

View of the terrific explosion at the Great Fire in New York. From Broad St. July 19th, 1845.

 

The Fire Of July 19, 1845 — The View At Bowling Green.

I came across the fire while trying to figure out the names of public health institutions in 1847 New York.  The NYC guide I’m using – Doggett’s New York City Directory – for 1845-46 contains a list of the 217 buildings destroyed by the fire, and the names of the hundreds of people who were displaced by it.

I thought it might be fun to map the extent of this fire, described in Doggett’s as:

“The disastrous fire of the 19th of July, 1845 – long to be remembered by the citizens of New-York – having laid waste a considerable portion of the business section of the city; and causing, consequently, the removal of numerous business men and firms.”

Ever systematic, the guide went on:

“The total loss by the late fire has been variously estimated at from $5,000,000 to $8,000,000.  The fire commenced about 3 o’clock, A.M. and was not subdued till 11 o’clock A.M., a period of eight hours.  Supposing, therefore, the total loss to have been $6,000,000 – the average loss per hour, was $750,000; the loss, per quarter of an hour, was $187,500; the loss, per minute, was $3,125, and the average loss per second, was $52.08 1/2!  Bank notes, of the denomination of one dollar, would not burn more rapidly in a common fireplace than was the property consumed by this conflagration.”

I have no sense of the relative value of the area destroyed today, but it encompasses much of the financial district of present-day New York City.

 

These are a few of my favorite maps

shrouta

I’m putting together an aspirational syllabus for a digital humanities/mapping course, and have been thinking about my favorite maps, and why they work so well.  Here is a very-not-complete list of my current greatest hits:

Slave Revolt in Jamaica, 1760-1761: a cartographic narrative.

This is, by far, my favorite digital mapping project.  I’ve seen Vincent Brown speak on it, and I was quite impressed by his articulation of why we need a map like this to understand enslaved rebellion.  Because records of these uprisings tend to have been produced by ruling elites who were actively opposed to representing enslaved resistance as anything other than barbarous and futile, it would be easy to think that this uprising – and many others like it – were haphazard and poorly planned.  Brown’s map, on the other hand, reads the colonial archives against the grain to show us the strategy that underlay this revolt.  I love that he uses sources in which obscuring enslaved agency is a feature rather than a bug to highlight that agency.

Touring the Fire

A little less high tech, but still a great example of how a geospatial perspective can give us new, or at least different information about an historical event.  One of the persistent fictions about the Chicago fire is the culpability of Mrs. O’Leary’s cow, so it’s interesting to see how the fire spread, but also to treat the path of the fire like a walking tour, and to map it onto Chicago’s geography today.

London Soundmap

This is just ridiculously cool (and reminds me of a book I just finished about London’s underground rivers).  It borrows aesthetically from the iconic tube maps, but instead of information about subways gives us the sound of underground waterways.  There are some other great soundmaps on this site, including ambient London noise, the sound of the Thames estuary, and a handy map of the most common sounds in different parts of the city.  The whole thing is worth exploring.

While we’re talking about aural mapping…

Here’s a project which uses immigration data to create a true aural map of changes in American demography over time.

And finally, everything NOAA does, but especially their geospatial services.

Now it’s all about convincing the undergraduates that maps are cool…