@jnuneziglesias You imply that software citations are of papers about software, rather citing the software itself (and all the contributors at any time) - see https://t.co/GZE0jI7onh and https://t.co/sPu59ubqmd for work trying to change this (1/2)
@choldgraf @story645 Short answers: 1) it’s complicated; 2) maybe https://t.co/GZE0jI7onh will help; 3) we’re working on it in https://t.co/sPu59ubqmd; 4) see some posts in https://t.co/S8PRPl9l2g for discussion
@albz_marocchino @jeroenbosman @coenen_pieter @CorneelVDL @robinnkok @burkhard_mstern @ResearchGate @DOAJplus @ZENODO_ORG Great points. Do you know the Software Citation Principles? Things like this can really help here https://t.co/CCTjgj2lHc
@jsamwrites We wanted to put some of these differences in https://t.co/GZE0jI7onh but the reviewers said we needed to cite something, so we came up with more details and put them in this preprint, then cited it :)
@IanCal @amuellerml @KyleCranmer @jeremyphoward @matplotlib @tacaswell @NSF @thisgreyspirit @npch I don’t think this can be done just by NSF, but we’re working on it in the larger community via https://t.co/sPu59ubqmd Also see https://t.co/GZE0jI7onh
@Magda_Skipper @naturemethods It's too bad the authors are not aware of the @force11rescomm Software Citation Implementation Working Group (which created https://t.co/GZE0jI7onh) and is now working with publishers and repositories.
@rgfitzjohn @benmarwick @rmazor @TrevorABranch @hadleywickham @arfon @kyleniemeyer @force11rescomm @annemscheel @rOpenSci In the same paper (https://t.co/GZE0jI7onh), we say
to just cite what you directly used, and try to get those packages to cite what they use, etc., leading to transitive credit. ie, when standing on the shoulders of giants, cite your giant, who has cited their giant, etc. https://t.co/DgJHx2yykN