Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CFFs once Zenodo DOIs have been minted for archived versions #70

Open
jbstatgen opened this issue Jan 30, 2024 · 2 comments
Open
Assignees
Labels
Technical Issues strictly technical in nature, unrelated to the content of the standard itself.

Comments

@jbstatgen
Copy link
Collaborator

From citation.CFF:

identifiers:
  - type: "doi"
    value: "10.xxxxxx"
    description: "DOI for this repository archived in Zenodo"
repository-code: "https://github.com/tdwg/ltc"
url: "https://github.com/tdwg/ltc/wiki"

citation_release.CFF:

identifiers:
  - type: "doi"
    value: "10.xxxxxx"
    description: "DOI for this repository archived in Zenodo"
repository-code: "https://github.com/tdwg/ltc/"
url: "https://tdwg.github.io/ltc/"

The CFF standard allows the association of identifiers with the publication or published resource, e.g. a DOI.
We thought it sensible, once LtC is ratified to archive the release version and a current repository snapshot on Zenodo. This apparently will generate a DOI for each of them.
Once this is done, the CFFs should be updated with the DOIs (currently a placeholder is present).

Alternatively, the identifier keyword should be removed from the CFFs.

@ben-norton ben-norton added the Technical Issues strictly technical in nature, unrelated to the content of the standard itself. label Feb 20, 2024
@magpiedin
Copy link
Contributor

magpiedin commented Jun 13, 2024

@jbstatgen -- We'll follow up on this (happy to help!) at the July monthly LtC call, after the term IRI & versioning is worked out - #85 (& related issues)

@magpiedin
Copy link
Contributor

mini-update:

  • whenever the LtC maintenance group needs to update its author list, we will update the CFF
  • @ben-norton is updating stadocgen to pull from that / generate the authors YAML file from CFF

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Technical Issues strictly technical in nature, unrelated to the content of the standard itself.
Projects
None yet
Development

No branches or pull requests

3 participants