-
Notifications
You must be signed in to change notification settings - Fork 46
Adds public cross-system BadgeClass listing #120
Conversation
example, but it's possible that it will work. Need confirmation.
I would really want to see the URL location of the badgeclass as publicly accessible through BadgeKit as part of that output. |
BIG apologies. I gave you the wrong example for the badge class listing. It is way simpler - just a list of badge class locations. Here's a json example: https://gist.github.com/kayaelle/0ad933c2528fde4b829b |
Just to be clear - the list should be of url's pointing at |
Exactly - you can read more here: http://mozilla.github.io/openbadges-directory/#addbadges |
Ok, it's updated to match the specification listed on the directory page. Example output https://gist.githubusercontent.com/cmcavoy/cb9de5db668e7f7c3713/raw/4477e0b341eab00bd68162cd1ed34c2abfe12d40/gistfile1.json What say ye @brianloveswords @christensenep @kayaelle @ottonomy @jpcamara? |
👍 👍 My only tiny consideration would be that this format is really close to being able to deliver full Badge Class objects, as they appear baked by the current Backpack Issuer API, except that the Backpack uses the "_location" property instead of "location". On the other hand, it seems kind of silly to use "_location" when the only purpose of the list is sharing URLs though. |
Noted @ottonomy . Going to move the format discussion to the directory repo. For now I'm going to merge and push this to prod. |
Adds public cross-system BadgeClass listing
👍 Given the weirdness in mozilla/openbadges-backpack#1029 I fully support pushing this as is. We should talk in the Standard group about a modern 1.2-forward way of implementing embedded BadgeClasses and IssuerOrganizations. |
@cmcavoy when it's ready you can register the endpoint here: http://mozilla.github.io/openbadges-directory/#addbadges And the badges should get indexed. I'll get you an issue for backpack endpoint - apologies for delay. |
Hey @cmcavoy - Looking into why the badgekit badges aren't getting indexed. This url: http://api.badgekit.org/public/badges Is this correct endpoint url for the badgekit badges list? Thanks |
Did the merged code get deployed on badgekit.org? On Wed, Aug 13, 2014 at 5:08 PM, kayaelle notifications@github.com wrote:
|
Hi guys, wasn't this reverted because it had caused a bug? Looks like the endpoint is removed here #122 Apologies if I'm misunderstanding the problem! 😕 |
The last time I spoke to cmcavoy the endpoint had been merged and he registered it as an endpoint with the directory. The directory didn't index it. That was a couple of weeks ago. I only just had chance to look into the indexing issue and the url returned the error. Not clear on timing of when the endpoint was registered and #122. Can ask cmcavoy when he gets back. No urgency on it. Thanks! On Aug 14, 2014, at 5:28 AM, Sue Smith notifications@github.com wrote:
|
|
||
server.get('/public/badges', [ | ||
function(req, res, next) { | ||
badgeListName = "badgelist" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks to me like the first time you hit this route, you change badgeListName to "badgelist", and all subsequent calls to showAllBadges will now send back data under "badgelist" instead of under "badges".
For #119.
Example of the output is here: https://gist.github.com/cmcavoy/7ad769d76c91c8832bdd
@kayelle @jpcameron can you take a look at the gist and let me know if that output is ok?