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

Add CITATION.cff file #78

Merged
merged 5 commits into from
Mar 18, 2024
Merged

Add CITATION.cff file #78

merged 5 commits into from
Mar 18, 2024

Conversation

pjbriggs
Copy link
Member

@pjbriggs pjbriggs commented Feb 6, 2024

Adds a CITATION.cff to the Github repository, which will then make a "Cite this repository" option on the repository front page.

See:

Initial version produced using the tool at https://citation-file-format.github.io/cff-initializer-javascript/

@pjbriggs
Copy link
Member Author

pjbriggs commented Feb 8, 2024

There are a couple of things I'm unsure of:

  • How to address the "chicken-and-egg" issue of including the automatically-generated DOI created by Zenodo when it ingests a release, within the source code archive for that release
  • It appears that the citation information generated from the CITATION.cff file points to the Github repository, but my understanding was that it was preferable to reference DOIs (which should be permanent) over Github repos (which may be transient)

Looking at the example within the Turing Way documentation at https://the-turing-way.netlify.app/communication/citable/citable-cff#cm-citable-cff I see that Zenodo actually generates a DOI for all archived versions (what they call the "concept" DOI, see https://zenodo.org/help/versioning).

Since the CITATION.cff format includes a top-level doi: field (see e.g. https://github.com/citation-file-format/citation-file-format/blob/main/CITATION.cff) one solution might be to use the concept DOI, however this is not recommended by Zenodo as they prefer the version-specific DOIs (see the "versioning" document linked previously). Also it's not clear if doi: overrides repository-code: (which I assume is being used when generating the reference).

There is a practical reason why this is important, as I would like to also update the citation information within the documentation (currently this also points to the Github repository).

@pjbriggs pjbriggs linked an issue Feb 8, 2024 that may be closed by this pull request
@pjbriggs
Copy link
Member Author

It's still not clear how best to populate the citation file so for now I'm going to add the version that cites the GitHub repository, and modify the citation information printed by the program and that in the documentation to match.

@pjbriggs pjbriggs closed this Mar 18, 2024
@pjbriggs pjbriggs reopened this Mar 18, 2024
@pjbriggs pjbriggs merged commit 4121e24 into devel Mar 18, 2024
12 checks passed
@pjbriggs pjbriggs deleted the add-citation-cff branch March 18, 2024 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make RnaChipIntegrator versions citable via Zenodo
1 participant