16
Giving Researchers Credit for Data Neil Jefferies, Bodleian Libraries Thomas Ingraham, F1000Research Fiona Murphy

Giving researchers credit for data

  • Upload
    jisc

  • View
    212

  • Download
    1

Embed Size (px)

Citation preview

Page 1: Giving researchers credit for data

Giving Researchers Credit for Data

Neil Jefferies, Bodleian LibrariesThomas Ingraham, F1000Research

Fiona Murphy

Page 2: Giving researchers credit for data

“Carrot” for data deposit“Submit data paper” button on repositoryResearcher gets

– Another publication/citation opportunity– (Data preserved)

Publisher gets– More data paper submissions– Link referrals from data repositories

Repositories get– More data deposots– Better metadata

Page 3: Giving researchers credit for data

Next StepsMonth 1

– Detailed technical specification

– Analysis of platforms to identify potential quick wins

Month 2-4 – reference implementation

– Develop helper app

– Develop interfaces for repos (Oxford, FigShare)

– Develop Journal interface F1000

Page 4: Giving researchers credit for data

ApproachOpen Development

– Lead dev works on helper app and coordinates repo/publisher work

– Technical community building

Extensive Community enagagement

– Listserv

– Blog, Wiki

– RDA events etc.

Page 5: Giving researchers credit for data

CollaboratorsFigshare - repositoryRDA – community, publisher registryTHOR project - sustainabilityORCID – enabling technology

DataCite – enabling technology

Page 6: Giving researchers credit for data

ResourcingPM/Community engagament

– 1.5 days per week

Lead Developer

– Full time

Other development/UX

– 2 weeks

Outreach/materials/conferences

...34K

Page 7: Giving researchers credit for data

Schematic

Researcher

Helper App

DataRepo

Partial Package

(SWORD+)

Complete Package

(SWORD+)

Publisher

DataPaper

Data Deposit

Submit

Refs(Zotero)

Etc.(Upload)

Docs(O360/

G-Docs)

FeedbackDOI+Metadata

Page 8: Giving researchers credit for data

TeamRepositories

– Oxford University Research Archive● CEDA (Centre for Environmental

Data Archive)

Publishers– F1000Research

● Ubiquity Press (OJS)● Geophysical Data Journal● Wiley (Fiona Murphy)

Page 9: Giving researchers credit for data

Phase 1 - RequirementsSurvey/Analysis of data publisher workflows and data requirements

– Fiona Murphy

Gap Analysis between repos/publishersDefines functional requirements of helper app

All partners

Draft protocol spec (augmented SWORD, AtomPub for backfeed?) F1000R, Oxford

Review by all partners

Wireframes for Helper AppOxford/outsourced

3.5K, 3 months

Page 10: Giving researchers credit for data

Phase 1 - RequirementsSurvey/Analysis of data publisher workflows and data requirements

– Fiona Murphy

Gap Analysis between repos/publishersDefines functional requirements of helper app

All partners

Draft protocol spec (augmented SWORD, AtomPub for backfeed?) F1000R, Oxford

Review by all partners

Wireframes for Helper AppOxford/outsourced

3.5K, 3 months

Page 11: Giving researchers credit for data

Phase 1 - RequirementsSurvey/Analysis of data publisher workflows and data requirements

– Fiona Murphy

Gap Analysis between repos/publishersDefines functional requirements of helper app

All partners

Draft protocol spec (augmented SWORD, AtomPub for backfeed?) F1000R, Oxford

Review by all partners

Wireframes for Helper AppOxford/outsourced

3.5K, 3 months

Page 12: Giving researchers credit for data

Phase 1 - RequirementsSurvey/Analysis of data publisher workflows and data requirements

– Fiona Murphy

Gap Analysis between repos/publishersDefines functional requirements of helper app

All partners

Draft protocol spec (augmented SWORD, AtomPub for backfeed?) F1000R, Oxford

Review by all partners

Wireframes for Helper AppOxford/outsourced

3.5K, 3 months

Page 13: Giving researchers credit for data

Phase 1 - RequirementsSurvey/Analysis of data publisher workflows and data requirements

– Fiona Murphy

Gap Analysis between repos/publishersDefines functional requirements of helper app

All partners

Draft protocol spec (augmented SWORD, AtomPub for backfeed?) F1000R, Oxford

Review by all partners

Wireframes for Helper AppOxford/outsourced

3.5K, 3 months

Page 14: Giving researchers credit for data

Phase 2 - DevelopmentDevelop Helper App (iterative)

– Oxford/outsourced

– TDD so test harness is also a deliverable

Develop Repository Shim (the button) for OxfordOxford

Develop Publisher Submission Shim for F1000R F1000R

Publish final specValidation suite for packages

All

Identify candidates for trial deployment

All

Trial Deployment and collate feedback

40K, 4 months

Page 15: Giving researchers credit for data

Phase 2 - DevelopmentDevelop Helper App (iterative, depends on Phase 1 outcome)

– Oxford/outsourced

– TDD so test harness is also a deliverable

Develop Repository Shim (the button) for OxfordOxford (2 weeks)

Develop Publisher Submission Shim for F1000R F1000R (1 week)

Publish final specValidation suite for packages

All

Identify candidates for trial deployment

All

Trial Deployment and collate feedback

Up to 40K, 4 months

Page 16: Giving researchers credit for data

Phase 3 - ExpansionRoll out into production

– Real-life examples for dissemination

Package Helper App for deployment elsewhereOJS, CEDA/GDJ implementationsOutreach, additional use case development

Initial survey gives us a ready-defined “community”Sustainability for helper app (the rest is just specs)

Other workflowsJoint deposit-submitBackfeed for conventional AAS/Publications

Further Deployments and collate feedback

Up to 30K, 6 months