There is also the #BibTeX metdata standard for software. For 6y already: https://t.co/emCPLPkDS3
Which maybe default to the "misc" data type :-/
But still supports almost all of https://t.co/JtgRrpuZY1 :-)
see https://t.co/1oCfv4XX7t https://t.co/IxnBqKIPAW
@thosjleeper Your paper is important and will certainly attract more citations in the coming years. In decisions on grant proposals, tenure or promotion the R package should also count. A first step would be to ask R to make packages more citable, e.g. adding a DOI https://t.co/7b9lK9Mj5t
Searching for guidance on what software to cite? This comes up in consultations for me and probably for other #datalibs too. See https://t.co/9Npr3rITCI for more info. https://t.co/10BYGOYB3Y
@annemscheel The best guidance on this is https://t.co/6i7Sms7uLZ by @arfon @danielskatz @kyleniemeyer & @force11rescomm: there's no single rule, but in most cases we should cite in our paper the pkgs that our claims depend on, just as we would for papers & books https://t.co/vEDrM0esbP
@atrisovic @PKoppenburg @LHCbExperiment There are indeed software citation principles (https://t.co/Zup1ZuO9My), similar to paper citations. Referring to the #doi would be great, if you have one. Otherwise zenodo might be a good place to get a persistent identifier.