Here is a list of some of my favorite Facebook Apps:
FriendFeed: Allows me to publish my life stream on my Facebook profile
Boost: Boost is a Firefox add on that allows you to change the look and feel of Facebook. Adds a bunch of cool functionality like “download whole album” and showing full size images when you mouse over them.
Nexus: Creates a graph of your network. Really interesting to see how you are connected to other people and how connected they are to your friends.
FBcal: Generates an iCal file of your upcoming Facebook events and/or upcoming birthdays. Seeing as my Google Calendar plans my life, I don’t know how I’ve lived without this application for so long!
so here is a mapping of my plan for a UBC content management strategy. It is designed to overcome two obstacles:
1) Content changes, therefore the content stored in repositories has to change and be updated when the source is updated. This is overcome by using a wiki (this has been Novak’s vision of content management for a while) that produces RSS feeds along with an aggregator like Feed WordPress that updates the repository when a feed gets updated (that feature is still buggy at the moment, but I will get to fixing that ASAP).
So here is what it looks like (click on it for larger view):
So it’s 4:30 in the morning and I am nowhere near ready to go to bed. So instead I did the final quality testing for my “add user widget” WordPress Mu plugin.
This plugin eliminates the question that I’ve been asked plenty of times “what if a student who is not in the class adds themselves to a course blog?”. I think the answer is simple (and I think Jim and Brian would agree with me)… just delete and/or ban the user. However, in order to eliminate this barrier on implementing course blogs I modified the plugin to allow professors to enter a list of student emails. If the student’s email is in the list they can then add themselves to the list. This means that in conjunction with my Add to BDP RSS widget that Professors or institutions can decide whether anyone can add themselves, subscribers to the WordPress Mu system or only users that are in a specific list. This will now work for all three of the course blog types that I created.
This plugin is a modification of sidebar add user widget by DSader. It adds a whole bunch of control functionality that allows admin to change who is allowed to add themselves to a blog and also what type of permission is allowed. It also changes the way that the widget appears depending on the user’s status. It was developed primarily for course blogs.
Final, final update:
WordPress. org has started to show OLT some love and we are now rapidly publishing all of our plugins there. The new direct link to download sidebar add user widget is here and the plugin page is here.
Now that OLT has a place to house its plugins I will no longer be maintaining add user widget on this site. Instead it will live on blogs.ubc.ca. The direct link is here.
Fixed the problem with the plugin not reloading user’s status when they first add themselves.
Changed the way restricting users works. Now the admin can simply set a password in the widget control menu and users who know the password can add themselves to the blog.
Just drop into the mu-plugins folder.
Any problems/suggestions just leave a comment
This was supposed to be a long and intense post, blending many different discussions that I’ve had over the past week, but I don’t have time and since I just got my new WordPress site, I need to write! (I’ll get the rest of it up some other time).
Here is the Jist of it:
I have spoken to so many people who tell me that “Facebook is creepy”. One of the biggest taboos here is to say “oh, I saw it on your mini-feed”. People get all weirded out as if they didn’t know that one of the key reasons of Facebook’s success is the fact that it is so good at distributing your information to those who know you.
Jocelyn and Ciara (my resident Facebook experts) were lamenting that fact with me and we came up with the idea that maybe the problem is just the language that has evolved around Facebook. We put information on Facebook for people to see. We have complete control over who can see that information. It’s like creating a poster about yourself. It isn’t creepy looking at someone’s poster. Jocelyn and Ciara came up with some alternative names. They suggested something like “exploring” or “learning”. I think of it as “researching your personal social network”. Someone reading your profile is a good thing… it helps them to know you better. Someone reading your wall-to-wall with someone else is also a good thing. It’s flattering. Someone cares enough to read about you. If there is something that you don’t want people to read about you… you shouldn’t publish it and if you have to tell somebody something private… that’s what private messages are for.
I am technically a “mentor” for the UBC Blog Squad. Although I haven’t done much mentoring. In fact they pretty much school me in dedication and writing ability. Many of them have written some absolutely fantastic stuff.
So here goes, my attempt at a bit of helping out:
I’ve noticed that many of you haven’t changed your blogroll yet (although I see that Genevieve has added a bunch of things to her one). Your blogroll can really complement your blog, by telling people at a glance what you are interested in. It shows people what you are reading and gives background for your own writing. It also doesn’t have to simply be one long list. If you go to the “blogroll” tab in WordPress you will see that you can add categories.
You can then add specific blogs to each category. Here is a quick example of what this would look like:
There is also a link at the bottom of the “add to blogroll” section that you can drag into your browser so that when you see a site that you really like you can add it to your blogroll very quickly.
P.S. My actual blogroll is a terrible example. Seeing as I am not using WordPress at the moment changing it is a lot harder for me to do than for all of you!
So here they are, examples of the three kinds of blogs that I outlined in this post, as well as explanations for how to create them within WordPress MU. Jon has kindly let me use his Spanish 312 class as and example, so some of my examples are actually fully populated and active courses. (click on the headings to see the actual blogs)
This blog uses BDPRSS to output the content of an aggregated feed of the class. I created a widget to add to the list in BDPRSS so students can auto-populate themselves into the course. The other feature that I developed for this blog is an auto-populating class list (with the heading our class). The class list is the reason that I took so long to get these examples up and running. I spent a good chunk of this week working on an “add to blogroll” widget so that students could add links to their blogs in the sidebar. I tried many methods, but just couldn’t get the plugin to work. Gardner Campbell was paying a visit to UBC and while he was showing me some of the successes and issues that he has been having with his course blog Rock soul Progressive I saw that he was using the BDP RSS widget to display comments. A light bulb went on and I realized that I could simply tweak the widget to show a list of blogs in the course. Here is what you have to do:
- Create and output format in BDP RSS that contains the same blogs as the one that is being used to display entries in the course.
- In the “output format types” section select the radio button that says “list by sites alphabetically”
- In “about the items” set “maximum items per site” to 1, check “print site names” and “only display item’s title”. Uncheck “print the item’s age”
in the “XHTML formatting” section, add list tags around “title for each site” and comment tags around “each item’s title”. (see picture )
If you add the BDP RSS widget for the output to the sidebar then you create a class list.
This blog uses a spamblogger (I’m using feedWordPress because it actually updates posts if they are changed in the original feed) combined with BDP RSS to quickly create the course. Basically what happens is a feed aggregated by BDP RSS is fed into the spamblogger and feedWordPress republishes it. I have three reasons why I run the feeds through BDP RSS before I feed them to the feedWordPress:
- I’ve already created my Add to BDPRSS widget to add feeds to BDPRSS. If I wanted students to add their own feeds to the spamblogger I would have to create another widget (and the widget would have to be specific to the spamblogger).
- BDP works really well with a large range of feeds as well as with a large number of feeds. It acts as a kind of normalizing process, ensuring that each entry is parsed in the same way.
- It allows for the auto-generation of a class list as described for the ghost course blog.
This Blog is the simplest to set up and is probably closer to what most faculty members will imagine when they think of a course blog. I simply use the sidebar add user widget to add authors and the Wp-Authors widget to display the class list. Quick and simple. My example isn’t as good as the others simply because all of the content had to be written from scratch (or copy pasted from Wikipedia). K1, one of the work study students at OLT was kind enough to post a few items under different authors to show how this kind of course blog would look.
A fourth option is of course mashing the Spam Course Blog and the Communal Course blog together, thus giving students the option over whether or not they want to have their own course.
If there is anything that I am missing in my thinking here, please let me know.
Some notes on policy and where I’m going from here: As I have been making these ways for students to self-populate a course, the question keeps on coming up “what if people who don’t belong to the course add themselves”? At the moment the sidebar add to BDP widget gives three levels of permission, global (anyone), system (on the same MU system) and blog (subscribers to the blog). I will be working on changing the “add user” plugin to accept a list of people (I’m thinking student numbers or emails?) and check those against people who are trying to add themselves to a blog. This would mean that a professor could just paste a list in the control of the widget and not have to worry about people who are not in the class adding themselves. Then to close off the spam and ghost course blogs one would set the sidebar add to bdp widget permissions to “blog” and display the add user widget forcing students to add themselves as subscribers to the blog first so that they can be checked off against the class list before adding their feed.
Here is my first WordPress plugin. It is meant to extend the excellent BDP-RSS plugin by Bryan Palmer. This plugin allows users who are logged in to a WordPress MU system to add feeds to the BDP-RSS feed aggregator from the sidebar. It is primarily designed to allow students to add the feed of their own blog to a class aggregate blog.
Please let me know what you think.
Just download, unzip, then drop the plugin into your plugins->BDPRSS folder and activate in the plugins menu.
Update: For some reason the control is not saving the options properly. I’ll fix it on Saturday morning.
Update: Version 1.2 released.
Changed the way that permissions work.
- Simplified things by only allowing registers users of the community to add their feeds.
- Gave admin the option of password protecting a blog so that only users who know the password can add feeds
As always, let me know what you think of the changed.
Update: Version 1.1 released.
- Fixed subtitle bug
- Added control over what type of user can add feeds.
- Global: Anyone can add a feed
- System: Anyone on the Mu System can add a feed.
- Blog: Only a subscriber to the specific blog that the widget is on can add a feed.
- Made it so that if a user cannot add a feed, they don’t even see the text box.
In a comment on my post “who owns a class blog“ Jim Groom said:
That is the rub, when you open up a system like this, there are a number of ways of going at it, and having the ability to meet as many of them easily makes your life simpler.
I agree whole-heartedly with Jim. My judgment has been clouded lately by the Wp-o-matic’s ability lack of to update posts on the fly and the lack of a “delete all” button on any of WordPress’ pages. Today though, I saw the light. I now have a clear vision of three simple, definable, student driven course blog structures.
The ghost blog:
This blog is for the professor who doesn’t want to be confused by hundreds of student posts knocking around his/her blog. The blog simply uses BDPRSS and my add-to-BDPRSS widget (source code coming soon I promise) to populate a WordPress page with aggregated student entries. When another year of students comes, the old posts will still be there (or not, or in another blog that that the new blog links to), but as newer posts come in, the old posts will fall off of the bottom of the feed and the blog will have just new fresh content. No having to delete anything!
The Communal blog:
This blog is for the professor who wants to get stuck into the blogging experience with the students. This also probably the easiest (although I used to think it was the hardest) to implement. Jim reminded me of the “Add Sidebar Users” widget, which I will tweak slightly to make setting up this kind of blog super easy. Our new blogging service will allow students to sign up as just subscribers if they want to and with Campus Wide Login they won’t even have to remember their username. Zero work for the professor!
The spam blog:
Jim did great things with WP-o-matic. I found a tool that works even better for what we want to do (in fact, it is the one thing that I can now do better than the current incarnation of eduglu). FeedWordPress by Charles Johnson is another spamblogger that updates entries if they change in the feed. The biggest problem that I had with other versions of spam blogging tools was that they took dynamic content, republished it and then made it static. This might work for blog posts (which don’t generally change very much after they have been written)… but for something like a course syllabus or wiki feed (I’ll save that discussion for a later day) the content in the repository has to be continually updated. Otherwise we just have old junk entries lying around. FeedWordPress fixes that. FeedWordPress also has a nice “delete all” button that will get rid of feed entries that are marked for deletion. Best of all, the author has provided an excellent API and a bunch of hooks so that I can massage this plugin into doing my complete bidding.
I will be finalizing and testing these methods tomorrow and over the weekend and will hopefully have some concrete examples by early next week.
One last thing. These structures do not have to be independent. the communal blog can be combined with the spam blog (giving students the option). A ghost page can then be created in a different tab, feeding in content from other sources as examples and even points of discussion for future posts by the students. A ghost blog can be archived by simply feeding it into a spam blog and so on.