Your motherblog might need a (mostly invisible) spouse

Course blogs are everywhere these days. While Tumblr and instagram might be the “it” social media of the moment, a course blog’s suitability for exchanging ideas, presenting research, and engaging in an open, distributed conversation is hard to beat. Course blogs come in all shapes and sizes of course, but the format I’ve been using extensively this year came about with the help of Gardner Campbell. I’ve deployed it in a range of course settings, from seminars with six undergraduates to upper-level courses with thirty-eight. It has worked beautifully for helping new graduate students come to terms with historiography as well. Several people have asked me about the set-up, and although it can be explained with spoken words and hand motions, it will be easier to lay out here.  So what follows is partly a plug for this particular configuration and partly a “how-to” for those who want to try it themselves.

Why does a motherblog need a spouse?

Like many course blogs, this format uses a “motherblog” that syndicates posts from all of the contributors’ individual blogs. Each student has their own “childblog” which they can customize according to their own preferences. The student’s blog becomes an eportfolio of their work, a “deliverable” they can take away (and continue to build on) when the course ends. The motherblog aggregates the feeds from all members of the course in one easy to find and search place.

Mother Blog

Motherblog


 Child Blog

Childblog3

But how do you handle the comments?  One of the main advantages of having students blog is the amplification of the audience. Instead of completing an “assignment” for me (“Is that what you wanted?”), they are writing for a much more diverse and interesting audience — it includes me, but is mainly comprised of their classmates and anyone else who happens to be interested in what they have to say. Commenting gives us a chance to engage in a multilateral conversation about the substance of the posts over a few hours, several days, or the entire term. But since every student has her own blog, the comments on a particular post are going to be attached to the individual blog, rather than the course blog. (You can set the motherblog up so that comments on the syndicated posts appear on the course blog, but then they won’t be attached to the student’s blog.)  This means you have to click around and look for a conversation to join, which could be serendipitously fun, but might also be a pain in the neck.

The solution is a second blog that aggregates all of the comment feeds from the students’ blogs. I think of it as a (mostly invisible) spouse to the motherblog, because it does a lot of the heavy lifting in terms of pulling content together and pushing it forward. But like many spouses, it does this quietly and without much recognition. It will work just as hard as the motherblog, but never rise to a search engine’s attention.  This blog of the collected comments from all of the students’ blogs appears in an RSS feed on the mother blog. When someone goes to main website to see what’s been posted recently, the comments on those posts are visible on the front page as well.  Clicking on a post or an interesting comment will take you directly to the student blog you want to engage.

Comment feed on Mother Blog

 CommentsonMotherblog

Student Blog Post

PostWithComment

  It’s elegant, functional, and not hard to set up:

1) Create and set-up your motherblog to aggregate the posts from all of your contributors. (If you don’t have access to a WordPress enterprise installation, you can use an RSS multiplier to get the similar kind of functionality as you have with the syndication application.)

2) Create another blog to do the same for the comments.

3) Syndicate the individual blogs to the comment blog:

Syndication1

4) Select the “comments” feed:

syndicationcommentfeed

5) On the motherblog, pull the comment blog through the RSS feed and relabel the RSS feed as a comment feed:

CommentFeedRSSrename

6) Drag the “recent comments” widget on the mother blog to the “inactive” area of the dashboard:

InactiveWidgets

7) Create a link to the comment blog on the motherblog (optional):

CommentBlogMenu

8) That’s it!

DO Save the Time of the Reader/ Researcher

As a historian, I self-identify as a “super searcher.” I was trained to identify and track down whatever evidence I need, regardless of the time, effort, and tedium involved. As a researcher those skills stand me in good stead every day, but as a teacher, I want my students to spend at least as much time working with materials as they do identifying and locating them. They need to develop strategies for searching and acquire the content expertise to search intelligently, but they also need to start with “the good stuff” so that their curiosity will take over and spur them to dig deeper. For the project Brian Matthews cited in [Don’t] Save the Time of The Reader, my goal was to bring the teaching and learning of Soviet history into the networked age by using blogging and googledocs to contextualize sources available in at least three formats: print, the open web, and proprietary databases.

I’ve provided some background on the design of the course elsewhere, but the basics were as follows: Each student (38 total) had a blog that served as their digital portfolio for the semester and contributed to the content of the course. The individual blogs were syndicated to a motherblog with a magazine-style layout that included a slider and a featured post section. We curated the content from the individual posts into a “weekly edition,” highlighting the most engaging and sophisticated research in the slider or with a “red star.”

The class used a number of openly accessible collections, especially Seventeen Moments in Soviet History — a rich multi-media repository of translated primary sources for the Soviet period.  Other high quality internet sources for Soviet history include Gulag: Many Days, Many Lives —  a browseable archive of video, artifacts and film, that immerses viewers in the history of the Soviet Union’s vast system of forced labor camps; Making the History of 1989 — a digital history repository for studying the collapse of Communism in Eastern Europe; and 1917: Did the War Cause a Revolution?  an interactive teaching module about the Russian Revolution based on primary sources (part of the Digital History Reader created by a team of faculty at Virginia Tech with funding from the NEH)

Students find topically coherent, multi-media repositories like Seventeen Moments appealing and user-friendly. The images and audio files are engaging, the translated primary documents are selected for their significance and interest, and the scaffolding of the web site makes it easy to dig more deeply into a particular topic or branch off on a different one.

Getting students to use (and like) the proprietary databases held by the library presents more of a challenge. Every vendor has a different search interface, the scope of the resource (i.e. The New York Times) is far broader than Soviet History, and the sophistication of the database can be daunting for the novice researcher. For this project I wanted students to take advantage of the ProQuest Historical Newspapers, and the Current Digest of the Soviet Press, (now called the Current Digest of the Russian Press) a translated monthly compilation of articles from Soviet newspapers dating back to 1949. I was pleased that once the class got the hang of finding, analyzing and citing materials from the openly accessible sites, they also found it easier and more interesting to work with the Current Digest. Providing a link directly to the search interface for these resources helped, as did using class time to work together on finding articles about particular topic.  In classic crowd-sourced style, our collective networked searching proved far more efficient and productive than our solitary forays would have been.  The student’s post became more sophisticated in terms of analysis and source base as the semester progressed.

In this context, the first step in saving time for student researchers involved helping them build proficiency with openly accessible repositories that are relatively easy to use and cite. Once the students’ interest in the subject, content expertise, and searching skills had developed, they were more willing to add the Current Digest or the Historical New York Times into the mix and invest the extra time and attention to detail these resources require.

“Saving time” like this allowed the class to use time more productively. Class-sourcing the content for an entire course required a significant investment of time and energy from all of us, but had numerous benefits, including:

1) Giving students a bigger role and larger stake in developing historical knowledge and presenting history to audiences outside the academy;  2) Bridging the conceptual and technological divide between the resources of the open web and the proprietary knowledge of commercial databases; and 3) making the walls of the classroom and the library more porous and transparent.

Expert researchers still need their super searcher skills, but we also need to acknowledge that the world is changing.  Tomorrow’s super searchers will be just as competent as we are, but they will arrive there by different means.

css.php