Minimal metadata schemas for science software and code, in JSON and XML.

This is an extention of the work done by @arfon, @hubgit, @kaythaney and others on Code as a Research Object / fidgit. Code as a research object is a Mozilla Science Lab (@MozillaScience) project working with community members to explore how we can better integrate code and scientific software into the scholarly workflow. Out of this came fidgit - a proof of concept integration between Github and figshare, providing a Digital Object Identifier (DOI) for the code which allows for persistent reference linking.

With codemeta, we want to formalize the schema used to map between the different services (Github, figshare, Zenodo) to help others plug into existing systems. Having a standard schema will allow other data archivers and libraries join in. This will help keep science on the web shareable and interoperable!

JSON-LD schema: https://github.com/mbjones/codemeta/blob/master/codemeta.jsonld

Example instance: https://github.com/mbjones/codemeta/blob/master/example-codemeta.json

Comparison of current APIs in this space: https://github.com/mbjones/codemeta/blob/master/crosswalk.csv

We need help formalizing a schema and creating mappings between existing APIs and the proposed schema.

• Send us a pull request if you have any updates to our schema or mappings!
• Take a look at the issue tracker
• Join the discussion!
  • (JSON-LD) Metadata for software discovery
  • How should software be cited?
  • What information is needed to reuse code?

• Code as a Research Object blog posts:

  • Code as a research object: updates, prototypes, next steps
  • What else is needed for code reuse
  • JSON-LD for software discovery, reuse and credit

• JSON-LD.org

• Schema.org