Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Linking Software: citations, roles, references and more


Published on

Linking Software: citations, roles, references and more - Neil Chue Hong, Software Sustainability Institute at Repository Fringe 2015

Published in: Education
  • Be the first to comment

  • Be the first to like this

Linking Software: citations, roles, references and more

  1. 1. Software Sustainability Institute Linking software: Citations, roles, references,and more Repository Fringe 2015, Edinburgh, 3-4 August 2015 Neil Chue Hong (@npch), Software Sustainability Institute ORCID: 0000-0002-8876-7606 | Institute Software Sustainability Unless otherwise indicated these slides licensed under Supported by Project funding from
  2. 2. Software Sustainability Institute Authorship Lifecycle Identif yCite Reuse Research Index Papers, data, software all research outputs of a continuous cycle. With software, technology makes it easier to track, but not reward. We cannot separate papers, data and software when we release research.
  3. 3. Software Sustainability Institute The current process Start research Write software Use software Produce results Publish research paper Release data 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.
  4. 4. Software Sustainability Institute Write software A better process? Start research Identify existing software Use software Produce results Publish research paper Adapt/ extend software Release data Release software Publish software paper Publish data paper Whichreferences softwareanddatapapers Software and data papers are needed as proxies for rewarding reuse. But it enables a shorter contribution cycle for data and software.
  5. 5. Software Sustainability Institute What do we choose to identify: - Workflow? - Software that runs workflow? - Software referenced by workflow? - Software dependencies? What’s the minimum citable part? Boundary
  6. 6. Software Sustainability Institute Algorithm Function Program Library/Suite/Package … Granularity
  7. 7. Software Sustainability Institute Versioning Personal v1 Personal v2 Personal v3 Personal v2a Public v1 Personal v3a Personal v2a Public v2 Public v3 Why do we version? - To indicate a change - To allow sharing - To confer special status
  8. 8. Software Sustainability Institute AuthorshipAuthorship • Which authors have had what impact on each version of the software? • Who had the largest contribution to the scientific results in a paper? OGSA-DAI projects statistics from Ohloh
  9. 9. Software Sustainability Institute Moving forwards • Making software citable  At “package level” (is this the right granularity?) • GitHub -> Zenodo / FigShare / Insititution Repo    Principles for citation • Force11 Software Citation Working Group   Making roles clearer • Project Credit  • Contributor Badges   Code as a Research Object • Defining minimal metadata  • How do we ensure this is “linked up” with RepoFringe community?
  10. 10. Software Sustainability Institute Find out more about the SSI • Community Engagement (Lead: Shoaib Sufi)  Fellowship Programme  Events and Workshops • Consultancy (Lead: Steve Crouch)  Open Call for Projects / Collaborations  Software Evaluation • Policy and Publicity (Lead: Simon Hettrick)  Case Studies / Policy Campaigns  Software and Research Blog • Training (Lead: Aleksandra Pawlik)  Software Carpentry (300+ students/year)  Guides and Top Tips • Journal of Open Research Software (Editor: Neil Chue Hong) • Collaboration between universities of Edinburgh, Manchester, Oxford and Southampton Supported by EPSRC Grant EP/H043160/1, and EPSRC/ESRC/BBSRC grant EP/N006410/1