1. Software Sustainability Institute www.software.ac.uk Dealing with software: the research data issues http://dx.doi.org/10.6084/m9.figshare.1150298 26 August 2014, Dealng with Data Conference Neil Chue Hong (@npch), Software Sustainability Institute ORCID: 0000-0002-8876-7606 | N.ChueHong@software.ac.uk Where indicated slides licensed under Supported by Project funding from

2. Software Sustainability Institute www.software.ac.uk “Re-” is the new black

3. Software Sustainability Institute www.software.ac.uk The Research Cycle Create Test Interpret Publish Revise Paper Data Software Research Outputs Research is a continuous cycle. When we publish we are contributing to the body of knowledge.

4. Software Sustainability Institute www.software.ac.uk Research/Reuse/Reward Cycle Index Identify Cite Reward Create Test Interpret Publish Revise Research Reuse Reuse is also a cycle. We build our research on the work of others. Reward mechanisms should encourage reuse.

5. Software Sustainability Institute www.software.ac.uk The current process Start research Write software Use software Produce results Produce results Publish research paper Release data Release data Release software Release software Which mentions software and data This process is simple but does not reward production or reuse of good software and data. It also has a long contribution cycle.

6. Software Sustainability Institute www.software.ac.uk “Re-”positories Backup|Sharing|Archiving of software

7. Software Sustainability Institute www.software.ac.uk Differing roles, different repositories backup  sharing  archiving Timescales Policy Licensing Ingest Metadata Assurance

8. Software Sustainability Institute www.software.ac.uk Versioning Personal v1 Personal v1 Personal v2 Personal v2 Personal v3 Personal v3 Personal v2a Personal v2a Public v1 Public v1 Personal v3a Personal v3a Personal v2a Personal v2a Public v2 Public v2 Public v3 Public v3 Why do we version? - To indicate a change - To allow sharing - To confer special status Version control systems make this easy and concept of a person and an output are there but not unique

9. Software Sustainability Institute www.software.ac.uk Algorithm Function Program Library / Suite / Package … Granularity What do we define? - Useful units of reuse

10. Software Sustainability Institute www.software.ac.uk What do we choose to identify: - Workflow? - Software that runs workflow? - Software referenced by workflow? - Software dependencies? What’s the minimum citable part? Boundary

11. Software Sustainability Institute www.software.ac.uk Authorship Authorship Which authors have had what impact on each version of the software? Which authors have had what impact on each version of the software? Who had the largest contribution to the scientific results in a paper? Who had the largest contribution to the scientific results in a paper? Can micro-attribution work? Can track author, but not contribution? Can micro-attribution work? Can track author, but not contribution?http://beyond-impact.org/?p=175 OGSA-DAI projects statistics from Ohloh Why do we identify? - To measure - To restrict - To communicate - To include

12. Software Sustainability Institute www.software.ac.uk Code as a Research Object What if you could assign DOIs to code easily? Could we make software more reusable? http://mozillascience.org/code-as-a-research-object-a-new-project/ https://guides.github.com/activities/citable-code/

13. Software Sustainability Institute www.software.ac.uk Write software A better process? Start research Identify existing software Identify existing software Use software Produce results Produce results Publish research paper Adapt/ extend software Release data Release data Release software Release software Publish software paper Publish software paper Publish data paper Publish data paper Which references software and data papers Software and data papers are needed as proxies for rewarding reuse. But it enables a shorter contribution cycle for data and software.

14. Software Sustainability Institute www.software.ac.uk Alternative Metrics

15. Software Sustainability Institute www.software.ac.uk One-click challenge “One-click” archiving of a significant version of software in a code repository to a suitable institutional repository “Suitable” repository:  Clear access / deposit / preservation policy  Adherence to standards  Ability to easily “transfer” in / out  Allows use of appropriate licenses for code  Sustainability of hosting organisation  Ability to monitor, check integrity  Provides permanent unique identifiers Proposing a hackday to make this happen

16. Software Sustainability Institute www.software.ac.uk Summary Software is an important output of the research cycle, and should be rewarded Repositories play an important role in the research cycle, including software But software has specific issues with regards to research data management Tooling is needed to lower barriers to deposit

17. Software Sustainability Institute www.software.ac.uk Further information This presentation:  Slides: http://dx.doi.org/10.6084/m9.figshare.1150298http://dx.doi.org/10.6084/m9.figshare.1150298  Abstract: http://dx.doi.org/10.6084/m9.figshare.1150299http://dx.doi.org/10.6084/m9.figshare.1150299 Where does it go from here: the place of software in digital repositories  http://www.research.ed.ac.uk/portal/en/publications/ where-does-it-go-from-here-the-place-of-software-in- digital-repositories(ab6130c6-aee6-4972-9256-8ea0eb1862c9).html http://www.research.ed.ac.uk/portal/en/publications/ where-does-it-go-from-here-the-place-of-software-in- digital-repositories(ab6130c6-aee6-4972-9256-8ea0eb1862c9).html Software Papers: improving the reusability and sustainability of scientific software  http://dx.doi.org/10.6084/m9.figshare.795303 http://dx.doi.org/10.6084/m9.figshare.795303 Software Sustainability Institute  http://www.software.ac.uk/ http://www.software.ac.uk/ Supported by EPSRC Grant EP/H043160/1