Should we put the schemas of this repo as artefacts on Zenodo?

[4lm]

Hi all,

I have a question I would like to discuss with you! Should we put the schemas of this repo as artefacts on Zenodo?

Right now for example we might change the repo and modules name of this project #20, we also might switch to a different naming for version folders and version naming of constants #21. Maybe there will be other changes in the future? And I'm quite sure, if this project will last, this will be the case ...

So to constantly put the schemas of this repo as artefacts on Zenodo could be the way to go! This would give us updatable resources on fixed URLs with version history, checksums and fixed DOIs (which IMO the scientific community would love for citation). This would IMO also help our schemas to establish them as a standard.

What do you think?

[4lm]

We could also automate this process with a little CLI script: https://developers.zenodo.org/

[Ludee]

I think your idea is good! Not just for the json schema, also to archive the metadata version (template and example) as well. I have many broken links because we moved and renamed the metadata too often. A proper DOI would be useful!

[jh-RLI]

@Ludee If we are still plan on uploading the metadata to Zendoo? If so we should:

1. think about which files are all uploaded there and
2. we should create a kind of release pipeline, otherwise the release will be confusing and maybe incomplete in the future.

[Ludee]

This will be done after the 2.0 release.