...
How to break the topic down
- How to record information to describe a software project and its contributors
- Projects going on to create systems for software citation: to record, to read, to collect, etc. Get input from different projects. What are their research questions/interim findings. We have CodeMeta, CFF, CiteAs.
- What information do journals and repositories want when submitting software
- How can citing be more useful for researchers. Is there enough information to be useful for research publication/software readers/users
- The Future: Can software cited be fully available in a – validated, CI, packet managed, dependency managed, virtualised way – so that it can be retrieved or sun live. e.g, Jupyter https://jupyter.org/ and Binder to republish https://mybinder.org
- Note: we need clear guidelines or pointers to this info, for: software makers, journal submissions of software, and academic writers or scholarly literature wanting to cite software.
- Top three info sources in each area: journals, papers, software citation software project, working groups and organisations
- Journals do give guidance
- Style guides give guidance
- Citation managers have software included as a designated source
Community: to engage
- #oscibar https://etherpad.wikimedia.org/p/oscibar2018_session10
- Zenodo
- CodeMeta https://github.com/codemeta/codemeta
- CFF Citation File Format https://citation-file-format.github.io/
- CiteAs http://citeas.org/about http://impactstory.org/
- Force11 working group running through https://github.com/force11/force11-sciwg/
- Wikidata
- Software Heritage
- Katrin Leinweber TIB - Software Carpentry
- de-RSE (Research Software Engineers) Group (German group): http://www.de-rse.org/en/
- Software Heritage
- Sustainable Software for Science: Practice and Experiences (WSSSPE) https://twitter.com/WSSSPE
...