Use cases for the big codemeta.json

[maelle]

(and/or its complemented version cf #19 #18)

The main use of this repo is to provide JSON for ropensci.org/packages, JSON that is quite minimal.

But there might be use cases for the big codemeta.json and/or its complemented version.

• What are the biggest packages?
• Most common dependencies?
• ?

For blog posts/tech notes and what else? A dashboard? Reports?

[sckott]

what exactly is "big codemeta.json"?

[maelle]

https://github.com/ropensci/roregistry/blob/ex/codemeta.json which is mostly only the output of codemetar::create_codemeta().

• It is transformed into a JSON for the packages page https://github.com/ropensci/roregistry/blob/ex/registry2.json using its own info + info from the folder (to deduce the GitHub organization in case URL is wrong in DESCRIPTION)
• potentially it could be complemented with other info (cf cf Field suggestion: latest commit to master at the time of registry building #19 Field suggestion: latest CRAN release #18) to become a really big JSON.

[sckott]

Yeah, that'd be neat to use it for other things.

[maelle]

Please list any application idea you have when you get a chance, to help decide whether to publish the raw big codemeta or a complemented codemeta 🙂

[maelle]

Cf also ropensci/codemetar#118 (comment) cc @cboettig (I promise to repair the big codemeta.json soon 😉 )