Here’s my post-THATCamp reflection. Hope everyone keeps sharing here and on twitter.
Archive for category Post-Camp Sharing
I’ve posted ALL the tweets (I think) from #thatcamp arranged by session at adellef.co/318 . Sadly, my brain gave out, so a number of tweets are unaffiliated with their proper session. Your Comments could help, though!
I’ve temporarily made my blog open to all comments (I usually have to approve every one so as to prevent certain enlargement advertisers from using my site inappropriately). This means you’ll see your comments pop up automatically, at least until later this week when the SPAM gets really bad.
Thanks in advance for your assistance, kind thatcamp’ers!
I’ve done some blogging while at THATCamp and since I’ve come home.
- Notes on day one
- Notes on day two
- A summary for my place of work (ZSR Library @ Wake Forest University)
- A reflection post on my own blog
Great unconference you guys! You’ve given me a lot to think about and I already have some ideas about things I want to try to do in response both at my place of work and in my own scholarship. Thanks all!
I wanted to thank everyone for their participating in the Introduction to Programming with Python and the follow-up session on Django during THATCamps’s BootCamp!
As mentioned during the session I am linking a few resources that can be helpful for aspiring Python Programmers as well as a few other resources referenced. I hope everyone finds them useful.
Great Python Resources
- The Zen of Python – What is the sound of One loop Iterating?
- Python For Non-Programmers – A great meta-list of tutorials and lessons on Python for the non-programmer.
- Google’s Python Classes – Some good screen-casts teaching python from the beginning.
- Official Python Documentation – Great documentation is a core value in the python community and few better examples than the official documentation.
- Django Documentation – The framework use in the second session is also well documented.
- Cool URI’s Don’t Change – Stable and persistent URIs are a vital part of creating durable scholarly works and the foundation of linked data. Every digital scholar can benefit from reading this article.
- O’Reilly on The Importance of Unit Testing – Always important to create a sustainable and extensible application, unit tests can be particularly vital in scholarly projects because of their long lifecycle.
Code From Sessions
Here are the hacky pages of code I was displaying during our session discussion. I don’t see an ability to upload files here so I’m linking them as Google docs.
Hi all, intrepid THATCamp Coordinator Amanda French here, signing on from the Center for History and New Media to ask you to fill out our THATCamp evaluation survey. It’s brief, and we’d love to hear from you. I must say I’m particularly keen to see what comes up in the “favorite session” fields, though those, like most in the survey, are not required.
Here’s the evaluation: surveymonkey.com/s/thatcampeval
Meanwhile, I have to give all of you a big fat “Strongly agree” on the Likert scale to the imagined survey items stating: “THATCamp Southeast provided a most interesting weekend Twitter stream” and “THATCamp Southeast participants came up with some fascinating session ideas and wrote some terrific blog posts.”
I’ll collect the series of posts I’ll be making this week about my THATCamp SE experiences here. Expect updates.
I’d like to add a special thank you to our hosts, expression of admiration verging on jealousy for the beauty and functionality of the Emory Library space and its awesome guest wireless connection, and thanks to all who participated in conversations with me (or near me so I could eavesdrop.) I learned a lot. Best wishes to all – Phoebe Acheson, @classicslib
Check out my post on “Why I Love THATCamp”! I don’t allow comments on my homepage, but I’d love to hear what you think here!
The DH & Assessment session Saturday afternoon started with the usual mini-rants about our regional accreditor and reductionist assessment and turned into an “oh, wow, here’s a tool for this” discussion. The core of the discussion revolved around the open-source <emma> assessment tool built for the University of Georgia’s first-year composition class. (Links: <emma> front-end, which will be frustrating because it’s just the sign-in for UGA students, and the website of the Calliope Initiative, the non-profit continuing development and the business end for other institutions.)
At the lunchtime Dork Shorts, Robin Wharton had demonstrated the gist of <emma>: students submit papers in Open Document Format. Then instructors and peers can comment on specific passages and code their comments by area of the comment (e.g., thesis development might be coded as green, something else as yellow, etc.). Students’ revisions are linked to their original documents, they declare when a revision is the final document, etc. So far, this looks like a useful, user-friendly way to comment on student work.
In the afternoon session, it became clear that <emma> was also being used for institutional assessment–it has the ability to look at the comments and the comment categories, a sample can be drawn for assessment by a set of readers, with disagreement on basic judgments by two readers kicked to a third reader or other moderation process, etc. And the system has the capacity to allow conclusions such as shifts in comment categories (i.e., student skill development) across a course or a longer span of time. In other words, institution-level judgments based on the day-to-day evaluative culture within composition instruction.
Those at the session had the obvious questions about the system (expensive? it was developed by one person in the English department who taught himself programming, along with two graduate students) and then we started talking about what would be necessary to develop parallel systems for performances (e.g., faculty-juried music performances at the end of the semester). So we gabbed a bit about Pear Note, Transana, and some other options. And then we discovered that as ODF documents, the base documents students submit can include media. Hmmn…
Bottom line for me: Huge thanks to Rob Balthazor and his team at UGA for showing how digital humanities can put assessment on a much less shaky footing.