Showing posts with label Blogging. Show all posts
Showing posts with label Blogging. Show all posts

LEM: Community Portfolio

Below is my response for the Learning Design Challenge #10: Sharing Individual Content via Community Portfolios. #DailyLEM10

This is something I really want to do for my own classes next year, both with memes created by the students (and their thoughts about those memes), and also the stories they write. For this example, I pursued the meme idea since that fits in nicely with the workshop on open content that we did earlier this summer, but without specifying the nitty-gritty of the community space: Incorporating Open Content.

Right now, students have their own blogs and/or websites as individual portfolios, and I curate content myself (I pin new stories to Pinterest Boards like this one: Indian Epics Fall 2016 which students see at the Project Directory class page), and I keep a lasting archive (eStorybook Central), but I would like to create something more student-driven, where they are putting content into the community space based on what they consider their best work. Right now I don't even have mechanisms in place to harvest the memes they share/create; I only curate stories.

As I've been wrestling with this question for a long time, I see it more as a technology problem than a design problem: I know what I would like to have happen but I had a hard time finding the technology to support it... until now! While on my evening walk yesterday, I had a real brainstorm, and I'm excited to share that here!

What is your desired experience for the activity?
* I want students to be able to share the best things they create (memes, stories) with other students in the class, and I want students to be able to easily discover that content. My goal is to diminish my curatorial and administrative role in order to hand more of that over to the students; after all, only the students know what they consider to be their best work!

How will you motivate participants to engage in “authentic” sharing?
* Students already create content in their own spaces, and they visit each other's spaces as a mode of sharing and learning, and motivation there is very high — so I don't need to do any motivating; students will be even more motivated if I can help them drive the curation process more actively.

What kind(s) of feedback make the most sense for this kind of environment?
* I already have some good student commenting processes in place; my goal here is to add new avenues both of sharing and of discovery which will improve the commenting: the more students are identifying their own best work and, consequently, finding content that is really high quality, the better the commenting process will be.

What are some possible constraints for this design?
* The real constraints are technological: specifically, the mechanisms for sharing (students identifying best content that they put into the shared space) and the mechanisms for discovery (students exploring the shared space to discover what they like best).

Plus: A technological nice-to-have...
* I would like to have one version of the solution be Canvas-friendly; I personally don't use an LMS for my class space, but if I could find a way to make this work in the Canvas space, it is more likely to be an option other faculty at my school would consider.


EURKEA: Inoreader! The key to my solution is this: I will use Inoreader (which currently aggregates all incoming content from my students' blogs), and specifically I will use Inoreader Rules. So, if students include a keyword in their blog post somewhere, I can use an Inoreader Rule to automatically assign a tag. I will just need to write up instructions for how students can add a simple but distinctive keyword (like MemeGallery, one word) when they want to flag something as best content. I can also manually add the tag, if needed, and if a student changes their mind, I can also remove the tag manually. (I already have some processes like this in place for student-generated content; for example, here is the stream of stories for the class — but without a student self-nomination process: Myth-Folklore Stories.)

Once the self-nominated content is tagged for the Gallery, I can then easily redisplay that content in all kinds of ways!

I can put it in Canvas, like this: Meme Gallery. To do that, I use Inoreader's export to HTML feature:


Even better: IFTTT will deliver that content to all kinds of platforms! In IFTTT, the trigger is "Inoreader: New tagged article" (including articles tagged by a rule). Then, the IFTTT action can really be anything. Just to show one example here, I set up a Tumblr that will be filled with content automatically. Here's the IFTTT recipe:

And here's the resulting Tumblr: Meme Gallery Tumblr. Of course, I can play with the gazillions of Tumblr themes to find the best display. I also have access to all the features of Tumblr too. Lots to explore there! I just set this up super-quickly as a test case.

Why Tumblr? An excellent Tumblr feature for my purposes is the randomizer. Randomizers are essential for browsing and discovery for this type of content, and Tumblr is great at delivering posts at random (just add /random to the Tumblr URL). Here's the link: Meme Gallery - Random! I also included that randomizing link in the Canvas page.

VERY happy with this. The real magic is in the technology here, not so much the design. I am so excited to try this out with real student blogs in the Fall!!!

Click here for full-sized view:


Update: I had faked the Inoreader tag to test this out, but I also put a rule in place that will scan all my blog posts just like I want to scan all incoming student blog posts... and it worked! I just published my Growth Mindset Cat meme and because the keyword appeared in the post, presto, there it is in Canvas!


Update: I also created an IFTTT recipe with Pinterest... and that worked too! There's the cat, automatically sent to Pinterest:

10 Tips for Building a Student Blog Network

I teach fully online classes, and blogs are "the classroom" where we meet online; it is how my students and I all interact with one another, and I've been using blogs this way for over 10 years now. There are lots of different blogging tools out there, but I've tried to make the tips below software-neutral, focusing on what you can DO with blogs... and then you can decide on the specifics of how to proceed with your own classes. So, hoping for a world in which everybody blogs (!), I've listed 10 Blogging Tips below... plus four pre-semester strategies to gear up and get ready to go.


GEAR UP:


Become a blogger yourself. Before you start blogging together with students, take a semester (or summer) beforehand to do your own blogging and see what it's like. Create your own blog, post regularly, and read other people's blogs too. Are there other people at your school who blog? Get in touch with them and see what advice they can offer. Ask questions, and learn how to make the most of your blog. Your experience and enthusiasm will be a big boost for your students as they get started! You might blog on topics related to your course, or you might keep a blog based on some other personal interest or project. For example, I don't teach Latin anymore, but I do keep a Latin blog: Bestiaria Latina.


Learn how to use a blog aggregator. A blog aggregator, also known as a feed reader, allows you to follow lots (LOTS) of blogs so that all the posts are consolidated in one place. You can organize the incoming posts in folders, and a good aggregator will also help you keep track of read/unread posts, along with options to search, filter, and label post content. Many people use Feedly, but I far prefer Inoreader. If you don't use a blog aggregator now, try Feedly first (it's very user-friendly), and then you might migrate to Inoreader later when you are ready to take advantage of the wider range of features that Inoreader offers. When your students start blogging, you will definitely want to have some kind of feed reader in place in order to keep an eye on their posts as they accumulate (see below).



Commit to a platform. For many years, I've been using Blogger (Google's free blogging platform), and I provide my students with all the technical support they might need to use that platform. I like Blogger because it is very easy to use and also because it is very javascript-friendly; those are priorities for me, and you need to discover what priorities are important to you. So, experiment with a couple of different platforms yourself, see what you like best, and then commit to supporting that platform with your students. But note: there is no reason that all your students have to use the same platform; Blogger is the only platform for which I provide technical support, but if a student is already using another blogging platform, that's great! I define the platform requirements in very basic terms — linkable post labels, no advertising, and full RSS feeds for both posts and comments — but beyond that, the students can make their own choice. Since very few of my students have ever blogged before, almost all of them choose Blogger, but every semester a few students use WordPress, and I am really glad that they do; it's a chance for other students in the class to see what different blogging platforms offer.


