One of the pitches given at our second research data spring sandpit workshop on 13 July 2015.

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

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. Next Steps
Month 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

4. Approach
Open Development
– Lead dev works on helper app and
coordinates repo/publisher work
– Technical community building
Extensive Community enagagement
– Listserv
– Blog, Wiki
– RDA events etc.

5. Collaborators
Figshare - repository
RDA – community, publisher registry
THOR project - sustainability
ORCID – enabling technology
DataCite – enabling technology

6. Resourcing
PM/Community engagament
– 1.5 days per week
Lead Developer
– Full time
Other development/UX
– 2 weeks
Outreach/materials/conferences
...34K


7. 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

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

9. 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

10. 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

11. 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

12. 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

13. 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

14. Phase 2 - Development
Develop Helper App (iterative)
– 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 Deployment and collate feedback
40K, 4 months

15. 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

16. 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