Aggregating blog entries for the upcoming Mentor Texts series
As I wrote in my last post, next week I will be doing some joint writing with folks around the idea of mentor texts in the digital writing workshop. However, I wanted to take a moment and write out/explain how we are going to aggregate all of our posts into one spot. With all of us blogging at different websites, I wanted to be sure to pull all this thinking together to share and record this event. It had to be automatic so none of us had to “do” anything other than focus on our writing and our ideas. Basically, I wanted the tech to take care of the process so we could take care of the thinking. What follows is an explanation of what I did, how I set it up, and why I chose to do it this way as opposed to the other possible solutions.
One of the goals that I had when we began talking about this project is to pull all of the blog posts from each of the five blogs into one spot. I had toyed with using Delicious, Diigo or another social bookmarking tool so that we could each bookmark our posts into one common space. However, I quickly decided against that because, from my point of view, I wanted to completely focus on the writing, not the process that I would have to go through (and teach everyone else to go through) to bookmark all these posts. I knew that there had to be a way to do it using the RSS feeds that each blog created. In the past I had toyed with the website ifttt.com. This site basically uses a trigger that I can set up to signal another action, also defined by me. To simplify that process, what ifttt (which stands for “if this then that”) allowed me to do was create an event on their service that looked at the RSS feed that my blog creates and searches for the term “mentor texts”. If it finds the term “mentor texts” in my RSS feed, then, it would pull the entire text of my post and do something with it. In this case, I wanted it to post someplace else.
Ifttt.com has a number of preset services (they call them channels) to choose from that you can activate to create events or triggers. Using the API of tools like Evernote, Twitter, and YouTube (see a complete list of channels here), ifttt uses the language of the web to pull all of these services and then do another action. The two channels that I chose were the “feed” channel and the “Posterous” channel. Posterous is a blogging site that makes it really easy to share content. I had set up a Posterous account quite awhile ago but never did much with it. Seeing that ifttt worked with Posterous, I set up the RSS feed for this site so that whenever I posted something and tagged it with the phrase “mentor texts”, ifttt would recognize it, pull the entire text, and then repost it to the Posterous blog that I set up for this project. To set this up, I had to activate both the feed and Posterous channel on ifttt and then create the task.
Kind of surprisingly, it worked flawlessly with my blog. I posted a number of test posts and within 15 minutes (the amount of time ifttt checks my feed), whatever I put in that post showed up on Posterous including any pictures or media.
My next step was to go back to ifttt and take the task that I had created and make, what ifttt calls a recipe. Basically, this creates the formula for the task and lets you copy it. Using that recipe, I set up Franki’s blog and had her test if for me as well. This is where it got a little more complicated.
What I learned when I set up Franki’s blog:
- Not all RSS feeds work the same way – I knew that there were different types of RSS, but I didn’t really know the difference between and “atom” feed and an “xml” or regular RSS feed. Whenever I’ve needed to use RSS before (usually with an RSS reader) it just worked.
- Blogger’s feed wouldn’t pull the full text.
- Only a new feed item would get pulled into the Posterous blog, no past posts would be pulled in.
- Ifttt searches the entire text, not just the tags.
Armed with this new knowledge, I went back to Franki’s feed and added a short line of text at the end of the existing blogger feed. Franki’s feed is “http://readingyear.blogspot.com/feeds/posts/default“. This is an atom feed that ifttt doesn’t recognize. However by adding the text “?alt=rss” to the end of her feed, you are redirected to the regular RSS feed which works famously.
Troy, Kevin and I all use WordPress so there was no need to change any of our feeds. Franki and Katie use Blogger and adding that bit of text to the given feed URL worked fine. Tony uses Typepad which also creates an atom feed. In the case of his blog, I just changed his feed from http://keeferto.typepad.com/blog/atom.xml to http://keeferto.typepad.com/blog/rss.xml and it worked.
After having everyone test each of their blogs to make sure it worked, I decided to do one more thing so that I can really stay hands off with the technical side of the project and focus on the writing. I wanted to be notified whenever my tasks in ifttt was triggered and one of us had posted a new topic on the Posterous site. One of the things I really enjoy about Google Calendar is that I can get text message notifications when an event is added or to remind me of an event. Ifttt also has an SMS channel that I can set up to text me when a new post is put up on Posterous. So now, any time any of us posts something next week, ifttt will post it to Posterous and then I will get a text message so that I know I have something new to read.
For a project like this, I think this is an ideal solution. It automates the whole process and takes those tasks that I would normally do manually and takes them off my plate but will still aggregate all of our thinking into one place. The technology is working for us and getting out of our way so we can focus on thinking and writing around this project.
To see the results of our thinking around mentor texts, visit the Posterous site and follow along.
Last Thursday we hosted our second film festival in the Parkway School District and, from the reaction we got from parents, teachers, students and administrators, it was a resounding success. If you’re interested in seeing some of the films, visit 

