ncn-github-oa

How to deal with NCN Open Access rules and GitHub repositories

https://github.com/filipspl/ncn-github-oa

Science Score: 36.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
    Links to: zenodo.org
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.7%) to scientific vocabulary

Keywords

ncn open-access zenodo

Keywords from Contributors

hack molecular-interactions molecular-modeling pymol-plugin bruteforce
Last synced: 6 months ago · JSON representation

Repository

How to deal with NCN Open Access rules and GitHub repositories

Basic Info
  • Host: GitHub
  • Owner: filipsPL
  • License: cc0-1.0
  • Default Branch: main
  • Homepage:
  • Size: 233 KB
Statistics
  • Stars: 5
  • Watchers: 2
  • Forks: 1
  • Open Issues: 0
  • Releases: 3
Topics
ncn open-access zenodo
Created about 3 years ago · Last pushed about 2 years ago
Metadata Files
Readme Funding License Citation Zenodo

README.md

Guide how to link GitHub repositories with Zenodo to obtain a DOI

We originally created this guide to provide hints on how to deal with the rules imposed by our grant agency, the National Science Center (NCN), Poland, regarding publishing in Open Access, GitHub repositories and the need for permanent DOIs. But don't hesitate to use it if you need to link your GitHub repositories to Zenodo for DOI for any other purpose.

DOI cffconvert

Notice of Non-Affiliation and Disclaimer: We are not affiliated, associated, authorized, endorsed by, or in any way officially connected with the GitHub, NCN, or Zenodo.

How to

  1. Add a LICENSE file to your GitHub repository as we did here, if you don't have one. You can read more about adding a license to the GitHub repository here.

  2. In your repository, create a CITATION.cff file with a citation details.

    • Use this wizard to create a CITATION.cff file, basing on ours as an example (alternatively, you can customize our CITATION.cff file, but it is more convenient to use the wizard).
      :warning: Add the DOI identifier field and temporarily put there any DOI, you will later change it to the DOI obtained via Zenodo for your repository.
    • The format of the file is YAML
    • License: our grant agency, NCN, requires the datasets to be published under the CC0 1.0 licence. What about software? :question:
    • After commit, the citation tool will be available on the right repository panel:
  3. In your repository, create a .zenodo.json file. You can edit the this sample one here.

    • Add your grant number in the field "notes"
      :warning: Polish grants do not work with the dedicated field "grants/funding"
    • More information on the format and fields are available here
    • The format of the file is json
    • license: our grant agency requries the datasets to be licensed under CC0 1.0 or CC BY 4.0 (NCN’s Open Access Policy was recently relaxed in certain cases, see details at NCN website.


📢 At this point, you should make your repository publicly available.


  1. Connect Zenodo to GitHub (or vice versa) as described here.

    • Your GitHub settings will be available at https://zenodo.org/account/settings/github/.
    • Enable the integration by switching the repository on:
    • Go to GitHub and make your first release (or pre-release):

    • At this point your repository will be visible at the appropriate Zenodo page. Please note the status - green means ok, orange means processing, red means error
    • At this point you can add a repository DOI identifier issued by Zenodo to the CITATION.cff file (see above). See below on how to get the universal DOI
  2. New DOI is generated every time you do a release (or pre-release) of your repository. To get the one-universal DOI for your repository, at the Zenodo page:

    • Move to the the GitHub panel
    • Select your repository from the Enabled Repositories panel
    • Click DOI for any of the releases, you will be redirected to the Zenodo page of your published repository
    • In the right panel, look for Cite all versions? You can cite all versions by using the DOI...:
      > NOTE: You can also add a cool zenodo badge to your repository: DOI

Additional remarks and optional steps:

  1. You may want to enable GitHub actions to check validity of CITATION.cff, as is done in this repository (.github/workflows/cffconvert.yml). You will get a cool badge: cffconvert
  2. When the paper is published and has DOI assigned, you may add this info to CITATION.cff file in identifiers section.

Unanswered questions

  1. The GitHub repository has an unique DOI, and the following up, peer-reviewed scientific paper also has its own DOI. We (the scientists) want to get citations from the scientific paper. Questions:
    • shall we require others to cite both GitHub repo and scientific paper? Or only the paper?
    • if both are cited, can we merge both citations (eg in Google Scholar)?

Discussion

Feel free to discuss these matters on the Discussions page.

Owner

  • Name: filips
  • Login: filipsPL
  • Kind: user
  • Location: Warsaw, Poland
  • Company: @thervira @genesilico

- computer aided drug design + medicinal chemistry - python programming, web devel - ML - QSAR, tox prediction - :swimmer: :bicyclist: :runner:

GitHub Events

Total
Last Year

Committers

Last synced: 8 months ago

All Time
  • Total Commits: 17
  • Total Committers: 3
  • Avg Commits per committer: 5.667
  • Development Distribution Score (DDS): 0.471
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Filip Stefaniak s****k@g****m 9
Natalia Szulc n****c@i****l 7
ImgBotApp I****p@g****m 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 8 months ago

All Time
  • Total issues: 0
  • Total pull requests: 6
  • Average time to close issues: N/A
  • Average time to close pull requests: about 13 hours
  • Total issue authors: 0
  • Total pull request authors: 2
  • Average comments per issue: 0
  • Average comments per pull request: 0.17
  • Merged pull requests: 6
  • Bot issues: 0
  • Bot pull requests: 1
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • n-szulc (5)
  • imgbot[bot] (1)
Top Labels
Issue Labels
Pull Request Labels

Dependencies

.github/workflows/cffconvert.yml actions
  • actions/checkout v2 composite
  • citation-file-format/cffconvert-github-action 2.0.0 composite