Digital Marginalia

A collection of links, notes, and things I’ve seen in the last little while that are too long for a tweet but too short for a full blog post unto themselves…

First, and most importantly to me, the soundtrack to this update the brilliant 13th Floor Elevators (and particularly, Roky Erikson’s great solo version of Two Headed Dog):

I updated my laptop to Windows 10 – I primarily use the laptop for checking e-mail, writing more than a tweet, constructing a drum beat or using Word 2007. The process was smooth for a laptop that’s close to 6 years old and has 4 gig RAM and 320 gig hard drive. However, here’s a series of Windows 10 related links that will be of benefit to those who wish to better understand what this upgrade means. The first outlines the new features of the OS. The second has to do with blocking auto-updates. The third has to do with privacy settings, which we all should be interested in.

http://fieldguide.gizmodo.com/14-things-you-can-do-in-windows-10-that-you-couldnt-do-1721271379

http://www.slashgear.com/microsoft-has-a-tool-for-blocking-windows-10-auto-updates-27394432/

http://lifehacker.com/what-windows-10s-privacy-nightmare-settings-actually-1722267229

I’ve been working off and on over the summer with our student centre trying to think of ways badging could work as a co-curricular record for students. I don’t know that we’re much further, but we are going to try some things over the next year and see how they work. I’m interested in ways that we can empower students to grant badges to other students, especially when those badges might contain institutional imagery. How can we ensure that people don’t misunderstand what the badge means and that it’s a peer issued badge? Lots and lots of stuff to unpack there.

http://chromatrope.co.uk/open-badges-for-training-and-development-2/

http://www.dontwasteyourtime.co.uk/technology/mapping-digital-skills-in-he/

http://huxleypiguk.blogspot.co.uk/2015/07/free-open-badge-e-book.html

http://higheredstrategy.com/wp-content/uploads/2014/08/Intelligence-Brief-9-Career-Services-Offices-3.pdf

http://literaci.es/privacy-badges

While in training this week, Carpe Diem learning design was mentioned. I didn’t inquire further, but I did some looking further into it. It strikes me as neat, but prone to my faulty brain labelling it Caveat Emptor learning design, which has a whole separate implication. I would recommend not using Caveat Emptor learning design, if it exists.

http://www.ld-grid.org/resources/methods-and-methodologies/carpe-diem

I didn’t go to Brightspace Fusion/User Conference this year because a) I hate Orlando, and b) the hotel was not within public transportation/walking distance of anything nearby. I did however have my twitter feed blow up for a couple hours when I got mentioned by my good friend Barry. I’m actually speechless about this still (almost two months later!) – it’s honoring and humbling to have others say such nice things about me.  Thank you to you all.

Badging

I’ve been involved, somewhat peripherally, with the Open Badging Initiative for the last six months or so. Initially, it was a way to start thinking about breaking the LMS (Integrated Learning Platform? aw, screw it, I don’t know what the thing is called anymore) out of the box it’s in and communicating what the LMS does well with other parties. I thought it could be a way to communicate skills, think about developing a short-hand language through the badge to communicate with other people. It’s really a way to check all the boxes that get me excited currently. Open standards? Yep. Mutating a system to do something other than what was intended? Yep. Visual design an image that communicates a value to another party? Yep. Explore the value of a systematic education? Yep.

The problem is that I essentially stopped programming in 2004 when I really didn’t need it anymore. Sure I’ve done a few things like hack together a PERL script to parse out values in a text file, and dump it into a database, but using badges at this point, or at least at my institution, I need to get up to speed with programming and handling JSON, XML if I’m going to start tinkering with our LMS and implementing badges. Ouch. Thankfully, I’ve got a few friends and colleagues who’ll help me get there.

For those of you who don’t know, badging is a way of giving value to something by awarding an image that represents that value. At it’s simplest, it works like the Scouts – demonstrate something and get a badge for demonstrating that you know something. It’s basically the same proposition as what grades are in higher education. The neat thing is that the badge doesn’t have to be tied to a number that’s arbitrarily set by someone (a teacher) or something (a computer, schooling system…). It can be tied to evidence or not, depending on the issuer of the badge and what they demand for getting the badge. That’s where badging is cool for me.

When you earn a badge that conforms to the Open Badges Standard, it can be pushed to your backpack. This is the central repository of badges for you. I’ve embedded below a portion of my backpack for you to see how one might display achievements.

What makes badges a little better than a grade value is the evidence of learning which is listed as part of the criteria. Now in many cases this is not as transparent as it should be. For instance, I’ve been working through CodeSchool’s Javascript introduction and JQuery courses that issue badges. Their criteria is displaying on a page that “confirms” I completed a module. Wouldn’t this page be much better if it shared exactly what I did to earn the badge? That would be powerful. I realize that there’s all sorts of considerations for student privacy, and ideally they would be able to control what is shared with the badge (maybe an on/off switch with each badge issuer to allow for a simple description of what earned the badge or a more detailed results page). That might lead to badges being more than a symbol of learning that doesn’t communicate clearly to the viewer what was learned.