Archive published snapshots of invalid-blocks on Zenodo so the dataset has a persistent DOI and individual releases can be cited exactly.
Follow the stale-blocks model: create a date-tagged GitHub release when main has changed since the previous release, let the Zenodo GitHub integration archive it, and document the concept and version DOIs in the README. The initial setup needs to enable this repository in Zenodo and publish one release before the DOI badge can be added.
Add explicit citation metadata for the dataset's creators, title, licence and keywords. The first archive should also be checked to ensure Zenodo classifies it as a dataset rather than software.
Archive published snapshots of
invalid-blockson Zenodo so the dataset has a persistent DOI and individual releases can be cited exactly.Follow the
stale-blocksmodel: create a date-tagged GitHub release whenmainhas changed since the previous release, let the Zenodo GitHub integration archive it, and document the concept and version DOIs in the README. The initial setup needs to enable this repository in Zenodo and publish one release before the DOI badge can be added.Add explicit citation metadata for the dataset's creators, title, licence and keywords. The first archive should also be checked to ensure Zenodo classifies it as a dataset rather than software.