Dear Rémi, All the Force11 and RDA discussions I’ve been a part of have focused on CodeMeta as the machine-readable citation format (although the Force11 principles should apply to any jsonld format). We use CodeMeta at Caltech as part of our software preservation workflow (basically a custom version of Zenodo), but unfortunately Zenodo doesn’t currently support CodeMeta for metadata mapping. Hopefully that will change soon!
On the recommendation front - adding a CodeMeta file<https://github.com/caltechlibrary/ames/blob/master/codemeta.json> is a great way to be ready for the future. There is some software that can generate CodeMeta from Python packages (https://github.com/proycon/codemetapy) or R (https://github.com/ropensci/codemetar). Best, Tom Morrell | Research Data Specialist | Caltech Library<https://library.caltech.edu> Mail Code 2-32, Pasadena CA 91125 | 626-395-3827 | data.caltech.edu<https://data.caltech.edu> On Apr 8, 2019, at 1:27 PM, Rémi Rampin <[email protected]<mailto:[email protected]>> wrote: 2019-04-08 16:08 UTC-04, Terri Yu <[email protected]<mailto:[email protected]>>: I forgot to say that yes, I am the owner of the GitHub repo and I recently got a request from a scientist asking how they could cite my software. That's what prompted this question. This is software that is under development, so I don't have a paper and I don't want to spend a lot of time maintaining citations. It sounds like generating a DOI via Zenodo is the easiest and most common way to take care of this issue, if your repo is on GitHub ? Also note the nice CiteAs tool that can find citations automatically for repository or website: http://citeas.org/. I would recommend adding a CITATION.txt to your repository (or a CodeMeta file<https://codemeta.github.io/user-guide/>, but that is more involved) next to your LICENSE.txt, listing the main contributors of the project and your preferred citation if any (if you have a paper associated with it, or your Zenodo DOI). Once integrated, Zenodo will automatically archive your code and create a new DOI (or rather, a new version of the same record) every time you create a release on GitHub, so this is really a setup & forget solution that you shouldn't have to worry about down the road. I am skeptical of the FORCE11 principles, that recommend yet another JSON-LD format, which seems to have much lower adoption than CodeMeta. Best -- Rémi The Carpentries<https://carpentries.topicbox.com/latest> / discuss / see discussions<https://carpentries.topicbox.com/groups/discuss> + participants<https://carpentries.topicbox.com/groups/discuss/members> + delivery options<https://carpentries.topicbox.com/groups/discuss/subscription> Permalink<https://carpentries.topicbox.com/groups/discuss/T33d60669d32ac1d7-M8789ba37353cfc9184721247> ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/T33d60669d32ac1d7-Md943313cd0cda367e0b7b2ca Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
