I'm not sure how ours & the UMich one differ significantly - the process
looks fairly similar. I'm not seeing the code for theirs posted, but it
sounds like they took the existing User Badges module and tweaked it to
meet their custom needs. I built ours as a submodule with a dependency on
User Badges. For ours, site admins change the Mozilla Open Badges
information and assign badges to the user. When a badge is assigned, an
assertion URL is created, and the user can then log in and choose to push
the badge to his/her Mozilla Backpack (by clicking a link). We use the
issuer API (https://github.com/mozilla/openbadges/wiki/Issuer-API) to
assign the badge.

Zeth

On Fri, Mar 15, 2013 at 12:15 PM, Louis St-Amour <[log in to unmask]>wrote:

> How does that Drupal module compare with
> https://open.umich.edu/wiki/Badges/build ?
>
> Personally I couldn't make heads or tails of the Mozilla Badges project
> until I saw this page's overview at https://wiki.mozilla.org/Badges and
> https://github.com/mozilla/openbadges/wiki/Infrastructure-Requirementswhich
> has a system diagram and explains the key concepts:
>  Definitions
>
>    - *Learner / User* - someone who has earned a badge.
>    - *Issuer* - an organization which issues a badge.
>    - *Badge* - an achievement, represented by a PNG file with embedded
> data.
>    - *Baking* - the act of embedding data in the badge PNG file.
>    - *Assertion* - a JSON file hosted by the issuer that describes a single
>    badge and the learner it belongs to. This information is kept in plain
>    text. The assertion includes a BrowserID identifier (an email address).
>    - *BrowserID* - the authentication framework used in the application.
>    More information on BrowserID <https://browserid.org/>.
>    - *Backpack* - a learner collects multiple badges from many different
>    issuers, the badges are kept in the OBI Backpack, a logical grouping of
>    badges and the user that owns them.
>
> It's an interesting idea, for sure, to send and share badges as PNGs with
> embedded metadata, particularly if they can be signed and verified.
>
> Thanks,
> Louis.
>
> On Fri, Mar 15, 2013 at 1:53 PM, Zeth Lietzau <[log in to unmask]
> >wrote:
>
> > We're planning on using badges for some upcoming teen content creation at
> > Denver Public Library, and are hoping to hook into Mozilla Open Badges.
> > We're a Drupal shop, and have been working on a module that hooks into
> the
> > User Badges module to connect with Mozilla:
> >
> > http://drupal.org/sandbox/zeth/1931630
> >
> > Zeth
> >
> > On Fri, Mar 15, 2013 at 9:41 AM, Megan O'Neill <[log in to unmask]>
> wrote:
> >
> > > We're talking about it, but not sure whether we'll be able to devote
> > > resources to it yet. I will send you an update if we make a decision!
> > >
> > > Megan
> > >
> > >
> > > On Fri, Mar 15, 2013 at 11:18 AM, Michael Schofield <
> [log in to unmask]
> > > >wrote:
> > >
> > > > Is anyone [planning on] issuing badges? We are so early in the
> process
> > > > that rather than homebrewing something it's probably to our advantage
> > > using
> > > > something like the Mozilla Open Badges. It's fairly new, but do any
> of
> > > you
> > > > have experience? Any general badge-issuing words of wisdom?
> > > >
> > > > [1] http://openbadges.org
> > > >
> > > > Michael
> > > >
> > >
> > >
> > >
> > > --
> > > Megan O'Neill Kudzia
> > > Web Services & Emerging Technologies Librarian
> > > Stockwell-Mudd Library
> > > Albion College
> > > 602 E. Cass St.
> > > Albion, MI 49224
> > >
> >
>