Mozilla BadgeKit

View Github Repository Open presentation in a new window

cmcavoy

See all presentation from cmcavoy

Mozilla BadgeKit

0 0

badgekit-overview

Presentation on Mozilla BadgeKit

On Github cmcavoy / badgekit-overview

Mozilla BadgeKit

http://badgekit.openbadges.org

Sunny - overview
Sunny - overview

Technical Architecture

The Issuer

The Issuer in this case is a collection of issuers, most common case is a "city". The issuer also controls all communication with the community it serves.

The Admin (BadgeKit)

The admin uses the same api's as the issuer site.

The API's

Data Hierarchy (CSOL)

In CSOL, we had a strict top down hierarchy. A single badge system (CSOL) had issuers, programs and badges.

Data Hierarchy (BadgeKit)

In Badgekit, we allow for interrelationships via templates. Templates can be shared between issuers and systems.

Templates

Allowing instances and issuers to share templates gives us the ability to pre-seed a system with any sort of standards we want.

Badge Lifecycle

Template

Badge Lifecycle

Draft

Badge Lifecycle

Published Badge

The actual badge is displayed on the issuer / city site via the api. The issuer site has complete control over the display.

Badge Lifecycle

Published Badge

Information about the displayed badge, how many have been issued, etc are shown on the badgekit site.

Badge Issuing

By Claim Code

Create claim codes, send them as emails. The emails or any kind of communication, is still handled by the issuer site.

Badge Issuing

Apply & Award

Applications are submitted through the issuer site, but evaluated in badgekit.

Badge Issuing

Auto-awarded Level Badges

Badges can have points associated wtih them, that are earned through other badges. When the points are earned, badges are issued.

Federated Backpack

Based on CSOL backpack. Federated.

State Changes

Communicated back to the Issuer site via webhook / callback.

We used callbacks extensively in CSOL

Authentication / Authorization

Built into the API, so that applications can build on top of the same ACL's BadgeKit uses.

Publishing the ACL's via the API makes it possible to integrate other tools into the admin. Custom reporting, metrics, etc. Exploring the Hawk standard (sort of like OAuth).

Timeline

  • January 22nd - first round of user testing / iteration cycle.
  • February 5th - second round of user testing / iteration cycle / branding finalized. Begin integration with CCOL.
  • March 6th - BadgeKit beta release
  • End of March - federated city backpack release
  • April 1 - CCOL integration, Spring Break release.
  • June 1 - Cities of Learning 2014 Summer shared model rollout with up to 12 city partners.

Sunny discuss the timeline. Include bit about user testing.

What's Next?

  • SMS / Mobile Badging
  • Learning Pathways / Ladders of Engagement Integration in Badge Definition
  • Robust, Earner Focused Backpack
  • Enhanced Dashboard for Issuers

Jess, setting up the future

Questions