BadgeKit

Overview

March 2014 represents the date of the Digital Media and Learning conference and will mark the release of BadgeKit beta. The concept here is that we will develop a unified user experience from the point of designing the badge - to the point of a user posting that badge to their social media profiles. Critical to this is also building out all the necessary touch points for tools in the ecosystem to be able to plug in or build on top of the BadgeKit foundation. We will use the DML deliverables as a use case to help us contextualize the tools that we will build out for BadgeKit.

##MVP For DML we want to issue DML badges and this is how we want to do it:

####Visually design individual badges and define the criteria for earning them in "Badge Studio".

Example: I can design the DML Selfie Badge visual using a polaroid icon and then define the meta data def/ criteria = "you must take a picture of yourself with DML signage indicating you're at the DML conference 2014" in Badgestudio that will be hosted on Badg.us

Badge designing can be done on a number of existing platforms including Makebadges, Achievery, openbadges.me, and many more.

####Learners can then apply for the badge by submitting evidence and their e-mail address - on a splash site for DML

Example: Nichole goes to badges.dml.org and she click on the selfie badge "apply" button, reviews the criteria, submits her selfie photo that she takes at the DML photobooth along with her session #, she then types in her email address and hits submit. As a result of this she gets a confirmation message and email and her submission goes to the queue for review.

Badges built on other badge design platforms should be easily importable and made available to earn.

####Mentors or peers can review the badge applications against the criteria. Once criteria is met, the badge will be issued to them via email.

Example: Nichole's application is in the queue and a designated mentor or peer with appropriate privileges can log in the assessment tool and review the applicaiton against a rubric. After evaluation against the rubric, mentor determines to award badge or not along with feedback. Nichole is sent an email with review results.

####Recipient accepts the badge and send it to their backpack - badge acceptance flow from email

Example: If mentor issues Nichole a badge, Nichole receives email and clicks button to push to her backpack. She is taken through a claim flow and the badge gets into her backpack.

####They share their badge on their social media profile.

Example: Nichole goes into her backpack and clicks share button which gets her badge posted on her profile with all the embedded metadata.

####At DML we will also release a refreshed BadgeKit site

The site will show the verbs as offerings on the site as templatized, forkable, and documented.This will also be the moment to launch the new brand.

How this helps us to build for BadgeKit

As a result of this we will be developing the following tools for BadgeKit:

• Build: Create 1 tool that helps anyone design the visual look of a badge,develop its criteria and define its metadata.
• Issue: Revised UX flow for claim code issuance + acceptance
• Collect: a UI that allows users to search, display and [group] badges
• Share: share an individual +/or group of badges through an embed code. multiple opportunities to share the news of a badge (with or w/o the badge itself).
• Assess: Implement Aestemia UI for assessors to review evidence against criteria for evidence-based assessment and develop/Design plugin for applicants to submit evidence
• Branding: UI and visual design of BadgeKit will be applied to all the tools.

##Roadmap:

While we are going to be working on a detailed roadmap, we will definitely have a few milestones to reach this goal. The milestones:

• Nov 11 - Project kickoff
• Jan 30 - badg.us relaunch
• Feb 15 - badgekit.ob.org push
• March 4 - release in conjunction with SXSW Edu
• March 6-8 : DML

##Notes:

• Discovery and pathways will be a parallel effort led by Chloe, keeping in mind that - the pathways work will eventually be incorporated into the core BadgeKit offerings (so the team will be kept in the loop and provide support and feedback on that work) but we are developing it in the meantime in a parallel effort so that the work is able to be incubated without the constraints of the DML MVP.

• badg.us will become our nightly build.

• A glossary of commonly used terms is being developed.