Why and How to Cite Software (and Get Your Software Cited Too)
summary
Shows concrete evidence that software is under‑cited and gives practical fixes: Howison and Bullard 56% uncited and breakdowns of 286 mentions; demonstrates index behavior with Pandas 17,000 paper citations 1,001 software citations; explains versioning, DOIs and Zenodo deposition and the GitHub–Zenodo integration; lists FORCE11 software citation elements and formats; shares team experience with scores 125,000 PyPI downloads 26 paper citations 2 software DOIs and reports that adding citation metadata provably increases software citations.
AI-written summary · about
chapters (20)
- 0:00Software citation importance
- 1:30Why citation is missing
- 3:13What to cite in research
- 5:23Benefits of citing software
- 6:05Case study: scores software citations
- 7:07Zenodo for software
- 9:15Challenges in citation formatting
- 10:17FORCE11 software citation
- 12:24Proper software citation examples
- 13:06Version info in citations
- 14:51Persistent IDs vs URLs
- 15:52Finding what to cite
- 17:17Citing software with no instructions
- 18:19Make software easier to cite
- 19:24Publishing software paper
- 20:27Clear citation instructions
- 21:31Lessons from scores project
- 22:53Q&A: Dependencies and scope
- 24:16Q&A: Citing versions
- 25:42Q&A: Incentives for engineers
related talks
29mCitation is Collaboration: Software Recognition in Research and Industry
37mHow do you measure 'public good' in open source and beyond?
01h 03mKeynote: Scientific Computing and the Gateway to Open Source
16mKeynote: Back to Security Basics: Evaluating, Consuming, and Contributing Open Source Software
42mFederal Source Code Study: An Analysis of Publishing the People's Code
36mBuilding the Digital Commons for Software Supply Chain
41mThe unreasonable effectiveness of public work
27mDesign Your Open Source Project