Archive for category Research
As I was explaining to some of my coworkers yesterday, Day of DH started with the goal of trying to make public the work—and the many different types of work—that take place under the rubric of digital humanities. We accomplish this by blogging and tweeting, just making note of what we do throughout the day.
Of course, the not-so-secret part of Day of DH is that one doesn’t get it all done in a single day. And that’s why last night found me in front of my computer, churning through email and the like. In doing that, I found an email from a collaborator with whom I’ve been writing a project proposal. We had been aiming to deliver it on the first of April, but some serious illness interposed. Since she was feeling better, she’d done the last fact check on one of our references. The proposal was ready, so I cleaned up the file and sent it on to one of the Co-Directors of Emory’s Center for Digital Scholarship. Only after I clicked ‘send’ did I realize that it would have been more appropriate to wait to send it until this morning, so I could have #DayofDH’d about it. Oh well.
I don’t think that I’m quite ready to share what we hope to do, but I’ll say that it builds on the work that Rebecca Sutton Koeser and I have been doing on the Belfast Group.
Writing this proposal was an interesting experience. A group of us started brainstorming what we could do right before the academic year started, and we followed with some monthly meetings. Given the schedules of some of our collaborators, monthly meetings were about as good as we could do. When we suddenly found ourselves in January, with not a lot of progress made, I made a suggestion that we move the proposal writing group down to a smaller number of individuals. That’s exactly what needed to happen. Following a 90-minute conversation, Lisa Chinn and I knew what direction we wanted to take. A few writing sessions later, we had a proposal ready to go. I hope that we’re able to keep it within scope.
The real lesson here—apart from timing one’s emails to big blogging events—is that while collaboration is important and often a big part of DH work, collaboration isn’t an end in itself. If collaboration isn’t working for you, then there’s nothing “DH” about sticking to its current form. Adapt and get the situation that you need in order to get your work done. Because, at the end of the day, getting your work done is about the most DH thing you could be doing.
Herewith, the second quick update post.
A New Cluster at #Alt-Academy
A few weeks ago, on 27 January 2014, I was pleased to join Katina Rogers in announcing a new phase of #Alt-Academy. The open-access collection edited by Bethany Nowviskie first went live in the summer of 2011 and included essays that sought to define “alt-ac” as a concept of labor, employment, and identity within the realm of higher education. I contributed an essay to that original collection that discussed how one went about finding and applying for alt-ac positions, as well as discussing how I personally coped with the “failure” of not being on the tenure track. Myself notwithstanding, #Alt-Academy is an important collection because it was a first attempt to make visible a type of work that many of us found rewarding and as intellectually stimulating as the tenure track. The success of the intervention was such that “alt-ac” continues to be a handy term of art, as seen by the upcoming CALS Symposium at Penn State on the subject where Bethany, Patricia Hswe, and I, among others, will have the pleasure of presenting.
In 2012, I pitched Bethany on an idea for a new cluster of content to be added to the collection. I’d found in the intervening years that the thing people inevitably wanted to know about my position was how I’d got to my job from a very traditional PhD program. Indeed, my essay in #Alt-Academy along with the others in its cluster was intended to highlight the process of “Getting There.” I proposed to Bethany that people curious about alt-ac might need still more signposts, and she agreed. After announcing a CFP in 2012, I began collecting proposals and then several essays in the beginning of 2013.
And somewhere in there is where the reality of an alt-ac job cropped up: it took me far longer to edit the essays than I had thought it would, and while I made some progress it was going to be some time before they were all ready to be published. In the fall of this last year, Katina let me know that she would be taking over general editorship at #Alt-Academy from Bethany. As Katina and I began collaborating, she proposed that I not try to get all the pieces ready to go at once but instead publish them on a rolling basis, and this is exactly what we launched.
The new cluster, “Looking for Signposts” features five essays out of the gate by Kim Yates, Andrew Asher, Daveena Tauber, Maureen McCarthy, and Katina herself. I also wrote a new introduction for the cluster. Spoliler: in it, I confess that our signposts aren’t quite what you’re looking for in the collection. Since alt-ac paths tend to be highly idiosyncratic, what we end up doing is simply bearing witness to the possibility of alternatives. As uncommon as that still is within the academy, I’m pleased to say it’s becoming more and more common.
I’m very grateful to the authors who contributed to this cluster—both those who have been published and those who are yet to come. And I’m also thankful to Bethany and Katina for the help that they’ve provided me along the way. And since we hope to be releasing new essays about every quarter, I suppose I better get back to work!
 It turns out that being in an alt-ac job is also why this post is kind of late. Between teaching my class this semester, all I could manage for the launch in January was tweeting and giving +1s to Katina’s post.
