3. Who is Issuer?
Whoever issues a badge becomes an issuer.
An issuer is one who issues
badges to users
Badge
Earner
Issuer
[Schools, Institutes, Organizations, Jon Training,
Gaming sites, Online learning]
3
EbizON
4. Backpack
A Backpack is the central repository system where the badges are stored when user claims the
badges. From the Backpack, user can manage the badges, group them, set privacy level and share
it on various displayer sites.
Group badges
Set Privacy
Share
Backpack
EbizON
4
5. Displayer
Displayer is any site where the badge is being displayed. If you want the users to display their
badges on your site as well, you can also become a displayer. It can be multiple sites. The
backpack is used to share the badges on various displayers.
Your website
Social
networking
sites
Backpack Job Portals
Displayer
5 EbizON
7. Approach 1: Using Mozilla Backpack
• An issuer and displayer plugin for your site.
• Mozilla Backpack.
• Each user will use Mozilla Persona to claim their badges.
• Mozilla Displayer API can be used to embed Javascript widgets.
Issuer Plugin Mozilla Displayer
Claimed badges
Backpack Plugin
A central repository to Push to
To issue badges keep and manage all the display To display badges
badges from various
issuers
Mozilla Persona
7
EbizON
8. PROS & CONS Of Approach 1
Pros
• Easiest to implement
• Mozilla takes care of API upgrades etc.
Cons
• We need to have users sign up on Persona.
• Branding of your site is not controlled.
8
EbizON
9. Approach 2 – Using a local instance of
Mozilla Backpack
• An issuer and displayer plugin for your site.
• An instance of Mozilla Backpack on your server https://github.com/mozilla/openbadges
• The backpack instance would be meant to bypass Persona and integrate with your website’s SSO
implementation
A local
Issuer Plugin instance of Displayer
Claimed badges Mozilla Plugin
Backpack Push to
SSO A central repository to
To issue badges display To display badges
keep and manage all the
badges
9
EbizON
10. PROS & CONS of Approach 2
Pros
• Your website’s branding can also be implemented on manage backpack.
• Here you can also control that only your badges are shown on your site.
Cons
• Slightly difficult to implement, since you’ll need to by-pass Persona, Integrate the manage
backup interface with your user page etc.
• Here the local instance of backpack needs to be upgraded regularly as Mozilla upgrades the
backpack code.
10
EbizON
11. Approach 3 – Drupal Backpack
Implementation
• Run the Drupal backpack implementation (https://github.com/ebizon/openbadging-profile) on your local
server
• Also includes issuer backpack implementation.
• Displayer API would integrate with external forums/blogs etc.
• These badges are OBI Compliant and can be pushed to Mozilla
Displayer
Issuer Claimed badges
Custom Backpack
Subdomain Push to
[www.badging.example.com] A central repository to www.example.com
manage and group the display
SSO earned badges
Badges will be issued here to
the users.
www.example1.com
Your Site
[www.example.com]
11
EbizON
12. PROS & CONS of Approach 3
Pros
• Already existing out of the box system.
• Fastest to use.
• Would have to implement SSO with existing system.
• Branding can also be controlled.
Cons-
Backpack is custom written in Drupal and therefore, needs to be updated whenever OBI
specifications are changed.
12
EbizON
13. If you want to integrate badging with your site
using any of these above,
Contact : priyanka@ebizontek.com
13
EbizON
14. For Any Query or Installation of
Open Badges, contact:
Priyanka Jhamnani
Sr. Drupal Consultant/Manager
Email: priyanka@ebizontek.com
Skype: priyanka.jhamnani
Drupal.org http://drupal.org/node/1962434
id:
Website: http://ebizontek.com
EbizON
