Close

Twitter Chats for "Introduction to the Old Testament"

Posted on by Brooke Lester

Something new this year for the online Intro class: weekly Twitter chat.

How It's Done

On Twitter, you normally see the posts of people you follow, in an undifferentiating stream with the latest posts at the top. However, you can also view a Search window, and see all posts that include your search term…including posts from people you do not follow. So if a set of participating users agree to include a shared search term in their posts, then they can use that Search window as a chat forum. By convention, such a search term is proceeded by the hash sign (#), and is called a "hashtag": for example, our hashtag is the hash sign followed by our course number, #11500x. We meet Tuesday evenings 7:00-8:00 pm, CT.

Our Course

This course is "Introduction to the Old Testament," a fully online course with about 20 learners, taught by me at Garrett-Evangelical Theological Seminary. The course is completely asynchronous: there is no time at which all learners must participate together in real time. Also, our learning management system (Moodle) does not include a "virtual classroom" module. (It could, but we have not purchased one.) So, a Twitter hashtag chat allows us a space in which to have synchronous engagement with one another.

How It's Going

I am using the one-hour weekly Twitter chats to engage "big ideas" or "essential questions" that are foundational to the tasks they are accomplishing in the course; for example, "What is 'academic biblical studies'?"; "Academic biblical studies as public work"; "Biblical literature as narrative art"; and so on. Participation is voluntary, and has ranged from 10-14 learners (of my 20) to a scant 2.

Since Twitter is a public forum, our followers from outside of our class have discovered our chat and joined us. This includes my colleagues who teach biblical studies elsewhere (some known personally to me, but not all), former students, and other interested outsiders.

Each week, I have assembled a list of prompts, to keep things going or to get things back on track if necessary. I have not had to use them often, but I feel more comfortable having them ready to hand. Some "template" tweets are a good idea to keep handy though: reminding learners to use the course hashtag, announcing the chat and its topic, inviting lurkers to join in, etc.

Nearly all of my learners are brand new to Twitter. In every class I teach, whether online or face-to-face, I like to incorporate an activity that will introduce most of the learners to a new digital accomplishment of some sort. The idea is not that they should all like Twitter, but that they should have regular, guided experiences of braving new digital tasks.

Have you ever used Twitter chats as a teacher or as a learner? Are there other digital "new frontiers" that are part of your course work this year?


[Twitter Chats for Introduction to Old Testament was written by G. Brooke Lester for Anumma.com and was originally posted on 2012/09/27. Except as noted, it is © 2012 G. Brooke Lester and licensed for re-use only under CC BY-NC-ND 3.0.]

Borrowing Syllabi: Collaborate, Re-mix, Acknowledge

Posted on by Brooke

A number of years back, Chris Heard posted the flowchart [link updated] by which he assessed a certain paper-writing assignment. I have mentioned before that I picked it up and modified it for my own use. At that time, I incorporated much of it into a checklist for the students to consult before submitting the paper. More recently, convinced of the value of rubrics for assessment, I have developed that into a three-column rubric. I realized recently that, some point, in the heat of revision, I had dropped my standard acknowledgment of Chris's original work.

Katharine Harris wrote recently on the value of including acknowledgments in syllabi: if we are smart, we are re-mixing assignments and assessment tools designed by others, and as an ongoing research project in curriculum, a syllabus should reflect that.

"Re-mixing" syllabi created by others (or their elements) is not different from how designers of open-source software "fork" already-existing applications: taking a tool that exists, then copying and modifying it into a new creation, is to create a new "fork" for that tool. Brian Croxell talks about "forking a syllabus," and Lincoln Muller offers tips on using GitHub—an online resource for sharing and forking software code—to collaborate on and share syllabi, assignments, and assessment tools.

I have begun developing an online lesson for faculty on the value of using plain text [in] the writing process and in collaborative writing, and a section of that lesson will include the use of GitHub for sharing modules from syllabi: policy statements, projects, assessment tools, and so on. I will plan to work out parts of that lesson here on the blog.

How have you built on tools drawn from others' syllabi? What are your habits regarding acknowledgment?


[Borrowing Syllabi: Collaborate, Re-mix, Acknowledge was written by G. Brooke Lester for Anumma.com and was originally posted on 20121/04/18. Except as noted, it is © 2012 G. Brooke Lester and licensed for re-use only under CC BY-NC-ND 3.0.]