17
@ontowonka Credit where credit is due: acknowledging all types of contributions COASP 2016 Melissa Haendel

Credit where credit is due: acknowledging all types of contributions

Embed Size (px)

Citation preview

Page 1: Credit where credit is due: acknowledging all types of contributions

@ontowonka

Credit where credit is due: acknowledging all types of

contributions

COASP 2016Melissa Haendel

Page 2: Credit where credit is due: acknowledging all types of contributions

What *IS* “success”?

Page 3: Credit where credit is due: acknowledging all types of contributions

https://goo.gl/b60moX

It’s not always what you see

Page 4: Credit where credit is due: acknowledging all types of contributions

What is attribution???

Page 5: Credit where credit is due: acknowledging all types of contributions

Over 1000 authors

Page 7: Credit where credit is due: acknowledging all types of contributions

Many contributions don’t lead to authorship

NIH BD2K co-authorship

D.EichmannN.Vasilevsky

> 20% key personnel are not profiled using publications

Page 8: Credit where credit is due: acknowledging all types of contributions

Some contributions are anonymous

Data depositionImage credit: http://disruptiveviews.com/is-your-data-anonymous-or-just-encrypted/

Anonymous review

Page 9: Credit where credit is due: acknowledging all types of contributions

Image by Julie McMurry 2012

An ecosystem of contributions

Awarded to

Awards

Awards Awards

Emplo

ys

Employs

Employs

Creates

Creates

Uses

Described in

Contained inRecognizes product ofCreates

Authors

R01 AI 144578

Institution X

Institution Y

R21 AI 045678 Researcher A

Researcher B

Researcher C

Ab 256

Protocol 245

Mouse 567

GeneID987654

Instrument 123

PMID 45678

Plasmid 84756

$

$Uses

Page 10: Credit where credit is due: acknowledging all types of contributions

Who helped solve the STIM1 UDP_2542 case?

Page 11: Credit where credit is due: acknowledging all types of contributions

Credit extends beyond the publication

Johannes creates stim1 mouse

Melissa curates patient data for UDP_2542

Will performs analysis of UDP_2542 data that includes stim1 mouse to generate a dataset of prioritized variants

Tom writes publication pmid:25577287 about the STIM1 diagnosis

Tom explicitly credits Will as an author but not Melissa.

Page 12: Credit where credit is due: acknowledging all types of contributions

Dan Katz

Page 13: Credit where credit is due: acknowledging all types of contributions

Who contributed?

Melissa HaendelPeter RobinsonChris MungallSebastian KohlerCindy SmithNicole VasilevskySandra Dolken

Johannes GrosseAttila BraunDavid Varga-SzaboNiklas BeyersdorfBoris SchneiderLutz ZeitlmannPetra HankePatricia SchroppSilke MühlstedtCarolin ZornMichael HuberCarolin SchmittwolfWolfgang JaglaPhilipp YuThomas KerkauHarald SchulzeMichael NehlsBernhard Nieswandt

Thomas MarkelloDong ChenJustin Y. Kwan Iren Horkayne-Szakaly Alan Morrison Olga Simakova Irina Maric Jay Lozier Andrew R. Cullinane Tatjana Kilo Lynn Meister Kourosh PakzadSanjay Chainani Roxanne Fischer Camilo Toro James G. White David AdamsCornelius BoerkoelWilliam A. Gahl Cynthia J. Tifft Meral Gunay-Aygun

Melissa HaendelDavid AdamsDavid DraperBailey GallingerJoie DavisNicole Vasilevsky Heather TrangRena GodfreyGretchen GolasCatherine GrodenMichele NehrebeckyAriane SoldatosElise Valkanas,Colleen WahlLynne Wolfe

Elizabeth Lee Amanda LinksWill Bone Murat SincanDamian SmedleyJules JacobsonNicole WashingtonElise FlynnSebastian KohlerOrion BuskeMarta GirdeaMichael Brudno Jeremy Band

Hans GoebleKaren BalbachNadine PfeiferSandra WernerChristian Linden

Clinical/care Pathology Ontologist CS/informatics Curator Basic research

Page 14: Credit where credit is due: acknowledging all types of contributions

Contribution and Attribution in the Context of the Scholar workshop – Force 2015, Oxford, January 2015

Measuring success through improved attribution VIVO 2015, Austin, August 2015

OpenRIF: semantic infrastructure for the scholarly research landscape, Portland, April 2016

Project CRediT workshop, Washington DC, December 2014

The evolution of credit

NISO Alternative Metrics Initiative: Outputs in Scholarly Communications, May 2016

Page 15: Credit where credit is due: acknowledging all types of contributions

EXAMPLE OUTPUTS related to software:

Outputs: binary redistribution package (installer), algorithm, data analytic software tool, analysis scripts, data cleaning, APIs, codebook (for content analysis), source code, software to make metadata for libraries archives and museums, data analytic software tool, source code, program codes (for modeling), commentary in code(thinking of open source-need to attribute code authors and commentator/enhancers/hackers, who can document what they did and why), computer language (a syntax to describe a set of operations or activities), software patch (set of changes to code to fix bugs, add features, etc.), digital workflow (automated sequence of programs, steps to an outcome), software library (non-stand alone code that can be incorporated into something larger), software application (computer code that accomplishes something)

Roles: catalog, design, develop, test, hacker, bug finder, software developer, software engineer, developer, programmer, system administrator, execute, document, software package maintainer, project manager, database administrator

Workshop results: >500 scholarly products

Page 16: Credit where credit is due: acknowledging all types of contributions

Introducing open Research Information Framework (openRIF)and the Contribution Ontology

Interoperable standard for representing people and organizations within the research ecosystem

http://bit.ly/ConnectedResearchersDavid Eichmann

Contribution Ontology

Page 17: Credit where credit is due: acknowledging all types of contributions

Acknowledgements

MARIJANE WHITE, KRISTI HOLMES, DAVID EICHMANN, KAREN E. GUTZMAN, STACY KONKIEL, MATTHEW BRUSH, VIOLETA ILIK, MIKE CONLON,

AMY BRAND, DAN KATZ, LIZ ALLEN, FIGSHARE, FORCE11 ATTRIBUTION WORKING

GROUP, CASRAI, OPENVIVO, SCIENCV, DIGITAL SCIENCE,

OPENRIF DEVELOPMENT TEAM

Join the Force Attribution Working Group at: https://www.force11.org/group/attributionwg

Join the openRIF listserv at: http://group.openrif.org