capturing the impact of software AAS 2017

35
aas January 2017 Heather Piwowar @depsy_org capturing the impact of software

Transcript of capturing the impact of software AAS 2017

Page 1: capturing the impact of software AAS 2017

aasJanuary2017

HeatherPiwowar@depsy_org

capturing the impact of software

Page 2: capturing the impact of software AAS 2017
Page 3: capturing the impact of software AAS 2017
Page 4: capturing the impact of software AAS 2017
Page 5: capturing the impact of software AAS 2017
Page 6: capturing the impact of software AAS 2017

depsy.org

Page 7: capturing the impact of software AAS 2017
Page 8: capturing the impact of software AAS 2017

search all of CRAN and PyPI

Page 9: capturing the impact of software AAS 2017
Page 10: capturing the impact of software AAS 2017
Page 11: capturing the impact of software AAS 2017

three componentsof impact

Page 12: capturing the impact of software AAS 2017
Page 13: capturing the impact of software AAS 2017
Page 14: capturing the impact of software AAS 2017
Page 15: capturing the impact of software AAS 2017

an overall score, with equal weighting to 3 components

Page 16: capturing the impact of software AAS 2017
Page 17: capturing the impact of software AAS 2017
Page 18: capturing the impact of software AAS 2017

weighted contributorship

Page 19: capturing the impact of software AAS 2017

open source, open data

Page 20: capturing the impact of software AAS 2017

integrated at impactstory.org

Page 22: capturing the impact of software AAS 2017
Page 23: capturing the impact of software AAS 2017
Page 24: capturing the impact of software AAS 2017
Page 25: capturing the impact of software AAS 2017

launched last year.

....what did people think?

Page 26: capturing the impact of software AAS 2017
Page 27: capturing the impact of software AAS 2017
Page 28: capturing the impact of software AAS 2017
Page 29: capturing the impact of software AAS 2017

some big requests

Page 30: capturing the impact of software AAS 2017

expected:

more package library systems (esp bioconductor)

more languages (import detection complexity)

more platforms like bitbucket (esp to get commit history for authorship)

better deduplication (no orcid, alas)

things that aren't on a version control system at all (not happening)

Page 31: capturing the impact of software AAS 2017

outstanding challenge:

deciding what is a research package in python(important b/c refset matters)

future plans:

more advanced text mining

Page 32: capturing the impact of software AAS 2017

https://github.com/Impactstory/depsy-research/blob/master/introducing_depsy.md

more Depsy details:

Page 33: capturing the impact of software AAS 2017

10.1038/529115a

Page 34: capturing the impact of software AAS 2017

thoughts? tweet @depsy_org or via github issue.

Page 35: capturing the impact of software AAS 2017

thanks!