This pull request includes a draft .zenodo.json file generated by a script (also included). Comments:
creators: I listed Mylène and myself (the package.contributors with role: author).
contributors: I listed Guillem and Lander (the package.contributors with role: curator) as type: DataCurator and data contributors (the package.contributors with role: contributor) as type: DataCollector.
grants: If the work was supported by a grant from one of the listed authorities, it can/should be listed here.
As introduced in #47, Zenodo can be linked to a GitHub repository for automatic publishing on each GitHub release (https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content). By default, Zenodo infers metadata from the repository, but also allows the metadata to be customized with a
.zenodo.jsonfile (https://developers.zenodo.org/#add-metadata-to-your-github-repository-release) that must follow their Deposit metadata format (https://developers.zenodo.org/#representation).This pull request includes a draft
.zenodo.jsonfile generated by a script (also included). Comments:creators: I listed Mylène and myself (thepackage.contributorswithrole: author).contributors: I listed Guillem and Lander (thepackage.contributorswithrole: curator) astype: DataCuratorand data contributors (thepackage.contributorswithrole: contributor) astype: DataCollector.grants: If the work was supported by a grant from one of the listed authorities, it can/should be listed here.communities: If the record should be listed in any of the existing Zenodo "communities". For example this one for SCNAT: https://zenodo.org/communities/oliviazwygartFinally, once the the paper is published, it should be listed under
related_identifiers, with relationisDescribedBy. See #54.