Skip to content

Add a .zenodo.json file and populate it #102

Description

@martin-rdz

Håvard and me discussed on Friday, that we should prepare for a doi publication, which might be already needed by Georg in October.
We would suggest to provide the zenodo meta data already in the .zenodo.json file.

Resources on that here:

An example might look like

{
    "creators": [
        {
            "name": "Carberry, Josiah",
            "orcid": "0000-0002-1825-0097",
            "affiliation": "Brown University",
            "type": "ProjectMember"
        }
    ],
    "contributors": [
        {
            "name": "Lovelace, Ada",
            "type": "Researcher"
        },
        {
            "name": "Babbage, Charles",
            "affiliation": "University of Cambridge",
            "type": "ProjectLeader"
        }
    ],
    "title": "Memory bus simulation scripts",
    "version": "1.8.0",
    "access_right": "open",
    "related_identifiers": [
        {
            "identifier": "https://doi.org/10.5555/666655554444",
            "relation": "isSupplementTo",
            "resource_type": "publication-article"
        }
    ],
    "keywords": [
        "computer science",
        "psychoceramics",
        "journaling filesystems"
    ],
    "license": "mit",
    "upload_type": "software",
    "language": "eng",
    "grants": [
        {"id": "10.13039/501100000780::101122956"}
    ],
    "communities": [
        {"identifier": "simulation-software"}
    ]
}

@HolgerPollyNet How to draw the line between creators/authors and contributors? Funding sources? We can also have that discussion via mail.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions