You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One common issue with citing code in papers is that authors of code do not always provide clear instructions on how to cite the software. Sometimes it's a zenodo doi pointing to a webpage or a github repo, sometimes a paper, sometimes the user guide, sometimes a proceedings. I suggest we try to systematically list the recommended citation for each software.
The text was updated successfully, but these errors were encountered:
One common issue with citing code in papers is that authors of code do not always provide clear instructions on how to cite the software. Sometimes it's a zenodo doi pointing to a webpage or a github repo, sometimes a paper, sometimes the user guide, sometimes a proceedings. I suggest we try to systematically list the recommended citation for each software.
yeah I think this makes sense! Thank you, @pkoppenb
I think we should float this repo as much as possible and ask the relevant authors to add their citations. I think this will otherwise need a massive effort. Plus, it needs to be kept updated. Sometimes every new version of the code comes with a new reference. This can't be kept up to date by a few people.
One common issue with citing code in papers is that authors of code do not always provide clear instructions on how to cite the software. Sometimes it's a zenodo doi pointing to a webpage or a github repo, sometimes a paper, sometimes the user guide, sometimes a proceedings. I suggest we try to systematically list the recommended citation for each software.
The text was updated successfully, but these errors were encountered: