Mozilla Open Badges 201Badge System Design & Technology Review

This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.

Megan Cole Marketing Lead

megan@mozillafoundation.org@megcolek

Sunny LeeProduct Lead

sunny@mozillafoundation.org@soletelee

Badge System Design OverviewTechnical Overview7 Steps for RoadmappingWhat’s NextAnd more...

Welcome to our 201 Webinar

AAssessment Assessment Assessment

Assessment Assessment Assessment Assessment Assessment

Assessment

differing opinions

BSome folks say our educational system is…

Cmany challenges

seat time complicated metrics

overcrowding remediation

Badges act as representations of achievements, learning, skills,

interests, competencies

hard & soft skills,peer assessment, and

stackable lifelong learning

Open Badges are a form of personal social currency

you can share across the web

How are we getting there?

Through ashared infrastructure:a universal standard

Badge metadata spec + Issuer API

(and in 2014 an Endorser API)

Badge nameBadge URL (description) Badge criteriaBadge imageIssuerIssue dateRecipientAlignment (standards)Expiration dateEvidence URL

What does this mean in practice?

formal & informallearning pathways

Can I see an example?

Badge System Design

http://bit.ly/badgesystemdesign

1. Badge Team 2. Badge Info

3. Badge Tech 4. Badge Design

http://bit.ly/badgesystemdesign

http://www.digitalme.co.uk/badgecanvas/

Homework

exercise #1: write down your top 3 badge system goals

(5 minutes)

Homework

exercise #2: copy the spreadsheet & begin working

through your first badge(7 minutes)

Homework

exercise #3: share your badge thinking with us at

badges@mozillafoundation.org(8 minutes)

http://bit.ly/BSDwiki

http://bit.ly/ob-research

Technology Overview

Mozilla’s  Open  Badge  Infrastructure

Free and open source software - Backpacks and APIs

http://community.openbadges.org/

API: An application programming interface (API) that specifies how software components should interact with each other.

http://bit.ly/OB_IssuerAPI

Widget: A small application with limited functionality that can be installed and executed within a web page by an end user.

http://bit.ly/OBWidgets

http://bit.ly/platform-chart

http://bit.ly/OBIDev

7 key points in roadmapping and resource management

1. Funding2. Partnerships3. Research4. Badge system design5. Time management6. Technical resources7. Design resources

1. Funding

How might you actively think about the personnel and

required resources needed to build your best possible badge

system?

2. Partnerships

How might you freely imagine the system that you might be

able to build with others?

3. Research

How might you intentionally plan for the ways that badges

may influence you & your teams as well as your badge

earners?

4. Badge System

How might you consciously think about the genealogy of your system and it’s future

growth?

5. Timing

How might you deliberately plan for a full system life cycle?

6. Technology Resources

How might you best architect your team to fail fast and

maximize success?

7. Design Resources

How might you dynamically explore the most compelling visual representation of your

system?

1. Funding2. Partnerships3. Research4. Badge system design5. Time management6. Technical resources7. Design resources

What’s Next?

Join our weekly Community callWednesdays at 9am PDT / 12pm EDThttp://bit.ly/OBCommCalls

Post questions to our Google Grouphttps://groups.google.com/d/forum/openbadges

Reach out to us for informationbadges@mozillafoundation.org

Stay up-to-date with our Bloghttp://openbadges.tumblr.com/

Stay in Touch

THANK YOU!

http://openbadges.org || @OpenBadges