Build the blogging into your course design. In my classes, all the student work happens in the blogs; there are no quizzes or tests, and there are no papers. Your classes might also use blogs intensively, or you might just use the blogs for a once-a-week reflection activity; it's all about what will work best for you. To see the kinds of work my students do in their blogs, take a look at this week's assignments: Week 9 (and that's a typical week; my courses use a week-by-week module design). Just how blogs will fit into your course design depends totally on the course. As a general design principle, though, I would advocate for consistent assignment(s) so that your students will get regular practice and reinforcement; that's especially important if your students are new to blogging. After a few weeks of doing the same type(s) of assignments each week, the blogging will become easy and familiar!



And then... LET THE BLOGGING BEGIN:


1. Start students blogging right away. After a brief overview of the class, the very first thing that my students do is to start their blog. Here's how that assignment works: Create a Blog.  I follow that up with a fun ice-breaker type of assignment: Picture a Favorite Place. My goal is for students to feel confident and excited about what they can do with their blog right from the very start. It's also a great way for me to start to get to know the students; I subscribe to their blog posts and comment feeds in Inoreader (see below) as soon as they create their blog, and that allows me to keep an eye on their work from the very first day of class. I also make sure to cover important technical issues right from the start: labels on blog posts, comment configuration options, name display / profile settings, creating links, inserting images, etc. That way, later assignments don't have to cover technical issues and, even more importantly, students can feel confident and in control of their blog right from the start.


2. Encourage students to customize their blogs. This is easy to do since the students are highly motivated to customize and personalize their blogs; some of them start customizing their blogs immediately, which is wonderful to see! To give them the support they need, I use "Tech Tips" for extra credit; the Tech Tips are not just limited to blog development, but the blog tips are definitely the most popular. Here is my Tech Tips list for this semester: Tech Tips: Blogger. The classes I teach are not technology classes, and some students are not interested in developing their technical skills at all... and that's okay. The extra credit Tech Tips are there as an option for any student who's interested. What's nice is that as the semester progresses and students watch each other's blogs take shape, even those students who were not originally interested in tech exploration often become curious about how to customize their blogs too. Also, while I've never had a student actually lose their blog, I encourage students to learn how to back-up their blogs along with any other work they are doing for class: Back-up, Check-up and Review.


3. Use labels/tags for blog navigation. If students blog every week (and my students are posting several times per week), their blogs are going to fill up with content quickly. Using labels for navigation is then essential: the consistent navigation that labels provide is how other students can quickly find posts at any blog in the class. So, for example, students label their Introduction post with the label "Introduction," and that makes it easy for other students to find that Introduction post later (see below); so too with the "Comment Wall" post, etc. I make sure to provide explicit instructions about labeling posts in each blog post assignment starting from the very first blog posts. Here's a screenshot of label navigation in a blog sidebar; some students opt for horizontal label navigation instead, and either way is fine of course — it's their choice:




4. Encourage use of multimedia in posts. Right from the start, I emphasize the use of images in posts, along with giving students a crash course in image licensing and helping them to find public domain and CC-licensed images to use in their blogs: Finding Images. I also make the use of images (and image citation) part of their blog post assignments. Then, as the semester goes on, I also encourage the use of video and other embedded media in blog posts; here's an example of a video-based assignment that I use in the review week mid-semester: Music for Your Comment Wall. Being able to work with images and video in their posts is something that can be highly motivating for students, especially for students who are less confident in their writing.


5. Build blog commenting into the class. Students are posting in their blogs every week, and they are also commenting on each other's blogs. I don't use discussion boards at all; instead, I use the blogs as the locus of conversation. To help the students get to know each other week by week, I use randomized blog groups, and that randomization also helps ensure that each student gets more or less the same number of comments each week. How it works: each week, I sort the class into groups of three students at random (I just use a spreadsheet with a randomizing column to do that), so each student is thus commenting on the blog of two other students each week while receiving comments back from those same students, and I also offer an extra credit blog commenting assignment for students who want to do more commenting. I also make sure to show students how to check their comments, using email notifications and/or the blog dashboard.


6. Revisit Introduction posts. Each student writes an Introduction post in their blog during the first week of class. Then, as they comment on other students' blogs each week, they comment on the post(s) for that week AND they comment on the Introduction post so they can learn something more about that student, learning about each other. As a result, the Introduction posts get the most comments of any other post at the blog, and I encourage students to tinker with their Introduction post all semester long, adding pictures, videos, etc. Since my classes have appx. 40-50 students, the Introductions are important because students are meeting new people in class every week all semester long. Because they are Gen. Ed. classes with students from all the different colleges and majors, the Introduction posts are a lot of fun: the students are doing so many different things with their college careers!


7. Use Comment Wall posts. In addition to creating an Introduction post, I ask each student to create a "Comment Wall" post. The Comment Wall post provides a space where someone can leave a comment that is not in response to a specific post at the blog but instead as a conversational comment left for the blog owner. In my classes, the Comment Wall space is useful for all kinds of reasons: they provide a place for following-up with someone who may have left a comment at your blog, for complimenting someone on their blog design or asking them a question about their blog, and also for leaving comments about class work that is not blog-related, such as comments on project websites. Of course, just how that might work for your class depends on your course design and activities. Like the Introduction post, the Comment Wall space is where students are "presenting" themselves to other students in the class, so I encourage them to add a picture to the post, and later on to add video of some kind, just for fun.


8. Use randomization to increase discovery. Especially when a class is on the large size (as mine are), randomization is an important way to help all the students get to know as many other students as possible without a lot of work on my part. I use random blog groups each week for commenting, and I also build a blog randomizer so that students can visit the blogs in class at random: Myth-Folklore and Indian Epics. If students are looking for a specific other person in class, they can use the Blog Directory, but if they are just browsing, they can use the randomizer instead. (I build that randomizer with a wonderful free tool built by one of my students which you can find at RotateContent.com.) I also use the blog randomizer when I have some free time, especially at the beginning of the semester, so that I can spread my attention throughout the blogs randomly!


9. Reuse blog content. A great way to let students see that you value what they are writing in their blogs is to reuse that content. So, for example, in one assignment I ask students to reflect on the commenting culture in class, and I then collate their comments into a webpage: Thoughts about Comments. To get even more use out of their remarks, I create a randomizer which I can then use as part of the commenting assignment itself, reminding them about the different ways that people value the commenting process; you can see the randomizer at work in the yellow box here: Week 7 Comments. Of course, just how you want to reuse the content in your students' blogs will be based on your course design overall; the key is to think about the possibilities for reuse that blogs can offer, very different from classroom discussion which is not so easy to harvest and reuse. In addition, I try to design assignments so that the students themselves are reusing and revising their previous blog posts, building on past work for new assignments and also learning from what they read and see at other students' blogs.


10. Be blog aware. As the students begin blogging, I comment on their first posts, but after the first week, the commenting is very much student-to-student, and I comment only very occasionally on the blogs. At the same time, I keep a close eye on them using Inoreader as my feed reader. I have a folder for the incoming posts in each class, and I also have a folder for the incoming comment stream. This lets me easily keep an eye on all the posts as they come in, and I also try to keep an eye on the comments. This way I can get a "vibe" of how things are going in the class, seeing what students are thinking about, questions they have, etc. If I notice a problem (the most common problems have to do with image formatting), I can quickly comment, and I also cover questions and problems in the daily class announcements (and my class announcements are in blog form of course) based on what I learn from watching the blog stream. There's always a lot going on, but with a feed reader you can keep an eye on it all, learning and observing. Here's what my Inoreader view looks like, and you can do much the same with Feed Reader or whatever other blog aggregator you prefer:



So, I think those are the main points that I have in mind as I use blogs in my classes, but please let me know if you have questions I have not answered here or if there are questions you have as you build a class blog network of your own. I am a huge fan of blogging as a tool for creating and sharing online, and that means I'm always glad to brainstorm with others about how they might be able to make blogging a part of their classes too. Blog on, everybody! :-)


10 Reasons Why I Use a Blog for Class Announcements

I've been having trouble getting back into the swing of things at this blog, so I'm going to try the "10 Reasons Why" approach. The post can more or less write itself this way! I'm starting with this particular list in celebration of Blogger https allowing me to make even better use of my announcements blog (more about that here).

First, you might take a look at my Class Announcements blog. There's a new announcement every day, including Saturday and Sunday (Saturday is a slow day, admittedly, but Sunday is probably the busiest day in terms of students who are doing work for class).

1. Modeling a blog for my students. Given that my students are also blogging for class, I appreciate being able to model the usefulness of blogging for my students, along with good practices in formatting, linking, etc. There is no particular value in modeling my use of D2L BS for them. Real school requires real tools, in my opinion, not faux tools like the LMS.

2. Blogs are open, not trapped in the LMS. I believe in open education and, when I publish something on the open Internet, it becomes an OER. There are people who subscribe to my class announcements blog who are not in my class because they find the content fun to read, and I also sometimes share my class announcements with the social networks I am part of at Google+ and Twitter. There is no way to make anything inside D2L open to anybody anywhere; it is completely closed.

3. One blog, two classes. Although this might not be relevant to others, it is very relevant to me: I have two different classes, but I use the same class announcements blog for both. If I were to do the announcements inside the LMS, I would have to do separate announcements for the two classes (even if the content were identical!), and if I have to edit or update the announcements, I'd have to do that twice. Nightmare! With a blog, I can update one blog and have it appear as the LMS homepage for both of my classes.

4. Blogs are great for quick publishing. I use blogs as the publishing platform for pretty much everything I do. For me, it is much more congenial than trying to create content inside the LMS. In Blogger, for example, links are easy by design: highlight link text, Control-K, Control-V. In contrast, just try creating a link with the editor in D2L: it assumes you want to create a link to a tool in the course, so the task of creating a link to something on the real Internet is a long and convoluted process. Look how you have to scroll down to create a link to a URL; the list is alphabetical and URL just happens to be the very last item on the list. D2L may call it "quicklink" ... but there is nothing quick about it!


5. Blog posts are linkable. I can include links to specific announcements in emails that I send to students. This is most useful when I need to remind them about something that was highlighted in the announcements a few days ago. Plus, students can click on the link and see the announcement without having to log in to the LMS. So, for example, if a student is working on Dante and I want to share with them a Dante video that was in the class announcements last week, I just provide a link to that announcements post. And, yes, there's an advantage to linking that way rather than to the video directly: I like to get students to pay attention to the announcements; you never know when they might find something else in there that is useful to them.

6. Blogs look good on mobile. For students who might be reading the class announcements on a mobile phone, they look great! Blogger has good mobile-detection, and it switches to a nice mobile-friendly display automatically. So, if a student gets an email reminder from me that contains a link to the class announcements, they will see the mobile version of the announcements automatically if they are reading that email on their phone. Just add ?m=1 to a Blogger blog post URL to see the mobile view. This is actually very handy for creating print-friendly versions of other content I publish with Blogger (like the UnTextbook materials); you can always bring up the mobile version in your browser window and print that, which is much more efficient than printing the standard view.

7. Blogs offer multiple distribution channels. Students can look at the blog in their browser without even logging in to the LMS (I urge them to bookmark the link), they can subscribe by email (a surprisingly large number of students choose that option, and they can use whatever email address they want), they can get an RSS feed (a few of my students use blog aggregators), and, glory hallelujah, the blog serves as the landing page in D2L, so students see the announcements whenever they log in. Screenshot (note the very nifty graphic from the Norse Mythology Twitter stream which just happens to be at the top of the widget at this moment):


8. Blogs have sidebars! Admittedly, I am never sure if students will look at the sidebar of the blog, but I can put some useful information and eye-catching content there on the optimistic assumption that it might get noticed. So, for example, I currently have a class Twitter feed in the sidebar, along with a random growth mindset cat, plus some other basic information and links relevant to the classes. If students are looking at the blog on a mobile device, they don't see the sidebar, but they do see the sidebar if they are looking at the blog in their browser or in the LMS. I love the way the Twitter sidebar lets me keep the content "lively," so that for students who log in more than once in a day, there is the possibility that they will see different images there in the sidebar each time (and, of course, they can click and go to the Twitter stream directly from that widget display). Just for fun, I've embedded that Twitter widget down at the bottom of this blog post too.

9. Blogs are useful content repositories. Almost all the content in my announcements is recycled; I add a little bit of new material every semester, but I rely heavily on past semesters. By labeling the blog posts week by week and using weekday titles, I can quickly access past posts, reminding myself what I might need to be telling students on, say, Tuesday of Week 7. Here, for example, is a label that shows you all the Week 7 posts over time. I would never trust an LMS as a real content repository because, sooner or later, we are going to move to a different LMS; it's inevitable. With blogs, I can download and back up my blog and even move it to another platform if I want, although I've been happily using Blogger far longer than we have had D2L at my school, and I expect I will be using Blogger long after D2L has been replaced by something else.

10. And when the LMS is down.... my blog is up! Pretty much every semester, the LMS is down for some reason or another, and sometimes it is part of a wider campus outage. By having my class announcements outside the LMS, I can let students know about the outage and provide them with regular updates.

Okay, thanks to the rule of 10 I can stop there. I'm wondering if anybody from D2L BS will chime in to let me know why I really should be using their "news tool" instead...

And here's that widget from the sidebar embedded here this post:






Some Tips for Making Good Use of Inoreader


Thanks to Bonni for mentioning this post in a new post of her own -- CARE, VOICES, SCREEN TIME, AND ZOOM SETTINGS -- and I wanted to refer everyone to a super-detailed catalog of step by step how-tos with Inoreader that I wrote this summer, esp. for people using student blog networks:


Thank you, Bonni! :-)


