A null result is still a result. Right?

IntegrityQuiz_makebadgesIn the Unjaded Reflections blog post “Why should you create an open badge system”, Jade Forester has three warnings for people designing open badge systems:

1. Don’t try to make your badge system grow too much, too fast;
2. Ensure you have the technical and human resources you need to fully support your badge system;
3. Make sure there’s a need for badges

Starting INSIGNIA as a small scale system, with available resources, certainly sounded like a sensible approach, especially given this is only a seed project. If the need for the badge is clear, it’s likely to help with acceptance of open badges in the research community. Given these constraints, I seemed to have a perfect starting point: ANU’s compulsory, yet non credit bearing, research integrity course.

This course is a problem I had inherited from my predecessor, who built it in collaboration with the community, but without a good assessment regime or ongoing maintenance strategy. The course attempts to explain, mostly through case studies, how complex research integrity issues, such as authorship, plagiarism, informed consent etc, are in practice. The material was great, but I’ve been working for nearly a year to move the course from his bespoke online platform into our ANU learning management system (on Moodle) and to introduce a quiz as the final assessment activity (yes – this seemingly straightforward task took nearly a year. Committees eh?).

Taking Jade Forester’s advice on board, I thought issuing a badge for the successful completion of the final quiz would be a good first step towards an INSIGNIA series of badges for research education. I needed a way to provide students with evidence that they had completed the course and I had available resources. The research integrity course content was already there in Moodle 2.5, which I know has the capacity to create and issue badges. Red Dog Learning, who had been helping me to build the course, even offered to make the badge for me as the last part of their contract.

The problem, I quickly discovered, was that people and technical resources are not always enough. The barriers are more likely to be hidden and, just like a coral reef just under your bow, you sometimes don’t know they are there until you run aground.

Last week I happened to wander into the lunch room at the same time as the ANU online team, who are the people responsible for looking after ANU’s implementation of Moodle. Over my burrito I asked the team if our Moodle had the badges option turned on because I couldn’t see it anywhere when I was editing my course. The team told me they had not turned it on because no one had asked for it.

I told them I needed it and politely asked if they could turn it on.

They hesitated. “Most people don’t have a good reason for using open badges” said one, cautiously. I suspected this was a gentle way of saying “no” so I pounced on it.

“Well I have a whole pedagogical model” I replied. Then I explained the idea of open badges providing a ‘respectful pedagogy’ for research students, who may be well versed in the material within a course and just needed to demonstrate competency – my research integrity course being a good case in point.

The ANU online team nodded and looked thoughtful.

“We’ve been reluctant to turn it on because anyone could offer a badge for anything” another member of the team said.

I replied that was rather the point of open badges, but I could see the problem with it in a university context. Anything with the ANU brand on it, and no quality control mechanism behind it, was challenging to the credentialing authority of our institution. Poorly designed badges, like poorly designed courses, have the potential to reflect badly on us and might even undermine our credibility as an education provider.

I explained I was happy to have this conversation because my research was designed to elicit just these issues and write about them. But I couldn’t get very far in my project if I couldn’t actually make any badges available. Perhaps they turn on the badge making capacity, but just for me. I cheekily promised to be good.

They told me that turning on the capacity for making badges would have to pass through their stakeholder consultation mechanisms. I’ve been in the university long enough to spot the possibility of slow death by committee when I see it, so I offered to write a memo for the committee and the DVC A – to explain the project and the need for badges.

Still they hesitated. I couldn’t understand why.

As it turned out, the ANU online were worried about the possible privacy implications of open badges. The idea of a badge is that it can be easily moved ‘out’ of the Moodle platform and displayed in other places, like the Mozilla backpack. If the badge ‘carried’ data about the student with it, like an email address, this would be a breach of privacy legislation and the insitution would be subject to up to $300,000 in fines. Apparently this was complicated by the fact that ANU is a federal university (actually the only federal university, since all the others are run by state governments).

I started to get a head ache. “Would an open badge project off the ground actually require an act of Parliament?” I wondered aloud. Then I laughed, you know – in horror. My project was melting around my ears.

ANU online team looked at me sympathetically. They didn’t want to stifle innovation they explained, but they had Responsibilities. I believed them, but had to ask the next obvious question: “can we put in a check box that students can tick so they are giving consent for their private information to be shared in the badge?” Well, that probably contravened the legislation as well they explained. I must have looked despondant at that point because the team did, bless their hearts, tell me they would explore whether Moodle could selectively turn off student information so that the badge could be ‘clean’.

This is, I suspect, where the road gets bumpy… A null result is still a result. Right?

Oh well. At least I managed to use Makebadges to do the graphics for the badge. If you are interested in designing your own badges, I’ve found some good sites which I have started to compile into a ‘make your own badges!” page. I’ll be interested in your comments – has anyone else had a similar experience?

Advertisements

11 Comments

  1. Hi Inger,

    Having dealt with privacy issues before with universities I’m not exactly sure that this is one. Firstly, it’s debatable whether an email address actually counts as something to be covered by the privacy acts and policies,

    Secondly, even if it is, the Mozilla open badges only stores a hashed version of the email address that is not visible to end users. In fact Mozilla prefers UserIds to be used rather than email addresses.

    Thirdly, display of badges is entirely within the control of the end user (the student).No data is made publicly available without them making it explicitly so.

    You may get arguments that a user’s email address is being stored on an external system that could be hacked. I presume that ANU uses no external systems then? If so it would be just about the only university that doesn’t.

    All of these things can be accommodated with a bit of will from the powers that be. After all, whole universities store their email with third party providers let alone their email addresses.

    Just my 2 cents 🙂

    Cheers

    Mark

  2. I absolutely loved the metaphor of the invisible coral reef – this is what I have experienced several times. I really feel for your Moodle team and you! So many technical, institutional, & policy roadblocks can seriously hamper innovation.

    At UOW the concern has been more around branding of badges, both in their design and in their use. Policy concerns around UOW name being used as giving credentials for skills in the public and the quality control around that, for example.

    We are trialling badges in Moodle 2.5 by limiting the access to them through the user roles – creating a special role just for the pilot team. So badges are only available for the teacher (myself) and the students in my course. This will let us trial badges in a very limited capacity before a possible uni-wide rollout.

  3. This is absolutely crazymaking, because a student who applies for a badge can be told ‘this requires giving permission for us to disclose your name and e-mail address’ — and if they continue on that basis then the privacy implications vanish.

  4. Pingback: Do looks matter? Discussing badge design with ANU students | INSIGNIA

  5. Pingback: Badges – who do we trust, and why? - Centre For Legal Education

  6. Pingback: Badges – who do we trust, and why? — Paul Maharg

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s