1. Items can be only accepted if they refer to a JSD publication. Authors can, but are not required to, transmit the data when submitting their contributions. If data is submitted with the article, it will not be publicly available until the paper is accepted. Meanwhile, reviewers will be provided confidential access to the data during the review process.

  2. Eligible depositors must deposit metadata for all items that are deemed to meet the FAIR principals. i.e. sufficient metadata and content that provide the end-users with a resource that is Findable Accessible Interoperable and Reusable. See https://www.go-fair.org/fair-principles/ to become familiar with FAIR principals.

  3. Only items with an end-usage licence will be accepted - where possible these licences should be as permissive as possible to ensure that the resource is as 'open as possible, as closed as necessary' for use. CC0, CC-BY-4.0, CC-BY-SA-4.0 for data and MIT, BSD, GPL for code are suggested.

    • While the CC0 license grants unrestricted use, modification, and distribution of creative works without requiring any attribution, the CC-BY-4.0 license requires attribution but allows for non-commercial and commercial use, modification, and distribution, whereas the CC-BY-SA-4.0 license requires attribution and allows for commercial and non-commercial use, modification, and distribution, but also mandates that any derivative works be published under the same license. See https://creativecommons.org for more information about open data licenses.

    • While the MIT license grants permission to use, modify, and distribute software without requiring any attribution or warranty, the BSD license requires a disclaimer and a permission notice, but also grants permission to use, modify, and distribute software without requiring any attribution or warranty, whereas the GPL license requires that any derivative works be published under the same license, and also mandates that users share any modifications made to the original software. See https://opensource.org/licenses for more information about open code licenses.

  4. Data should be available without embargo.

  5. If no ORCID is listed, the name and surname and email addresses of contributors must be specified in the Description and Zenodo metadata. The list of contributors may be different from the one of the corresponding JSD paper.

  6. The validity and authenticity of the content of submissions is the sole responsibility of the depositor.

  7. If the repository receives proof of copyright violation, the relevant item will be removed immediately.

  8. The description of the submitted work must be sufficiently detailed. References to external articles or to other external resources are not sufficient descriptions.

  9. The submitted work must include a clearly identifiable README file, typically in the root directory. This is not required for works consisting in one single document (ex. publications, posters, or presentation slides). The README file contains detailed information about the work creation (authors, time, place, methodologies…), content (file organization and naming, formats, relevant standards…), sharing and access, etc.  All these information should also appear in the Zenodo metadata.

  10. The title must refer to the JSD paper. The JSD Community curators can ask the submitter to modify the title accordingly.

  11. Any personal and sensitive data must be anonymized.

  12. Grants can be acknowledged using "Funding/Grants" fields.

  13. The submitted work should be been cleaned up (e.g., there are no temporary files, no unnecessary empty files or folders, no superfluous file versions, etc.).

  14. If possible, files are available in open formats. If proprietary formats are present, the work also includes versions of the files converted to open formats, with the least possible loss of information. The files shared as inputs for proprietary or open software must include clear information about the software version used.

  15. The format of the data files and associated documentation are revised by the JSD Community curators in a validation process without dealing with the contents. 

  16. The JSD Community curators can ask the submitter to modify and/or complete metadata, request changes, additions or further information. 

  17. The JSD Community curators can reject or withdraw, even after publication, a dataset if considered not appropriate.