1,065
edits
Badges/StepxStep: Difference between revisions
no edit summary
Prawsthorne (talk | contribs) |
Prawsthorne (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
# This blog post details [http://criticaltechnology.blogspot.ca/2012/05/open-badges-what-ive-learned-so-far.html what I've learned so far] with open badges. It also serves as a good list of resources. | # This blog post details [http://criticaltechnology.blogspot.ca/2012/05/open-badges-what-ive-learned-so-far.html what I've learned so far] with open badges. It also serves as a good list of resources. | ||
# The p2pu challenge titled [http://p2pu.org/en/groups/the-world-of-open-badges/ open badges 101] is a great way to jump into the community. | # The p2pu challenge titled [http://p2pu.org/en/groups/the-world-of-open-badges/ open badges 101] is a great way to jump into the community. | ||
==== related screencasts ==== | |||
* Readings about the Open Badges Infrastructure - http://youtu.be/3-FkzP18_lQ | |||
* FAQs and Technical resources available for Open Badges - http://youtu.be/fzARrbOoP-8 | |||
* First look at the JSON message structure for issuing open badges - http://youtu.be/jqjuqmyW06E | |||
* A first look at the P2Pu Open Badges 101 challenges - http://youtu.be/LcIQw-NkOFE | |||
== Step 1: Go out and claim yourself a badge == | == Step 1: Go out and claim yourself a badge == | ||
| Line 17: | Line 22: | ||
'''''Note:''' not all badge issuing platforms work with the open badges. This is part of the open badges initiative, to create a standard approach and messaging protocol for the issuing and display of badges.'' | '''''Note:''' not all badge issuing platforms work with the open badges. This is part of the open badges initiative, to create a standard approach and messaging protocol for the issuing and display of badges.'' | ||
==== related screencasts ==== | |||
* Digital badges - claiming your first badge - http://youtu.be/cp0v8LKIeHo | |||
== Step 2: Technical Prerequisites == | == Step 2: Technical Prerequisites == | ||
| Line 40: | Line 48: | ||
==== Or some other server side programming language or application ==== | ==== Or some other server side programming language or application ==== | ||
Making use of the javascript libraries from within a web page is the manual approach to issuing badges. If you are going to want to issue badges from within a learning management system (LMS), another software application or custom developed software you are going to have to develop an understanding of that particular environment. | Making use of the javascript libraries from within a web page is the manual approach to issuing badges. If you are going to want to issue badges from within a learning management system (LMS), another software application or custom developed software you are going to have to develop an understanding of that particular environment. | ||
==== related screencasts ==== | |||
* Open Badges Technical Prerequisites - JavaScript - http://youtu.be/jzJjimCZz6g | |||
=== The technology stack === | === The technology stack === | ||
| Line 66: | Line 77: | ||
# Web hosting, programming language and database to store desired earner badges information | # Web hosting, programming language and database to store desired earner badges information | ||
<br/><br/><br/> | <br/><br/><br/> | ||
==== related screencasts ==== | |||
* Open Badges Technical Prerequisites - Technology Stack - http://youtu.be/X3Dc-Vofroc | |||
=== Server Infrastructure === | === Server Infrastructure === | ||
Each role requires resources on the internet, these vary greatly due to the work that is required. The diagram below shows the three roles and their interactions. The issuer on the left requires the most server infrastructure. The earner backpack requires infrastructure resources which will increase if you are planning on hosting a backpack (this is currently not recommended due to the lack of backpack federation features). It is currently recommended that you use the openbadges backpack hosted at http://beta.openbadges.org. The displayer role requires the least amount of resources as displaying badges requires the least amount of | Each role requires resources on the internet, these vary greatly due to the work that is required. The diagram below shows the three roles and their interactions. The issuer on the left requires the most server infrastructure. The earner backpack requires infrastructure resources which will increase if you are planning on hosting a backpack (this is currently not recommended due to the lack of backpack federation features). It is currently recommended that you use the openbadges backpack hosted at http://beta.openbadges.org. The displayer role requires the least amount of resources as displaying badges requires the least amount of softwar features. This can increase if the displayer provides additional badge display features.<br/><br/> | ||
[[Image:Tech-diagram-v3 updated.png|700px|Open Badges -- Tech-diagram-v3 updated.png]] | [[Image:Tech-diagram-v3 updated.png|700px|Open Badges -- Tech-diagram-v3 updated.png]] | ||
| Line 81: | Line 94: | ||
## criteria information | ## criteria information | ||
## issuer information | ## issuer information | ||
==== for the earner: ==== | ==== for the earner: ==== | ||
The earner requires the least amount of server infrastructure to support their activities. The earner could successfully earn badges with no server infrastructure of their own. The earner will require web locations to be able to host their evidence; this hosting could be in blogs, wikis, personal web spaces or existing educational infrastructure. If the earner does have their own server infrastructure or web space this could be used to host their evidence. | The earner requires the least amount of server infrastructure to support their activities. The earner could successfully earn badges with no server infrastructure of their own. The earner will require web locations to be able to host their evidence; this hosting could be in blogs, wikis, personal web spaces or existing educational infrastructure. If the earner does have their own server infrastructure or web space this could be used to host their evidence. | ||
==== for the displayer: ==== | ==== for the displayer: ==== | ||
From a server infrastructure perspective the displayer will need to have the ability to host HTML, JavaScript or an application widget that can make calls to the displayer API. This can be as simple as a hosted web page or a blog that can have the HTML of JavaScript embedded. If the displayer is providing the more robust features of a widget they will require the features for hosting the widget, making the displayer API calls, and any other programming or database infrastructure to support their widgets features. | From a server infrastructure perspective the displayer will need to have the ability to host HTML, JavaScript or an application widget that can make calls to the displayer API. This can be as simple as a hosted web page or a blog that can have the HTML of JavaScript embedded. If the displayer is providing the more robust features of a widget they will require the features for hosting the widget, making the displayer API calls, and any other programming or database infrastructure to support their widgets features. | ||
=== | ==== related screencasts ==== | ||
* Open Badges Technical Prerequisites - Server Infrastructure - http://youtu.be/j-fOUEmHGnM | |||
== Step 3: Creating your site == | == Step 3: Creating your site == | ||
=== Basic Requirements === | |||
==== Stability in the URL ==== | |||
==== Basic web site with the ability to support the json content type ==== | |||
==== Ability to hash the earners email with the salt ==== | |||
== Step 4: Issuing a badge == | == Step 4: Issuing a badge == | ||
=== Files and Folders === | === Files and Folders === | ||
| Line 99: | Line 120: | ||
https://groups.google.com/d/topic/openbadges/NC_5_2pgiKA/discussion | https://groups.google.com/d/topic/openbadges/NC_5_2pgiKA/discussion | ||
== Step 7: Displaying your badges == | == Step 7: Being a badge displayer == | ||
== Step 8: Displaying your badges == | |||