[Data Collection] OSH platforms to include

[moedn]

1. selected for v1.0

• [x] GitHub
  • [x] including a manually curated GitHub-repository of manifest files
  • [x] appropedia (OKH fork)
• [ ] GitLab (hope is has a very similar API)
• [ ] Wikifactory (API)
• [ ] list of OSHWA-certified products link (API)

2. pre-selected for v1.1

• [ ] hackster.io (API)
• [ ] thingiverse (has an API)
• [ ] kitspace
  • cool thing: PCBs can be ordered directly there by linking to service providers like Aisler or manufacturers directly

3. pool of further platforms

• [ ] maker.pro
• [ ] [instructables](https://www.instructables.com/9
• [ ] makernet/fieldready airtables
• [ ] OSEG wiki
• [ ] OSE wiki
• [ ] careables/welder.app (wevolver) (apparently has an API)
• [ ] wikifab

[hoijui]

regarding the OSHWA API: that seems very easy to use:

1. get an API token here(very easy!): https://certificationapi.oshwa.org/
2. enter it in the following command instead of TOKEN
3. Run the command, and find the results in the file oshwa_projects.json

Fetch project info from OSHWA:

curl --location --request GET 'https://certificationapi.oshwa.org/api/projects' \
    --header 'Authorization: Bearer TOKEN' \
    | jq > oshwa_projects.json

At the time of this post, it contains 1019 projects, and took ~2s to download. Each one looks about like this:

  {
    "oshwaUid": "US000093",
    "responsibleParty": "Google, LLC",
    "country": "United States of America",
    "publicContact": "thatch@google.com",
    "projectName": "Authboard",
    "projectWebsite": "https://github.com/google/makerspace-auth/",
    "projectVersion": "1.0",
    "projectDescription": "A board that goes in an Authbox to power a Raspberry Pi and handle the actuators for controlling access to tools based on membership or training.",
    "primaryType": "Electronics",
    "additionalType": [
      "Tool"
    ],
    "projectKeywords": [
      "Raspberry Pi Hat",
      "Meta-makerspace Hardware"
    ],
    "documentationUrl": "https://github.com/google/makerspace-auth/tree/master/hardware",
    "hardwareLicense": "Other",
    "softwareLicense": "Apache",
    "documentationLicense": "Other",
    "certificationDate": "2018-01-17T00:00-04:00"
  },

Here the fields are explained: API doc