Saying Goodbye to Blackboard Part II – Student Blogs & Privacy
In my first post I explained how I am using WordPress as a course management system, and in this post I will explain how I was able to easily add students to the class and set up their blogs. Keep in mind that my new course network is completely private, so only registered users can see who users are and participate in activities. To achieve this privacy, I installed a plug-in called Private WordPress. “Private WP will make sure people can only read your blog after they log in. Already logged in users will see no difference. Users who are logged out will get the login page, and only that.” I like to keep my options open, so although we are completely private, I still set up the students so they can have an option to use an alias.
First I added every student as a user to the main “hub” blog using their MEID and their Maricopa email address. This information is easily accessible in both Blackboard and SIS so I can do this before the semester begins. After I add them to the network, students are sent an email with log in instructions and a password to access the site. When they log-in they are instructed to edit their profiles to add their real name and a photo. At this point they can choose to display their first name only, first and last name or just their MEID. They can also use a chosen alias instead of their real names if they want. Students cannot change the initial username given (MEID), so no matter what they provide for their names, I can always identify them on the back end by the MEID. So far, all of my students have chosen to use their real names or stick with the MEID as the display name.
Next I create a blog or site for each user. You are given the choice between sub-domains or sub-directories in Step 4: Installing a Network. This means each additional site in your network will be created as a new virtual subdomain or subdirectory.
- Sub-domains — like
- Sub-directories — like
I wanted to try them both, so ENG101 uses sub-domains and ENG102 and ENH295 both use sub-directories. I think I like sub-directories better so. To add a site I need a site name, site title and an admin email. For the site name I used MEIDs again because they will be easily identifiable by me, and if students neglect to make their site private, they are not automatically identifiable to the world. For site title I use the student’s first name temporarily, and then I add their Maricopa email for the admin email. Once I add the site, students are sent another email with log in instructions. They are then instructed to either leave their blogs public or make them private by using the same plug-in I used on the main site. If they choose to go private, I instruct them to choose the option to “Allow all feed access - Guests may continue read your blog via feed readers. “ This is essentially the same option we would have in Blackboard if our district had the balls to turn it on. The blogs are not accessible by search engines, and you have to have the feed url in order to see the posts. So it’s still private, but I can still access it via a feed reader. This makes me very happy.
Students are also instructed that they can change the title of their blog to whatever they want, thus removing their names. So they can change Mary’s blog (default) to MJ’s Hangout if they want. I don’t really need to have their name in the title because when I set up the blogs initially I created a blogroll for each class using their real name and subscribed to each blog using the real name. This blogroll list is only viewable by logged in users from the main site, and my Google Reader list is private as well. When I want to grade Mary’s blog, I either click on her real name or visit my GReader. And if I ever get confused I can just look at the URL: http://eng102online.com/mar1234567 (fake) and the MEID on the end will identify the student. My initial impression is that either students don’t care about privacy or they’re too confused to care. Not one student has changed the name of their blog, and I haven’t check to see if any have gone private. I’ll do that soon.
Students have most of the same controls over their blogs that I have over mine. When I add and install plug-ins to the main blog, I have the option to activate site wide meaning students will now have access to the plug-in on their site. I can even control what themes are available to students, so if I want for their blogs to all look the same, I could just provide the one option. Or in the future I like to create a custom theme built just for writing portfolios for my ENG101 class. I could have all the pages prebuilt to make it easier for students. It can be a little confusing at first for students because they have two sites, the main class site (hub) and their own blog. When they click from the main site to go the dashboard, they end up first in the main site’s dashboard and there is not much there. They have to then click on the My Sites to see their blog and to be able to get to that dashboard.
Students cannot add themes or plug-ins to their site on their own. They can only activate themes or plug-ins that you have activated sitewide. The only problem that I can see so far is with the spam filter Akismet. I activated it sitewide so that all the student blogs could be protected, but it prompts all students to add their API key that you get by signing up for WordPress.com. I didn’t want to have students go through all of that, so at the moment all their blogs are exposed to spam. I like how the Private WordPress plug-in reminds students to activate privacy on their blog in case they missed my instructions to do so.
Overall, I’m pleased with how it’s all working out. I created lots of screencasts to help students, and I haven’t had too many questions about how to do things. I haven’t had too many complaints yet either. Only time will tell. In my next post I’ll talk more about how I’m collecting assignments and doling out quizzes and grades.