-
Notifications
You must be signed in to change notification settings - Fork 84
BadgeKit
BadgeKit: MVP: What we will we deliver for March 2014
For DML we want to issue DML badges and this is how we want to do it:
-
We want to visually design the badges and define the criteria for earning them in "Badge Studio".
Example - design the DML Selfie Badge)
Visual = polaroid icon
Meta data def/ criteria = yo, i was here.... see ... im at this photobooth.
Badge Studio on badg.us
-
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.
-
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 [Facebook or even LinkedIn hey!+1] profile.
Example: Nichole goes into her backpack and clicks share button which gets her badge posted on her profile with all the embedded metadata.
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. (but not a badge system - focusing on single badges) I think so for MVP - correct.
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.
- At DML we will also release a refreshed badgekit.openbadges.org that shows these verbs as offerings on the site as templatized, forkable, and documented.
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)
Badg.us will become our nightly
Next steps:
Create github issues for each step 1 through 6.
For support working with BadgeKit or Open Badges, use any of the following channels:
- Post general questions in our Community Google Group and post technical questions in our Dev Google Group.
- Reach members of the Open Badges team directly on IRC (irc.mozilla.org) on the #badges channel.
- Email questions directly to [email protected] and a member of the team will follow-up.
- Follow or tweet the Open Badges team @OpenBadges.
- Get involved or submit issues via the GitHub repos - feedback is always appreciated!
Introduction
Users
Developers
- Self-Hosting Guide
- Troubleshooting BadgeKit
- API Introduction
- User API
- BadgeKit and Open Badges Resources
Concepts
Design
History