Day of DH marked the first really glorious spring day in the Northeastern US—a nice omen! At noon I took my lunch outside and had an enjoyable conversation with my colleague, Elli Mylonas. The TEI Council is meeting in Providence at the end of this week, so she was in the process of planning the details of that visit (including the menu for dinner), and she also filled me in on the recent Hackfest held in the new Digital Scholarship Lab at the Brown University library, which by all accounts was fun and a success. If I had had a camera with me, this would have been the picture to take for the blog: brilliant sunlight, the vaguely menacing bulk of the Sciences library looming over us, a grove of trees in bud nearby, the severe geometry of cement paving stones under our feet. Metaphors everywhere you look!
One of the high points of my day was a 2-minute conversation that interrupted me as I was doing something less pleasant. One of the encoders for our Cultures of Reception project walked into my office.
Josette: Is “the Western world” a place name?
Julia: [interested but decided] No—it isn’t. It doesn’t really designate a place…It’s more like a loose aggregation of places, a concept… Sort of like “the developed world” or “Christendom”…too perspectival.
Josette: How about “the West”?
Julia [even more decided] No, definitely not… Although I guess there might be cases where a specific writer used a phrase like “the West Country” in a way that clearly referred to a few specific counties…
Josette: [a little disappointed but accepting the result] OK. [turns to go]
Julia: [explaining, getting into the spirit of it] See, actually there are two things going on here. There’s project management—your role (and it’s a good one) here is to raise these really interesting questions, and my role unfortunately is to be the hard-ass, to foreclose them, to make a decision one way or another [Josette is grinning because this is so clearly true; Julia tries to clarify]—to be clear so that we can be consistent. But there’s also something else: if we think about the goals of the project here…
[Josette grins more broadly because she sees what is coming]
Julia: …the goals of the project have to do with representing the cultural geography of transatlantic reviewing…[she trails off as the trap is sprung] Oh $%&#. [clutches brow]. OK, let me start over and rethink this. Yes, actually, we do need to mark those references somehow, they are absolutely crucial, they are central to what we are doing here. They aren’t names, but they are references to places…OK, here’s how we should do this…
The first event on my Day of DH (which so distracted me that I completely forgot it was Day of DH until lunchtime) was payroll. Brown University recently switched to a new payroll system that is based entirely on Flash and has interfaces of labyrinthine complexity. As far as I can tell, no one understands it—we all navigate by reproducing whatever odd pathway happened to lead us to the thing we need. If we could see a site map, with our actual routes plotted on it, I am sure they would be comically convoluted: like going all the way around the block to get to the house next door (which happens to be hidden by a tall hedge). Communicating with other people—for instance, working with an administrative colleague to discover whether my students have submitted any hours for the last pay period—involves a ritual of establishing that we are in fact looking at the same thing: “So, click on where it says your name and that funny number… OK, now click on your organization and then to go Tasks… no, not that one, the one in the lower left…”
This would just be a funny (not funny ha-ha) story about how bad a bad interface can be, except that I shared my woes with someone at another institution who said “So you hate [payroll system]? Everyone loves [payroll system]!!” This took me by surprise and made me think: How is it possible for someone to love a system like this, which makes it impossible to understand how it works, or to get any systematic access to the underlying data, or to accomplish any task efficiently? That question has shifted in my mind: What is different about the people who love a system like this? What is the audience for this kind of system? What are they responding to? I can’t just write them off as lunatics unless I’m willing to have them do the same.
A bit more dispassionately, the distinctive properties of this system seem to be:
- it is very “designed”: the layouts are not bound to a database-like grid, but arrange the visual items in more creative ways.
- it does not expose its structure in its navigation; the navigation is more like teleporting (“go here! by magic! through a wall! don’t worry how we got here!”).
- it does not seek to make repetitive tasks ergonomically economical (e.g. by providing a way to do them all at once, or providing a way to do all the steps of a task on one screen); it places a higher value on simplicity of presentation for any specific sub-task than it does on efficiency or economy of motion.
- by making a lot of its navigation rely on bookmarking and “favorites”, it encourages people to script their most common tasks, creating their own shortcuts and memorable paths through what would otherwise be a very complex navigational environment.
So I can understand that this would appeal to—or even create—users who don’t seek to engage with it as experts on the information it contains, but who rather have a set of tasks that need to be accomplished at intervals. It’s pleasant to look at (which I find obscurely irritating) and very, very hard on the wrists. And it reminds one of the value of serendipity, since that’s how I seem to find my way around…
I feel sure there are some useful lessons to be learned here from a DH perspective!
I’ve been welcomed to Day of DH 2013, and this is my first post. I’m very excited to be participating again this year. Last year, I spent most of the day flying to Australia, which included crossing the international date line and getting a bonus helping of DoDH. This year will be more pedestrian; my plans include:
- working on a grant proposal for the TAPAS project
- working on subscription renewals for Women Writers Online
- working on the curricula for several upcoming workshops, including Text Encoding Fundamentals at DHSI, the WWP’s next TEI customization workshop, and also the first Digital Humanities Data Curation institute at the University of Illinois.