Last weekend, I took part in the Pedagoo event #tmlovelibraries. It was a fantastic day, and I learned loads. At the pub session afterwards, there was a sort of TeachMeet Unplugged event, similar in feel to the TeachMeet 365 events or, as Fearghal testified, to the very early TeachMeets themselves. Fearghal had asked us all to come with something we were prepared to share; as I have been doing a bit of work with OpenBadges and have been very impressed with them, I decided that this was what I was going to talk about.
Then I hit the problem. 2 minutes is not a very long time, particularly to talk about something you have been working on for months and have found out so much about. So, to keep things short, I decided to create an OpenBadge for all the participants of tmlovelibraries and then give it to them as a present. By claiming it, they could find out a bit about Openbadges themselves.
This idea seemed to work well in the keeping things short arena, as well as the engaging the audience area – the word ‘gift’ seemed to be the important one in achieving this! As Fearghal commented on the night, my talk also had the effect of taking his carefully honed structure and blasting it into a million pieces as people went scurrying to the internet to find their badge. The badge is shown below, together with its claim code for anyone who was there. To claim it, navigate to the badg.us site and insert the claim code ‘kapyua’ into the “Claim award from code” box. This will prompt you to either sign in to your Mozilla Backpack if you already have one, or sign up with an email address to create one before awarding you the tmlovelibraries – Participant badge, which you can then display on your blog, Facebook profile or Twitter feed.
In the impromptu break that followed my talk, I was talking to a few different people, and realised that there was a real appetite for finding out more about using OpenBadges. Quite a few people had looked at the concept themselves, before deciding that the project was too technical for them to use effectively. This, of course, is exactly the same decision I came to myself when I first started looking into digital badges. I had been impressed with the ease of creating badges for recognising various achievements on Edmodo, but had hoped for some way to display them in fronter, our school’s virtual learning environment. When I had approached the extremely helpful people at Edmodo asking if this was possible, they said that whilst they were happy for the badges to be displayed elsewhere, but it would need to be purely a case of copying them as an image and uploading them elsewhere.
I felt sure that there had to be a more efficient way of doing this, and went off doing a bit of digital badge research. It soon became clear that OpenBadges were exactly what I was looking for, but despite the fact that there were plentiful resources available for those with an ability to code, there was nothing I could find that was very user-friendly for a class teacher.
Until I chanced across the ForAllBadges site that is. Straight from the off, ForAllBadges allowed me to create an OpenBadge simply by uploading an image to the site and filling in the information fields to attach to it. Perfect for what I wanted. But ForAllBadges had far more to offer than I had been looking for. It gave me a whole badge-management system, allowing me to upload classes and add staff, create and issue badges and – most crucially given the age of my pupils – a way to display the badges earned without needing a Mozilla Backpack (currently, a Mozilla Backpack is only available to learners over the age of 13).
I soon had a pilot badge system up and running and a fronter page created with links to the pupil’s individual Trophy Rooms; here their badges could be seen through viewing their ForAllBadges badge journal. After an email exchange with the amazing people at ForAllBadges, the ability for the student to add a reflective comment to their badge journal was quickly added. This setup now allowed for a badge to be created, issued, displayed and reflected upon as well as having the advantage of being part of the OpenBadge system allowing a great degree of portability for the badges once the pupil reaches the age of 13 (or Mozilla update their terms & conditions to allow under 13s to have a Backpack with permission from their parent/carer – a change that is on the cards very soon I believe).
This was perfect for what I was looking to use it for in school, but perhaps a bit too complicated to use in ‘open play’. I had been thinking that OpenBadges could be a great way to document CPD activities such as TeachMeets or MOOCs for example, but how could an event organiser award a badge to someone whose details they didn’t know? Would they have to do all the data-inputting themselves? This sounded like a prohibitive amount of work.
Fortunately, a site that David Muir had pointed me towards had the answer. Badg.us allows a user to create badges very simply, and in much the same way as ForAllBadges. However, the badg.us site interfaces drectly with the Mozilla Backpack and Persona sign-in service, making it a far more user-friendly solution when you will be issuing badges to people from outwith your organisation or whose details you are unaware of in advance. It also lightens the administrative burden of issuing badges, as the onus is on the claimant to provide their details. The site allows you to set up reusable codes (like the one above) for large-scale issuing, or one-use codes when you are looking to target your badge claimants more precisely (I used this to create “Presenter” and “Organiser” badges for tmlovelibraries, printed up claim codes for these and gave them to Fearghal to distribute).
In my opinion, these tools make the whole process of creating and awarding badges far more accessible to the typical classroom practitioner; teachers who, much like myself and Fearghal, would previously have found the process too technical can use these services to gain the benefits of OpenBadges without having to become coding wizards. Other tools have been developed that can do a similar job – for instance, WPBadger and WPBadgeDisplay allow you to utilise WordPress blogs to issue and display badges whilst OpenBadges.me provides a very useful badge designer for either online use or as a WordPress plugin . Recently, the ForAllBadges site has joined together with its sister site ForAllRubrics, and you can set things up so that once a rubric has been com pleted, an OpenBadge can be awarded automatically. After some late-night Twitter conversations between myself and the founder of ForAllSystems, ForAllRubrics also has built-in links to the CfE Experiences & Outcomes. A very handy teacher toolkit!
So, now it begins to get exciting. The badges are no longer a concept. Now that a teacher – or a student? – can create and award these badges, what might they do with them? I have a number of ideas that I’ll be trying in my school, and I know Fearghal had an inclination to use them as part of a programme he delivers at his school (this provoked a very interesting side discussion with David Gilmour about extrinsic/intrinsic motivation). I know that other organisations (including the Scout Association and – believe it or not – the SQA) have been looking at introducing them too.
What would you do with OpenBadges?
(this post can also be found on Iain’s blog (The H-Blog) at http://h-blog.me.uk/archives/435)