Sessions

Technical details

Once you are registered, you should receive login information for the site. To propose a session, log in and go to Posts -> Add New. Write your session proposal as a blog post and publish it to the blog. (It’s helpful if you categorize it as “Session Proposal” using the Categories box at the top right of the Add New Post page.) In the first time slot on Friday morning, 5/17, we will all go over the proposals together and create an agenda for the day from them. We encourage all participants to propose a session.

Content details

Some session genres and examples are given below. The best tip: do not prepare a paper or presentation. Plan instead to have a conversation, to get some work done, or to have fun. An unconference, in Tom Scheinfeldt’s words, is fun, productive, and collegial, and at THATCamp, therefore, “[W]e’re not here to listen and be listened to. We’re here to work, to participate actively […] We’re here to get stuff done.”

Note that while there may be some smidgen of presenting going on in hands-on skills training workshops, you can also propose to teach a workshop at the last minute. As long as you know something and others don’t, it will likely be productive for all concerned, even if you haven’t prepared much. And, if it isn’t, we encourage participants to invoke the law of two feet to find a more productive session.

Session proposers are session facilitators

If you propose a session, you should be prepared to run it. If you propose a hacking session, you should have the germ of a project to work on. If you propose a workshop, you should be prepared to teach it. If you propose a discussion of something, you should be prepared to summarize what that something is, begin the discussion, keep it going, and end it. But don’t worry – with the possible exception of workshops you have offered to teach, THATCamp sessions don’t really need to be prepared for; in fact, we infinitely prefer that you don’t prepare.

At most, you should come up with one or two questions, problems, or goals, and you should be prepared to spend the session working on and working out those one or two points informally with a group of people who are not there to judge your performance. As long as you take responsibility for running the session, that’s usually all that’s needed.  This is the Open Space Technology approach to organizing meetings.

Session genres

1. General discussion – Sometimes people just want to get together and talk informally, with no agenda, about something they’re all interested in. Propose a session on a topic that interests you, and if other people are interested, they’ll show up to talk about it with you.

• Jon Voss, Toward Linked Data in the Humanities, Great Lakes THATCamp 2010.
• Nick Mirzoeff, An actual digital revolution?, THATCamp Prime 2009
• Jeffrey McClurken, Archiving Social Media Conversations of Significant Events, THATCamp Prime 2009 (this session was combined with Nick Mirzoeff’s, above)
• Eli Pousson, How do we share our knowledge of historic places?, THATCamp Columbus 2010
• Frédéric Clavert and Véronique Ginouvès, Les archives orales et le web (Oral testimonies and the web), THATCamp Paris 2010
• Zach Whalen, ARGS, Archives, and Digital Scholarship, THATCamp 2010

2. Hacking Session – Several coders gather in a room to work on a particular project. These should usually take more than an hour or even two; if you propose such a session, you might want to ask that space be dedicated to it for the entire day.

• David Uspal, Hackfest: HTML5, THATCamp Philly 2011
• Wayne Graham, Mostly Hack Zotero hacking session, THATCamp Prime 2010
• Stéfan Sinclair, One Day, One Toolet, Great Lakes THATCamp 2010
• Ben Brumfield, Hackfest, THATCamp Austin 2009

3. Writing session – A group of people get together to start writing something. Writing can be collaborative or parallel: everyone can work together (probably in Google Docs) or by themselves (yet with a writing vibe filling the air) to write an article, a manifesto, a book, a blog post, a plan, or what you will.

• Julie Meloni, “Project develop self-paced open access digital humanities curriculum…, THATCamp Prime 2010
• Dan Cohen and Tom Scheinfeldt, One Week, One Book: Hacking the Academy, THATCamp Prime 2010
• Manifesto for the Digital Humanities/Manifeste des Digital Humanities, THATCamp Paris 2010

4. Working session – You’re working on something, and you suspect that some of the people who come to THATCamp might be able to help you with it. You describe problems you want solved and questions you want answered, and strangers magically show up to hear about what you’re doing and to give you their perspective and advice. This is not an hour-long demo; you should come with specific questions or tasks you want to work on with others for most of the session.

• Aditi Shrikumar, Text Mining and the Digital Humanities, Great Lakes THATCamp 2010
• Kathleen Fitzpatrick, “how to transform something like CommentPress into a viable mode of open peer review,” THATCamp Southern California 2010
• Sherman Dorn, The Ill-formed Question, THATCamp Prime 2009

5. Workshop – A traditional workshop session with an instructor who leads students through a short introduction to and hands-on exercise in a particular skill. A workshop may be arranged beforehand by the organizers or proposed by a participant who agrees to teach it.

• Kirrily Roberts, FreeBase workshop, THATCamp Bay Area 2010
• Bethany Nowviskie and Bill Turkel, Hacking Wearables and E-Textiles Workshop, Great Lakes THATCamp 2010.
• Aditi Muralidharan, Visualization workshop, THATCamp Bay Area 2010

6.  Grab bag – Indefinable by definition. It’s astonishing how creative people can be when you give them permission; performances and games are welcome.

(Text lifted in great part from THATCamp Prime 2012: Sessions.)