244
edits
Badges/chicago/techFAQ: Difference between revisions
no edit summary
(Created page with "== Technical FAQ == === What is this? === This is a list of frequently asked questions about the technical requirements for the Chicago Summer of Learning badging program. === ...") |
No edit summary |
||
| Line 26: | Line 26: | ||
# Displayer - A website that allows their users to display badges they’ve earned and collected in their backpack. | # Displayer - A website that allows their users to display badges they’ve earned and collected in their backpack. | ||
# Criteria Page - A web page that describes what a learner needs to do to earn a particular badge. For more information, see the question below, “How do I create a Criteria Page?” | # Criteria Page - A web page that describes what a learner needs to do to earn a particular badge. For more information, see the question below, “How do I create a Criteria Page?” | ||
=== Will my organization have to host anything? === | |||
No, Mozilla will coordinate hosting open badge issuing platforms. However, if you’re capable of hosting an open badge issuing platform, and want the flexibility that provides, there’s no reason not to. Talk to us: badges@mozillafoundation.org | |||
=== How will badges be delivered or issued? === | |||
Using the OpenBadger issuing platform, badges can be be delivered in one of three ways, | |||
# Through your website. We can support online-issued badges through a web API that can integrate with your existing website. The API has existing javascript libraries that make it easy to integrate. (Don’t worry, we’ll help you with this) | |||
# Through your own email system using a claim code. The learner will receive an email from you with a web location to visit and a claim code to enter on the site to claim a badge. | |||
# A printed paper with a web location to visit and a claim code to enter to claim a badge. | |||
=== What data can be collected? === | |||
Each badge has a defined set of metadata with it that communicates who issued it, when it was issued, what the earner had to do to get the badge, and optional evidence. The Open Badge Infrastructure stores this information with the badge, as well as a minimum amount of personally identifiable information (a verified email address) to verify their identity. There are opportunities to collect additional data from learners through deeper integration with the OpenBadger API, but will have to be worked out on a case by case basis. | |||
=== What’s the badge metadata specification? === | |||
The Open Badge specification is simply a set of required and optional information that is included with every badge issued. It includes issuer, issue date, criteria URL, evidence URL, expiration, and other information. It is an open standard for badges that ensures that all badges, regardless of type or issuer, are interoperable. | |||
=== What information do I need to include with my badge? === | |||
You don’t need to worry about this yet, we’ll help you, but eventually you are going to define the criteria information for the badge (i.e. what someone has to do to earn the badge), as well . | |||