As you might have gathered from the Twitter storm that barreled out of Fairfax, Virginia, this afternoon, we released and launched the fabulous, amazing Serendip-o-matic. One of the great things about living in the 21st century is that we have a ton of materials open and available to us in digital formats that have been collected in sources like the Digital Public Library of America, Europeana, and Flickr Commons. But since things are digital we don’t find them like we used to. Search makes it possible to pinpoint the exact thing that we’re after, as Shawn Graham nicely points out. Such precision is a bit problematic, however, as it leads us to miss the surprise of finding that unexpected book in the stacks or that item in the archives. Serendip-o-matic is designed to recreate that discovery process. After all, there’s so much stuff out there, if you only get exactly what you’re looking for then you’re missing out on some of the best stuff! Search is great, but this isn’t search: it’s Serendip-o-matic.
That’s the pitch, at least, and at this point in the day I think I’m finally starting to get it where I want it to be. Hopefully people are excited to learn more about it in the coming days. We did write the Today Show, so I think we can plan to be coming to your living room by Tuesday.
So what was it like on the ground? Crazy, more or less. I think everyone was on the move by 8am, with some of the design / dev team logging commits by that point. I started my day meeting with the Outreach team, working on their schedule for the day and talking about the press release. This may have involved arguing about parentheses and angle brackets.
Once we got over to CHNM, I spent most of the day dodging back and forth between rooms. I helped Outreach workshop some of the final language for the press release, once again focusing on the story we wanted to tell. I dodged over to help file issues on the design / dev team for the dev server of Serendip-o-matic. I bug checked responsive design on mobile, tablet, and web versions, as well as catching other pieces of human-readable content. I put my head down for 20 minutes once I got a request from the Chronicle of Higher Education for an interview request. (Thank goodness for my MLA media training which taught me this technique.) After the interview, it was on to drafting the press release email and identifying a few names from our media contact list to get an early warning email. Then it was dashing around again.
As we got closer and closer to what Mia had determined would be the “code chill” leading up to the “code freeze” at 2pm in expectation of the 3pm launch, we planned for the live launch broadcast while contending with continued difficulties in the Zotero integration and mass, multiple edits of text, CSS and design, and code at every level of the process. At one point, I found myself standing in the room where all the dev/design team was working and all I could think of was to run to get people food or make sure they were plugged into power. In the end, I think I took a picture.
In the end, we only got to a code freeze and final deploy around 2:55pm. Everyone erupted into cheers and applause, and we tweeted our teaser image. Our fearless leader Tom poured drinks.
But then it was a quick dash to the computers for the live launch. Jack had done a great job not only of setting up the technology for the 4-way Google Hangout, but also scripted everything. We had written questions and practiced a bit of what we were going to say, but what I was most nervous about was my live demo of the site. If I had been thinking more clearly when I was doing it, I might not have showed off the Zotero integration. Halfway through to clicking the “Go” button, I suddenly wondered if it would crash. That would have been terrible during a live demo. But fortunately Eli’s fixes held, and everything went perfect. We were genuinely surprised when Dan Cohen was able to join us and very much appreciated both his involvement and that of Brett Bobley and Jen Serventi from the NEH’s Office of Digital Humanities. Even better, we were able to highlight the many different types of work that the members of the team did. If for some reason you missed the video broadcast, and want to relive the heady excitement of it all, well, we pressed the “record” button ahead of time.
After we clicked “end” on the video, there was even more cheering and shouts of acclaim. Someone might have done some streaking. Everyone more or less collapsed into a cluster and started watching comments roll in via social media.
I can’t tell you how gratifying it is to have made something and immediately be able to present it to them to look at and play with. We heard from bloggers who were using it find images and users who were finding new sources for their work. Most of all, the general enthusiasm of the digital humanities community and the rings of Internet that surround them were appreciated. Thanks, all of you, so much for being willing to play a part by paying attention to what we’ve been doing this week.
Amazingly enough, the design / dev team almost immediately got back to work resolving some of the issues we still had outstanding for the code base. (The repo is open and public now. Go ahead and fork away!) We probably hung out in this pattern for an hour or 90 minutes, just soaking in the accomplishment. I think we were all reluctant to break out of the magic circle of the moment because we knew that it would mean that the experience was beginning to end. We had done what we set out to do, but it also means that we’re saying goodbye to each other in less than 18 hours. Some people will even be gone before I wake up.
It’s strange to think that I won’t be seeing these people next week. That we won’t be building Serendip-o-matic any more. Sure, we’ve got a long way to go on improving it, and we have plans for how to expand on the One Week | One Tool experience, but… Well, let’s just say I’m already looking forward to seeing everyone again at THATCamp next year for the #owot reunion.
What lessons do I have to extract from today? First, when you’re going to be doing something in front of other people, you really do need to practice. I didn’t give as good an interview on the phone as I would have liked simply because I didn’t get a chance to talk it through with someone. But I was so much further ahead by having written down my talking points. The second point is related and spins off the work of the fabulous outreach team: when you want people to pay attention, it helps to keep telling a story. It was the week’s worth of tweets and blog posts that gave enough information about what was happening that led to people being willing to spend some time with us on a Friday afternoon. Third and last of all, design matters. There is no way around it.
I’ve got at least two more OWOT posts coming, I think. So at least for you and me, dear reader, it’s not over yet.
I’m ecstatic to announce that the One Week | One Tool team has just launched Serendip-o-matic.
Go and play. More soon. And remember, it’s not search; it’s serendipity!
All right. You know the drill. Let me just say that today’s been a long day. We’re so close that I think we’re all super excited, but we know there’s still quite a bit of work to get done. Which explains why it’s not just me who’s awake at this point.
As I start blogging, Mia, Rebecca, and Scott “West” are wrangling some badly merged commits on the GitHub server and I’m seeing messages roll in via Growl. I’ve just finished looking through the list of issues we have outstanding in the repo, on Mia’s request to see if everything lined up with Meghan and my perception of prioritization. About an hour ago, we were looking at some final glyph designs that Amy had cooked up for our onboarding experience. And before that, Ray and I were hitting the email contact list spreadsheets to make sure we have everyone lined up for our press release tomorrow.
You wouldn’t believe how difficult some schools have decided to make this. Before that, Jack (who travels with his own projector?!), Meghan, and I were putting the finishing touches on the plans for the Outreach team tomorrow, including the live broadcast of the tool announcement. It’d be pretty convenient if I could tell you when that would happen…but I don’t know anything about that. Prior to that, people were passing out high fives to Eli for cracking a really knotty OAuth issue which he had been hammering away on for much of the last two days. Not to mention congratulating him for being able to eat a burger roughly the size of his head.
Before that, well, we were looking at some of the other designs that Amy had. That gets us back to about 8pm this evening. Of course, we all started the day around 9am.
So what did we do the rest of the time? Well, I’ll be honest to say that it’s getting hazy at this point. We really started with a consideration of the logo and site design that Amy came up with the night before. (This is such the wrong way to tell this in a grok-able manner, but I’m at the point, I think, where I’m writing how it feels, man, rather than anything else. Consider this an ethnography.) Mass applause and enthusiasm ensued after which point we had some discussions about the larger information architecture for part of the tool. We were pleased to be joined by Jennifer Serventi, our intrepid and amazing program officer from the NEH. Jen carried on the NEH tradition of bringing love in the form of carbs and calories.
But she also stuck around for about five hours, listening and generally taking in the vibe of what was happening. She took the time to meet individually with a number of different team members, the PIs, and each of us project managers. I often think that I have what it takes to be a program officer; and then I run into one of them and am blown away by their ability to listen.
These are the friendliest and most empathetic people that I think I’ve met in my entire professional career. I appreciated the fact that Jen wanted to hear not only about what I thought about the OWOT event so far but also what I thought it would allow me to take back to Emory. And it was great to have her sitting in with Jack and I as we worked on micro-copy for the website, struggling with the word counts and tone to make sure we hit the message as best we could.
Two other moments from the day are worth mentioning. First, on Tuesday Tom had told Meghan and I that we needed to be thinking about future vision for the project, about ways that it could live on beyond this particular week. I’ll be sharing our ideas in a coming blog post so as to avoid spoilers. But suffice it to say that after several days of feeling like we wouldn’t be able to deliver on this particular assignment, we’ve got the seed of something that all three of us are excited about. Happiness.
The second moment isn’t quite so happy but instead represents a learning moment for me as a project manager. After seeing the presentation on the website first thing in the morning, the Outreach team decided to get working on the micro-copy for the home page. In the mid-afternoon, when we brought them back together with the Dev and Design team, we discovered that the latter had iterated a few more times on the home page design in such a way that the work that eliminated the need for that text. What could have been a very testy situation was handled with grace by everyone that was involved, but it really came back on the project managers not communicating clearly with all of the teams. It’s an easy thing to do when we’re all running around trying to get something off the ground while not yet having a server or a logo and “ZOMG! what happened to our wifi connectivity?!” So I’m glad to catch the lumps for this one.
So. Lessons learned? First, visions aren’t just something that happen in the Old Testament. But like we see in scripture, they sometimes require waiting for. Such idling in the wilderness is okay—and should probably be expected. And if you happen to be a bit like Jonah and would rather be free of such visions, well, you might be in the wrong business. Second, well, don’t drop the ball. You’d have thought I learned this back in little league, but it turns out that I was a terrible right fielder. I probably should have copped to this in my OWOT application.
Finally—and not for the final time, I am sure—let me say publicly how thrilled I am to be working in an environment with such great and strong individuals. Everyone is pulling their weight and looking for places where they can help someone else at the same time.
It really does feel more like a barn raising that I would have thought possible. And at the end of the day, what we’re building is not so much a tool as a posse. I’ve got their back, and they’ve got mine. Watch out, #owot rolls deep. Especially, y’know, around 3-5pm EDT tomorrow.
EDIT: Don’t miss Jack’s post on day 3. And day 4 posts by Amrys and Mia, both of whom also talk about camraderie. I especially love what Mia writes in her post about creation of “rapid trust” alongside rapid prototyping. Glad to discover I’m not the only one feeling the love.