software-native metrics: depsy lessons learned

40
#3amconf Sept 2016 Heather Piwowar and Jason Priem @ImpactStory software-native metrics

Upload: heather-piwowar

Post on 11-Jan-2017

24 views

Category:

Data & Analytics


0 download

TRANSCRIPT

Page 1: Software-Native metrics: Depsy lessons learned

#3amconfSept2016

HeatherPiwowarandJasonPriem@ImpactStory

software-native metrics

Page 2: Software-Native metrics: Depsy lessons learned
Page 3: Software-Native metrics: Depsy lessons learned
Page 4: Software-Native metrics: Depsy lessons learned
Page 5: Software-Native metrics: Depsy lessons learned

depsy.org

Page 6: Software-Native metrics: Depsy lessons learned
Page 7: Software-Native metrics: Depsy lessons learned

10.1038/529115a

Page 9: Software-Native metrics: Depsy lessons learned

depsy.org

Page 10: Software-Native metrics: Depsy lessons learned
Page 11: Software-Native metrics: Depsy lessons learned
Page 12: Software-Native metrics: Depsy lessons learned
Page 13: Software-Native metrics: Depsy lessons learned
Page 14: Software-Native metrics: Depsy lessons learned

launched last November

....what did people think?

Page 15: Software-Native metrics: Depsy lessons learned
Page 16: Software-Native metrics: Depsy lessons learned
Page 17: Software-Native metrics: Depsy lessons learned
Page 18: Software-Native metrics: Depsy lessons learned

some areas we weren’t sure about, but feedback suggested we got right

Page 19: Software-Native metrics: Depsy lessons learned

public profiles for everybody!

Page 20: Software-Native metrics: Depsy lessons learned

an overall score, with equal weighting to 3 components

Page 21: Software-Native metrics: Depsy lessons learned

downloads, log transformed vs ranked, and display for interprebility, with percentiles

Page 22: Software-Native metrics: Depsy lessons learned

pagerankto weight or not to weight, displayed in interpretable way

Page 23: Software-Native metrics: Depsy lessons learned

citations

Page 24: Software-Native metrics: Depsy lessons learned

authorship weighting (committers vs pypi author vs maintainer)

Page 25: Software-Native metrics: Depsy lessons learned
Page 26: Software-Native metrics: Depsy lessons learned

and some big requests

Page 27: Software-Native metrics: Depsy lessons learned

biggest one: pull in new data from GitHub

Page 28: Software-Native metrics: Depsy lessons learned

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 29: Software-Native metrics: Depsy lessons learned

outstanding challenge:

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

Page 30: Software-Native metrics: Depsy lessons learned

future plans

Page 31: Software-Native metrics: Depsy lessons learned

above, plus better text mining

Page 32: Software-Native metrics: Depsy lessons learned

integrate better with libraries.io

Page 33: Software-Native metrics: Depsy lessons learned

tighter integration with Impactstory

Page 35: Software-Native metrics: Depsy lessons learned
Page 36: Software-Native metrics: Depsy lessons learned
Page 37: Software-Native metrics: Depsy lessons learned
Page 38: Software-Native metrics: Depsy lessons learned

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

more Depsy details:

Page 39: Software-Native metrics: Depsy lessons learned

thoughts?

tweet @depsy_org or via github issue.

Page 40: Software-Native metrics: Depsy lessons learned

thanks!