Software reuse, repurposing and reproducibility

1. Group 2.6
Software Reuse, Repurposing and Reproducibility27/2/2015

2. Team
» Ian Gent, St Andrews
› founder of recomputation.org
» Catherine Jones, STFC
› SoftPres, SCAPE
» Chris Greenough, STFC
› Lead of EPSRC Software Engineering Support Centre
http://www.softeng-support.ac.uk/about/
» Brian Matthews, STFC
› Significant Properties of Software, SoftPres
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 2

3. Scope and Gap
»Software underpins the research process enabling
analysis and simulation of data
»Need to keep it useable over the long term
»Two key aspects are:
› Uniquely identifying software
› Keeping software in a runnable state
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 3

4. Impact and Benefits 1
»Location of software through metadata associated with
persistent identifier
› Increased reuse potential through easier to find
› Better use of funding through re-use
› Credit for re-use through citation
»Improve the research record & increase quality of
software
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 4

5. Impact and Benefits 2
»Runnable state
› Enables reproducibility of past research
› Enables reuse underlying that research
› Enables repurposing of software for new research
»Synergy between persistent identifier and runnable state
› Discoverability is Runnability!
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 5

6. Sustainability
»Recommendations presented to DataCite for uptake in
the community
»Open Source software
»Seek further funding for development into a service
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 6

7. Outputs, milestones and indicators of success
Outputs Milestones Success Indicators
Guidelines for assigning
persistent identifiers to
software and linkage to
runnable state
M2 – draft for external
review
M3 – first version
Document produced and
externally reviewed
Dissemination July 2015 Presentation at DataCite User
Group meeting
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 7

8. Outputs, milestones and indicators of success
Outputs Milestones Success Indicators
Technical Scoping &
potentially prototyping
M6 Document produced and
externally reviewed
Building DOI allocation
service for software: landing
pages infrastructure
M7 Landing pages produced, using
test DOI service
“play-it” infrastructure M13 User interface for uploading
build versions
Dissemination Consider Community
workshop
Attendance numbers
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 8

9. Funding
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 9
Phase I Unofficial
Costs
Staffing (St Andrews & STFC) – aiming at 10 days St
Andrews & 15 days STFC
St Andrews ??
STFC c8K
Travel & Subsistence
(1 working meeting at partner site, travel to Jisc
meeting and travel to DataCite meeting)
2300
APC 1200
Plan ahead for Phase II Summer Internship at St
Andrews
? 3,000
TOTAL 14,500 + St
Andrews staffing

10. Funding
07/04/2015 Title of presentation (Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide) 10
Phase II & III
Staffing (St Andrews & STFC) : developers – approx 6PM
Travel & Subsistence : partner meeting and outreach
Cloud Resources: Probably some Azure time. Possibly donated from
recomputation or separate request to MS Research