I use Inoreader to manage my class blog network, and I also use it for my own personal learning network, so that means I spend a lot of time at Inoreader! In a separate post I wrote something about using Inoreader's syndication features to create class blog hub pages, and I've also written up a post about using Inoreader to create a blog network for #Rhizo15. In this post I just want to make some general observations about how I use Inoreader, both for my classes and also for keeping up with education blogs and news.

But first . . .

Some Background. I'm one of those people who was really sad about the demise of Google Reader (I used the old Reader bundles and blogroll features extensively), and I never really liked Feedly very much because it had no syndication features, just item-by-item sharing. With Inoreader, though, I have pretty much everything I could wish for when it comes to a feed reader; it's like Google Reader and Gmail and Yahoo Pipes combined. The basic (free) version of Inoreader offers RSS outgoing syndication for folders and tags, so if you have any interest at all in opening up your aggregator space to share with others, Inoreader can do that for you. (Feedly keep promising collection sharing, but even though I have a lifetime pro account and applied for "early access," I still don't have that collection-sharing feature, which I might in fact use for some additional syndication given that Feedly has such a huge user base.)

I should also note there are LOTS of features of Inoreader that I don't use (so I have not mentioned them below), and some features I have not even explored (yet). Most of the features I use are part of the free service, although I use a few premium features also; here are more details about Inoreader free and paid plans. They are good at posting news inside the Inoreader dashboard and at the Inoreader blog, and they are also active at Twitter and Google+. In my experience, they are very responsive to bug reports and feature requests, so don't be shy to contact them with questions and suggestions!


And now, here are . . .

MY INOREADER TIPS AND TRICKS

1. FOLDERS AND TAGS. In a lot of ways folders and tags are alike, but folders really are important because you can do things with folders you cannot do with tags. You can use folders to manage rules, bundles, OPML sharing, and dashboard views; you cannot use tags to do those things (although it would be nice if you could!). So, I make sure to put every feed in at least one folder, and I often have feeds in multiple folders, which can be very handy (so I have Education blogs, and also Must-Read Education blogs as separate folders).

2. USING TAGS. Tags show up with folders in the navigation pane, and they are incredibly helpful for me in managing my reading habits. I also use tags for workflow, adding and removing tags as I process something. With student blog posts, for example, I use tags to tag a problem the student needs to fix (like when they try to display Pixabay images by remote linking, etc. etc.), and then I remove the tag when the student has fixed the problem. I also use tags for sharing specific types of assignments with students, like the stream of Storytelling posts as a page at the course hub.

3. TAGS AND RULES. Rules (a premium feature) allow you to add tags automatically to incoming posts based on various parameters of your own choosing (folders, keywords, etc.); it's very much like creating rules for incoming email (see below for more info). You can add tags manually, of course, but having automatic rules for tag assignment has been a big help for me in managing content as it comes in, syndication to send content out (tag-based RSS feeds), along with overall reading habits and workflow.

4. READ/UNREAD. I rely very heavily on the read/unread signaling in the navigation pane to let me know what I really need to read. In order to make that work, I use rules to mark most of the incoming non-school content as already read, leaving "unread" only those blogs and news sources that I am determined to keep up with no matter how busy school gets. You can set Inoreader to mark as "read" the items you scroll through in expanded view (or whatever views you want to use for scolling/reading), so that is how I manage to at least skim all the incoming student blog posts, tagging things as needed to go back and read later, leave comments, etc.

5. RULES. I use rules to separate out my students' blog posts into tag-based collections, with the tags automatically assigned based on keywords in the title (it just takes a little manual jiggling from me when a student makes a typo, leaves out the keyword, etc., but 99% of the time the automatic rule is all I need). I also use rules to mark most incoming new items from my personal learning network as "read" (see note above) since the read/unread distinction is how I manage my time spent at Inoreader. Rules are a premium feature and they are the reason why I opted to go for the "professional" service (unlimited rules). You can also use rules for other behaviors besides tagging and marking as read/unread as you can see in this screenshot of the rule creation interface:



6. DASHBOARDS. The customizable dashboard is a premium feature, and I find it very handy. You can even have multiple dashboards, although the dashboard is so easy to configure that I usually just reconfigure my dashboard on the fly rather than building separate dashboards. If you do have premium Inoreader, I'd recommend playing around with the dashboard options because they can indeed be useful, although I mostly rely on the navigation pane to do my reading/browsing.

7. STAR. I really like the starred feature which is automatically a "special folder" in Inordeader. I use that to run a "recently starred" widget in my personal blog for example (there is RSS for the star folder, and so I popped that into the RSS widget in Blogger).

8. GOOGLE+ and TWITTER. In addition to standard RSS, Inoreader supports subscriptions to Google+ accounts and Twitter accounts (it's a premium feature). This is very useful for me in creating the "omnifeed" which reflects posts from all my blogs, activity from my two Twitter accounts, and also Google+ posts. You can see the omnifeed at MythFolklore.net.

9. HTML CLIPPINGS TO PDF. My students' storytelling posts lend themselves to more leisurely reading offline. To manage that, I use the HTML clippings to display a gigantic webpage of posts (you can put hundreds of posts on a clippings page if you want), and then print-to-PDF, which gives me a nice PDF file of stories I can mark up in a PDF reader on my iPad. For example, here are 100 of the latest stories from my Spring 2015 Indian Epics class in a webpage that I can print to PDF (220 pages! wow!).

10. PREFERENCES. Explore the preferences. The options you have to configure the Inoreader environment are excellent IMO. I appreciate the responsive color coding (like "new since last visit" in addition to the standard unread), the ability to change font size (I need all the help I can get!), the keyboard shortcuts, and on and on.



And for the DML2015 preparation plan, I did a screencast: Laura Loves RSS.

Course Hub Pages with Inoreader

In preparation for DML2015 in June (and June is soon!), I did a massive redesign and clean-up of some course hub pages. Admitted, these course hub pages are really not something I use or that my students use (which is why I had neglected the pages; the students and I both have other ways of intersecting with the course — more on that later), but it is definitely something I need in order to try to give visitors a sense of how the courses work, and I am now thinking it might also be useful for the students at the very beginning of the semester for a kind of overview also!

You can see the results here:


The idea is that these pages provide you with a basic overview of the courses. The main course hub page for each course shows the blog post feed in the left panel and a list of useful links in the right panel:


In addition to the all-posts feed you see there, I created some additional pages showing the blog comments feed, along with some specific types of posts for the classes: Reading Diary posts, Storytelling posts, along with their "Famous Last Words" posts (a free-form option for blogging about whatever). There are actually lots of other types of blog posts that the students are writing, but those are the main categories. During the semester, the feeds are full of new content every day, but now that the semester is over, it all feels very frozen in time. I'll be excited when the new semester starts up again in the fall, and the feeds come back to life!

Advantages and Disadvantages of an Aggregated Hub

There is no one-size-fits-all solution to the challenge of how you "re-present" a network of independent blogs. By using an aggregator, you can get all the latest posts and their content, which is great, but you lose the distinctive personality of each blog. For example, in the screenshot above, here is that that student's blog post looks like in its natural setting:


To make those person-to-person connections, the students need to engage with the blogs directly (more on that later), rather than accessing the course through an aggregator: the blogs provide personal spaces that allow them to interact with one another as individuals, above and beyond the content of a specific post or comment. When you are at someone's blog, you can read their introduction post, look at their other writing, see what they have put in the blog sidebar, etc. etc. You are "in their world" when you visit their blog; the aggregator is just a gateway to get you to where you really need to go, and the aggregator is also essential for me to interact with the class overall (more on that later).

To see just how varied the blogs are, you can click on any post title in the post display area and go straight to that person's blog. They are all so different! You can also visit the blog list for each class and click to access the blogs that way.

Inoreader HTML Clippings

As you can see, the course hub pages are insanely simple: just a a feed display panel on the left, and some links on the right. I built the feed display panels using the magic of Inoreader's "HTML clippings" view. The customizable clippings view that I use is a premium feature (part of the $30/year package), but you can get the same effect by using the standard clipping presentation and adjusting your webpage design accordingly.

To start with, as students join the class and make a blog, I use Inoreader to subscribe to their blog post feed and also to their blog comments feed. I put the post feeds and comment feeds into folders in Inoreader, and I also configure Inoreader to automatically assign tags to incoming posts based on keywords. The rules are also a premium feature, but it would also be possible to do this by manually assigning the tags and/or subscribing to the label-specific RSS feeds for the students' blog and then putting those label-based feeds in a folder.

So, after you have your folders and tags chugging along, you can then syndicate that content publicly via RSS, HTML Clippings, or an OPML file. I used the HTML Clippings option to create the different pages in the course hub, showing either all the posts for a course (those are blogs in a folder) or all the posts for a specific course assignment. Here's how you syndicate a specific folder or tag:

First, right-mouse click on a folder or tag in the sidebar, and then choose "View Folder Information" (or "View Tag Information").


You will then see a screen that allows you to turn sharing on or off, and also to access the RSS, HTML, or OPML data for that folder (or tag):
If you choose the HTML Clip option, you will then see the various options you can use to configure the display, along with an http link that you can use or an iframe option you can use to insert the display inside another webpage, which is what I did for my course hub pages that are linked above:

That's all there is to it! There are a lot of things I like about Inoreader, and this easy way of sharing curated content is one of my favorites. For another application of this same approach, see my homepage at MythFolklore.net. The feed on that page is what I call my "omnifeed," since it combines content from my blogs, plus my two Twitter accounts, and also my Google+ posts, thanks to Inoreader's great Twitter and Google+ integration. Whoo-hoo! :-)

Screencast!

Yep, I made a screencast; it is for our DML2015 presentation support site. Maybe it will be useful: Laura Loves RSS.


New Google Site: Teaching with Inoreader

Given interested by others in how I'm using Inoreader, I decided that it would be more productive to collection my Inoreader-related items at a website, rather than at a blog: Teaching With Inoreader. I'm excited about this because it will give me a chance to re-acquaint myself with Google Sites, too, so that I will do a better job of helping my students as they work on their own Google Sites. So, on this page, I will keep regular updates about what I am posting at the new website that specifically pertain to my classes.

Here are the new posts as of November 23, 2014:
  • Student Blogs and Comments. This explains how I set up the blog network by subscribing to student blog post feeds and comment feeds.
  • Archiving Assignments. There are a few assignments that I want to archive after the class is over; here's how I save an assignment archive as a PDF.
  • One-Time Fetch. The lack of updates for post content is the only real problem I had with Inoreader, but I found some good work-around solutions.
  • My Rookie Mistakes. Learn from my mistakes, so you don't have to learn from your own! :-)

Comment Wall

One of the biggest dilemmas I faced in switching from the Ning group blogging platform to Blogger was losing the great Ning Comment Wall feature. A simple solution — having students create a post called "Comment Wall" at their blogs — has turned out to work just fine! Not as good as Ning's Comment Wall... but definitely good enough!


BRIEF DESCRIPTION. Each student creates a simple post called "Comment Wall" in their blog which is easily accessible via the Comment Wall label. The post exists so that visitors to the blog can leave comments there. This is how students comment on each other's websites, and also how they leave thank-yous and other miscellaneous messages for each other. You can see how that works by looking at the Storybook listing for Myth-Folklore. As you can see, each Storybook has a link to the student's blog with Comment Wall. (For the Portfolio, since the writing consists of blog posts, students can just leave comments at those post although, interestingly, some students choose to do that at the Comment Wall instead and, of course, either way is fine!)


DETAILS.

Students do brainstorming and develop their Storybook projects during Weeks 1-5 of the semester, and then in Week 6, they begin commenting on each other's Storybooks. By that time, they have been leaving comments on each other's blogs for five weeks already, so they have become proficient at that, so the Comment Wall makes sense as a mode of communication. They receive feedback on their Storybook in this way for Weeks 6-12, which means every student should get around 10-15 comments total, and sometimes they get more if they are selected as a "free choice" in addition to the commenting group assignments.

I subscribe to the comment feeds for all my students' blogs, and I am really pleased by the quality of comments that are left both at the Comment Wall and also on the individual blog posts. Thanks to the power of Inoreader, you can see an HTML clippings view of the comment feels in my two classes. The Storybook comments are longer than the individual blog post comments as you'll see:
Myth-Folklore Comments
Indian Epics Comments


HISTORY.

For five years, I did all the student blogging in a Ning, and I used the wonderful "Comment Wall" on the Ning Profile page for students to leave comments for one another. That was the single best thing about the Ning: the Comment Wall really fostered CONVERSATION, in addition to comments, because it had a "reply" link with every comment, where you could create a threaded conversation back-and-forth between Comment Walls. Admittedly, though, students rarely took advantage of that option, and I suspect that was because the Ning had a strangely impersonal quality (see below) because of the generic design that did not allow individual customization.

In any case, I was very sorry to give that up that threaded conversation feature when I switched to the blogs, but I'm still pretty happy with how things have worked out: I use an Introduction blog post which serves much the same function as the old Profile Page did (I should write up an explanation of that also!), and the Comment Wall post solution has been working just fine.

One way in which this solution is superior to Ning is that when students visit another person's Comment Wall, they go in through the blog's main page, using the Comment Wall label to then click on to the Comment Wall. This means they get to see at a glance the person's latest posts, giving them an impression of what that person was doing for class over the past week. In the Ning, the Comment Wall was not integrated with the blog in that way and given how nicely the students are customizing their blogs to create a sense of personal presence, I really like the fact that to get to the Comment Wall you go through the blog home page.

Another factor that is contributing to the quality of interchange is how the students are in groups of three for their Storybook comments each week (new random groups each week). So, that means that they are both giving-and-getting comments to-and-from the people in the group. As a result, there is a sense of interchange that results from the round-robin strategy of using the groups. The comments are connected to one another in a kind of conversation among the group members each week.  Much of my approach here was driven by the QuadBlogging approach, along with a combination of randomization (so that everybody can meet everybody) and free choice (so that people can connect and reconnect based on shared interests).


GOALS. I consider student feedback on the Storybook to be one of the most crucial components of the class:

* Students have an audience for their work that is not just me.
* Students tend to provide holistic, personal feedback that is different from the feedback that I provide.
* Students learn how to provide feedback by practicing this skill every week while also receiving feedback each week from others.
* Students receive feedback in a timely fashion that allows them to improve their project week by week.
* Students can access all the project comments in a single place to review each time they spend time working on the project.


GENERAL THOUGHTS

The switch to Blogger which provoked me to use this "Comment Wall" post solution has been one of the best things that has ever happened in my classes. I had not realized what a negative effect the sameness of the Ning interface was having on the interactions: all the Ning blogs looked more or less the same (in a mini-Ning, students all had to use the same blog design), and all the comment walls looked more or less the same also. With Blogger, the sense of individual student presence and personality is so much stronger than it ever was before, which I think has given a big boost to the quality of the comments overall, with much more of a person-to-person dimension. I am very pleased with both the blog commenting and also the project comments at the Comment Walls!



Week 8: Review Week - Spring 15

The Week 8 Review Week went even better in the Spring 2015 semester with a more clear set of assignments, so I've updated this post to explain my current strategy.


BRIEF DESCRIPTION. There are two review weeks in my classes each semester: Week 8 and Week 15. The idea is to promote some self-reflection, looking both backward and forward, while also soliciting feedback and suggestions from the students — suggestions for me, and also suggestions for future students. The workload is also much lighter, saving the students two or three hours of time. We all need a break for humpweek, after all! The semester has a very nice symmetry now as a result: Orientation Week (Week 1), six reading weeks (Weeks 2-7), Review Week (Week 8), six more reading weeks (Weeks 9-14), and then a Final Review Week (Week 15).


DETAILS.

Instead of the usual Monday-Thursday assignments (reading, reading diary posts, and a storytelling post), the Week 8 review week has four very simple assignments: three are blog posts in which students review their progress in the course so far, and one is a blog check-up:

Monday: Reading Review.
Tuesday: Writing Review.
Wednesday: Commenting Review.
Thursday: Blog Label Check-Up.

I thought it was pretty cool how the class really does exist along these three dimension. I could have added a Technology Review post also, but I figured the blog label check-up was really essential, and three reflection posts are enough. I'll do a Technology Review post at the end of the semester, though, because it will fit nicely there, and the students don't need a blog check-up at that time.

Of course, these assignments can all be done at once, and some students did indeed do all of them at once, freeing up the rest of the week for other things. For most students the blog check-up required no real work at all, although it served a very useful purpose for students who either were having trouble with their blog labels and/or people who had missed the Comment Wall assignment earlier in the semester.

For the Friday-weekend blog responding, there were no new Storytelling posts in Week 8, so I modified that assignment slightly: instead of commenting on Storytelling posts from the current week, students responded to these Review posts in each other's blogs.


HISTORY. My Indian Epics class has always had review weeks because of the way the reading was structured, with the Ramayana taking six weeks (Weeks 2-7) and the Mahabharata taking six weeks (Weeks 9-14). I felt like the students really needed a break in that class, both in order to help with the transition from one epic to the next, and also because the reading load is significantly heavier than in Myth-Folklore. But then as I thought about making changes to the classes for Fall 2014 (this has been a semester of some huge changes!), I decided that having review weeks would be great in Myth-Folklore also. I am very pleased with how that has turned out, and I am especially happy with the assignments as they have evolved over the past two semesters.


GOALS. Each of the individual assignments has its own goals, but overall some goals for this Review Week are:
* to prompt students to reflect on their work during the first half of the semester
* to encourage students to plan and strategize for the second half of the semester
* to solicit feedback and suggestions for me to use and also for future students
* to give students a break with a lighter workload during "humpweek"


GENERAL THOUGHTS

I guess that when students see the word "review," the first word that pops into their minds would be: exam. And, of course, it does make sense to review for an exam. The more important role of review, however, is the role that it plays in any kind of learning experience. In my classes, I have no exams or tests, but I really believe in the value of review for learning. There are elements of reflection and review built into many of the class activities, and I am also really glad to have these review weeks in place for Weeks 8 and 15 also. I say "no" to exams... but I say "yes" to review!

For a graphic, here is something from David Kolb's model of experiential learning which I found in a wonderful post by Karen LaBonte: The Quest in the Quest-ions - reflecting is crucial!

The Portfolio Option

One of the biggest new experiments for me this semester is the Portfolio as an alternative to the Storybook, and now that Week 5 is over, I can report on how that is going since Week 5 is when the students made their choice!

Update: Week 10. I continue to be really pleased with how this option is working! One student decided to switch from her Storybook to the Portfolio option because she was so pressed for time, and that ended up being okay too. I was a little worried about how that would work since she was switching in Week 7, but she had so many good storytelling posts to choose from by that point in the semester that it has gone really well!


BRIEF DESCRIPTION. Each student completes a semester-long writing project, choosing to do either a Storybook (writing on a single topic) or a Portfolio (collecting their best weekly blog posts). You can see the schedule of assignments for both projects, along with information I provide to students about choosing between the Storybook or Portfolio.


DETAILS.

I have always required that the students do a semester-long writing project with a fully developed writing process: brainstorming, research, writing, revising... and revising some more. LOTS of revising. Since I started teaching these courses back in 2002, that project has taken the form of a Storybook, in which students choose a topic and come up with a storytelling plan that suits their topic. You can see an archive of past projects to see the results: Myth-Folklore and Indian Epics.

Starting in Fall 2014, I am offering an alternative project: instead of a Storybook, students can instead choose to compile a Portfolio of stories chosen from their weekly storytelling blog posts. This is similar to the Storybook in that it is based on writing and revising, but the stories are not connected to one another. Instead, they respond to the weekly readings in the class, using whatever style the student happened to have chosen that week for their storytelling experiment. So, just as for the Storybook stories, students will be turning in a new story to me every other week, and I will give them detailed comments back; they then revise the story, I read it again... and the it is time to add a new story to the Portfolio. At the end of the semester, the students will have a set of four or five stories labeled as "Portfolio" in their blog, accessible via the label link. To see how this is going to work, here is one student's Portfolio for Fall 2014 (one story so far).

So, as the semester begins, all the students explore past Storybooks and go through the brainstorming process for a Storybook, which culminates in writing an Introduction in Week 4. Then, they decide which way to go: carry on with the Storybook or opt for the Portfolio instead. The Storybook brainstorming is productive for its own sake, and it is also very helpful in preparing students for the kinds of writing they are doing in their Portfolio also, so in no sense is the time spent on early Storybook work lost time at all. In fact, one of the first Portfolio-related assignments I ask people to complete is to look at existing Storybooks to brainstorm about all the possible styles they might want to explore in their Portfolio over the course of the semester: Portfolio Brainstorm.

I'll surely have more to say about the Portfolio project as the semester goes on, but my verdict after the first week of Portfolio assignments is that it was a big success. I read and replied to all the Portfolio stories, and next week those will be coming back in as revisions, while students will also be getting feedback from other students this weekend, just as for the Storybooks. I'm really excited about that! In the old system, the students who were struggling and/or behind on the Storybook did not get any feedback from other students until their Storybook was actually online and ready to read. Sometimes that meant they were out of the student feedback loop until Week 6 or even Week 7. Now, with the Portfolio, they are going to be part of the give-and-get of student feedback this weekend, along with everybody else.

I'm so happy how this has gone so far, and I'll report back again later in the semester!


HISTORY.

I had been troubled by the fact that every semester 1 or 2 students abandoned their Storybook projects before the end of the semester. It was never more than 1 or 2, but it was a persistent problem. Not every semester, but almost every semester, at least 1 or 2 Storybooks never got finished, and I felt badly about that, since the experience was surely not very satisfying for the student. It also made me wonder, of course, just how many Storybooks students were finishing because they "had to" and not really because they wanted to.

So, this had been simmering on the back burner, but it was never really a big enough problem that I devoted a lot of thought to it specifically; I had other, bigger problems to work on, ha ha. But then, one day last spring, I had a BRAINWAVE. I can date it specifically to March 29 as I learn from this old Google+ post. It was kind of eerie to read that post now and realize that the idea was kind of a "birth of Athena" thing, because what I ended up doing is almost exactly what I figured out in that moment of revelation back in March. Freaky!

And here's how it turned out this Fall! In the Myth-Folklore class, the first time this option was offered, 7 students chose the Portfolio out of 48 students total. In the Indian Epics class, 7 students chose the Portfolio out of 32 students total. I really did not know what to expect, but I knew there would be more takers in Indian Epics because the reading load in that class is more demanding than in Myth-Folklore, so the students are pressed for time, and it's also the case that finding a topic for Indian Epics is more challenging, especially when Indian culture may be something completely new to the students, as it often is. So, that means 14 students out of 80 overall chose the Portfolio. I will try to remember to update this post every semester so that I can keep track of this over time!


GOALS. Since the semester-long projects are really the heart-and-soul of my classes, it's hard to list just a few goals; I have so many goals here. So, please look at the goals that I have listed for the Storybooks: TEACHING WRITERS. All those goals hold true for the Portfolios too, and I've reproduced that "teaching writers" graphic below.

As a special subset of goals, here is what I hope to achieve by offering the Portfolio specifically as an ALTERNATIVE to the Storybook:

  • Choice. Give students a wider range of semester-long project options.
  • Time Management. Help students who are facing serious demands on their time.
  • Blogging. Provide students the chance to develop a "curated" section of their blog, featuring their best posts.


GENERAL THOUGHTS

I am glad that there are enough Portfolios in both classes that it is not going to be seen as stigmatizing in any way, although I am still worried about that. I am hoping to gather some testimonials from the students at the end of this semester about whether they are glad or not about having chosen the Portfolio. I think their testimonies could be very useful in helping students decide to opt for the Portfolio. I really think BOTH options are excellent, and I am delighted by both writing projects. If all goes well, the students doing Portfolios will have a good experience with that, and I can find a way to share that positive evaluation with next semester's students so that people will see that the Portfolio is a great option, one that every student might want to consider!

In particular, I was glad to see that some students who are strong writers DID choose the Portfolio option. I suspect they did so because they are feeling overwhelmed by their many obligations, so it just makes sense for them to choose the option that lets them build on the existing stories in their blog, rather than writing additional stories. So, as students read the Storybooks and the Portfolios, they will see strong writing in both types of projects, along with less strong writing, since in every class there is an incredibly wide range of writerly experience, writerly interest, etc. Luckily, though, it is not going to be the case that students will be associating the stronger writing with the Storybooks. There is a range of writing to be found in both types of projects and, of course, with the revising, both the Storybook stories and the Portfolio stories will get better and better, week by week, all semester long!



(thanks to Larry Ferlazzo for the graphic)

Weekly Blog Comments

The blog commenting assignment is an important part of each week's activity. My goal is for each student to get one or two comments on their storytelling post each week. I can't guarantee that with 100% certainty, but I am pretty happy with how this assignment is working.


BRIEF DESCRIPTION. Each week, (most) students publish a storytelling blog post on or by Wednesday. On Thursday, I put the students who have published the storytelling post in random groups of three. On Friday, that assignment becomes available and lasts over the weekend: students respond to the other two students in their group.


DETAILS. One of the tricky things with a self-scheduled course is finding ways for students to interact with each other about the work they are doing. In addition, not everybody does every blog assignment each week, and not everybody does blog commenting each week, but I still want to make sure that everybody gets at least one comment, and hopefully two, on their storytelling blog post. I also want to help students get to know each other, so I ask them to comment on each other's Introduction post as well; if they already know the person (and thus commented on the Introduction post previously), they can choose another post in that familiar person's blog to respond to.

Here's how I make that work:
  1. After the Wednesday grace period ends at Thursday noon, I can see which students have done the storytelling blog post; usually there are two or three students in each class who have not done that post (which is fine — they can make that up with extra credit later on).
  2. I copy the list of links to student blog addresses (raw HTML) into a text file, each blog address on a separate line. Then I delete the students who did not do the storytelling post.
  3. Next, I paste the remaining blog addresses into a randomizer.
  4. I then divide up the randomized links into groups of three and paste them into the page that the students see here: Blog Responding.
  5. I then copy the plain text (names only) into a text file, copy the group numbers after the names, and sort alphabetically to create the group index.
  6. If there is a group with two people instead of three, I just add "choose at random" to that group. If there is a group with only one person, I move a person from another group, and then add "choose from group (whatever)" so that the students in those two groups are responding to each other.
That sounds complicated, but it only takes about 10 minutes per class. I then update the main page of instructions, letting students know the assignment is available starting on Friday through the weekend: Blog Responding.

Just as there are two or three people who don't do the storytelling post each week, there are usually two or three people who don't do the responding. Overall, though, most people do get two comments on their storytelling (plus their Introduction or some other post), and everybody gets one comment. For extra credit, students can choose to comment on additional stories, so that increases the overall amount of commenting that goes on each week (those extra credit comments are free choice). This is not a perfect system, but in terms of overall effectiveness, flexibility for the students, and ease of preparation for me, it works pretty well!


HISTORY. For years, I tried to keep the groups stable over a period of three weeks. That just didn't work, though, because of the students who either didn't do a story in a given week. So, I finally decided to randomize the groups every week, while also having a comment on the Introduction be part of the assignment in order to give a sense of connection even when the groups are random each week.


GOALS. This is a really important assignment for all kinds of reasons!
  • Get Feedback. Students give each other great feedback, and the feedback they give each other is often different from the kind of feedback they get from me.
  • Learn to Give Feedback. In the process of getting feedback, students also learn about giving feedback and can hone their feedback skills.
  • Discover Ideas and Inspiration. By reading other students' writing, students can discover ideas and inspiration that they can use to improve their own writing.
  • Building Community. This weekly assignment (along with the Storybook feedback in Weeks 6-12) is a way of building a sense of community in the class.

GENERAL THOUGHTS

I feel really lucky that the students do a great job of commenting on each other's blogs: they are very enthusiastic and offer lots of detail and personal observation. I try to create a positive climate of blog commenting with the comments that I leave on the Favorite Places posts and the Introduction posts from the first week so that when the students start commenting on each other's posts they will do a good job with that. In a separate entry here, I need to explain how I use Feedly to keep an eye on the commenting, just to make sure everything is going well — and it does!

Students regularly comment in the end of semester evaluations how much they like interacting with other students, getting feedback, and sharing ideas online like this. This type of interaction is admittedly different from a regular classroom-based class, and I would argue that this difference is a good thing. I won't contend that the interaction online is better or worse, just that it is a different, and that this difference is a positive value in and of itself. Who knows what kind of non-face-to-face communication students may need to use in their 21st-century careers? I hope that the online interactions in my classes can help prepare them for whatever may come!



Inoreader: Keeping Up With All Those Blogs!

It was my great good fortune to learn about Inoreader right at the beginning of the semester; it's made working with the student blogs so much more fun than ever before. I'll be making changes to my course for Spring semester so that I can make even better use of that tool. Meanwhile, in this post, I'll start explaining how I am using Inoreader in my classes for Fall 2014.

BRIEF DESCRIPTION. Inoreader is an RSS reader with some very powerful features that allow me to keep up with hundreds of student blog posts each week. In particular, I am making use of the rules, tags, multiple display views, and HTML clippings. Rules are a "Plus" premium feature ($30/year), but all the other features are part of the free version.

DETAILS. I am doing some powerful things with Inoreader, but at the same time it is very simple to use. Here's how I got up and running:

1. Add Blogs. As the students create their blogs, I grab the RSS to add the feeds to Inoreader, with each class in a separate folder. OU IE is my Indian Epics class; OU MF is my Myth-Folklore class. As you can see, this gives me easy access to each student's blog when I am interested in looking at a given student's blog as opposed to looking at a collection of blog posts for a given assignment.



2. Create Rules. I set up rules to tag the incoming posts based on keywords in the subject lines. So, for example, storytelling posts in my Myth-Folklore class are tagged storytellingmf, and the HTML clippings feature lets me share posts with that tag.


3. Scan Incoming. I also have a rule to tag all incoming posts as "Incoming" which is just a temporary tag. Periodically throughout the day, I scan the posts labeled "Incoming," taking a quick look at the post, adjusting the tags as needed (sometimes students don't put the keywords in the subject lines), and removing the Incoming tag as I go along. This takes just a few minutes each day. I sometimes leave a comment for the student right then; sometimes I add a tag to remind myself to come back and check something, etc. It all depends on how much time I have! Here's what the tag area looks like - the autocomplete means that when I do need to add tags, it prompts me to be consistent with the tags I'm already using:


And that's all, folks! For those of you who are users of rules and tags to organize your email, Inoreader is allowing me to use exactly the same organizational strategies. At the same time, it provides powerful sharing opportunities because each tag has its own RSS feed and its own HTML clippings service.

In other posts, I'll explain more specifically some of the ways Inoreader is helping me with each of the different types of assignments which the students are publishing in their blogs. Just how I interact with the students' blogs and how the students interact with each other varies from assignment to assignment, and Inoreader is helping provide access, both for me and for the students, to the different assignment types.

HISTORY. I started out years ago using Bloglines for student blogs, and then for five years I used Ning, a group blogging platform; you can read more about that history here. As far as RSS readers go, I was a loyal fan of Google Reader, and I made good use of "bundles" then. I switched to Feedly when Google shut down Reader, but I missed my bundles! I put out a plea for help at Google+ when I realized how badly I needed something like Google Reader to manage all these new student blogs, and Stefan Heßbrüggen recommended Inoreader. I am lucky to be connected to so many smart folks online; Inoreader was exactly what I was looking for.

GOALS. These are the main goals that Inoreader is helping me with:
  • Blog awareness. I am able to skim and scan, getting a good sense of all the blog posts as they come in.
  • Blog organization. I can review the different types of blog posts systematically, learning from the posts, commenting, and also re-using them.
  • Blog sharing. Being able to share the blog posts so that the students can get ideas and inspirations from each other is the best thing of all!

GENERAL THOUGHTS

For years I have been a wild admirer of ds106 and the aggregation/syndication tools that Alan Levine has been developing for WordPress environments. At the same time, I know that I am just not up for that technological adventure; I am a happy creator of web content, and thus an uber-nerd, but not much of a geek. I use hosted services like Blogger and PBWorks, and I am a big fan of javascript tools (like RotateContent.com) that let me embed and syndicate that hosted content. For my courses, though, without Google Reader's bundles, I was stumped. Inoreader came to the rescue! Although I am not able to work all the ds106 magic, it has let me come closer than I had ever dreamed possible without running my own WordPress installation.

One thing I like about my admittedly lazy use of hosted options is that it means I can share my strategies with everyone! Anything that I am doing in my courses, my students can turn around and do too, and I can recommend my strategies to anyone with an Internet connection and some time to play around with these hosted tools and services.

Of course, I know that no hosted service will last forever, and in the past ten years, I've seen services come and go, including dearly beloved services like Delicious and Google Reader. But I've also come to learn that sometimes the demise of a beloved service is what galvanizes change, in a good way. It was the demise of Delicious that prompted me to create my eStorybook Central archive of student work, for example, whereas before I had done that with Delicious; eStorybook Central has turned out to be much more useful to me as a project archive than Delicious ever was! Likewise, the end of Ning threw me into a bit of a panic, but it has provoked the biggest and best changes that I've ever made to my courses.

Of course, at the moment I am hoping that Inoreader sticks around for a very, very long time — and I can tell there are still lots of Inoreader tricks I have yet to learn. I am so excited about tweaking my assignments next semester in order to take full advantage of Inoreader's powerful help!