This document proposes a system to give researchers credit for depositing their data by allowing them to easily submit a "data paper" about their deposited data set. It involves developing a helper application that would integrate with data repositories and publishers to streamline the process of depositing data and submitting the associated data paper. The proposal outlines three phases: requirements gathering and design, development and trial deployment, and expansion and sustainability. The goal is to incentivize data sharing by providing researchers a publication and citation opportunity for describing and taking credit for their datasets.

1. Giving Researchers Credit
for Data
Neil Jefferies, Bodleian Libraries
Thomas Ingraham, F1000Research

2. “Carrot” for data deposit
“Submit data paper” button on repository
Researcher 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

3. Schematic
Researcher
Helper
App
Data
Repo
Partial
Package
(SWORD+)
Complete
Package
(SWORD+)
Publisher
Data
Paper
Data Deposit
Submit
Refs
(Zotero)
Etc.
(Upload)
Docs
(O360/
G-Docs)
Feedback
DOI+Metadata

4. Team
Repositories
– Oxford University Research
Archive
●
CEDA (Centre for
Environmental Data Archive)
Publishers
– F1000Research
●
Ubiquity Press (OJS)
●
Geophysical Data Journal
●
Wiley (Fiona Murphy)

5. Phase 1 - Requirements
Survey/Analysis of data publisher workflows and data
requirements
– Fiona Murphy
Gap Analysis between repos/publishers
Defines functional requirements of helper app
 All partners
Draft protocol spec (augmented SWORD, AtomPub for backfeed?)
F1000R, Oxford
Review by all partners
Wireframes for Helper App
Oxford/outsourced
3.5K, 3 months

6. Phase 2 - Development
Develop Helper App (iternattive)
– Oxford/outsourced
– TDD so test harness is also a deliverable
Develop Repository Shim (the button) for Oxford
Oxford
Develop Publisher Submission Shim for F1000R
F1000R
Publish final spec
Validation suite for packages
All
Identify candidates for trial deployment
All
Trial Deployement and collate feedback
40K, 4 months

7. Phase 2 - Development
Develop Helper App (iterative, depends on Phase 1 outcome)
– Oxford/outsourced
– TDD so test harness is also a deliverable
Develop Repository Shim (the button) for Oxford
Oxford (2 weeks)
Develop Publisher Submission Shim for F1000R
F1000R (1 week)
Publish final spec
Validation suite for packages
All
Identify candidates for trial deployment
All
Trial Deployment and collate feedback
Up to 40K, 4 months

8. Phase 3 - Expansion
Roll out into production
– Real-life examples for dissemination
Package Helper App for deployment elsewhere
OJS, CEDA/GDJ implementations
Outreach, additional use case development
Initial survey gives us a ready-defined “community”
Sustainability for helper app (the rest is just specs)
Other workflows
Joint deposit-submit
Backfeed for conventional AAS/Publications
Further Deployments and collate feedback
Up to 30K, 6 months