30
The blessing and the curse: handshaking between general and specialist data repositories Hilmar Lapp (NESCent), Todd Vision (UNC Chapel Hill) GSC 15 Conference, Bethesda, MD April 22-24, 2013

The blessing and the curse: handshaking between general and specialist data repositories

Embed Size (px)

DESCRIPTION

Talk presented at the Genomic Standards Consortium 15 conference.

Citation preview

Page 1: The blessing and the curse: handshaking between general and specialist data repositories

The blessing and the curse: handshaking between

general andspecialist data repositories

Hilmar Lapp (NESCent), Todd Vision (UNC Chapel Hill)GSC 15 Conference, Bethesda, MD

April 22-24, 2013

Page 2: The blessing and the curse: handshaking between general and specialist data repositories

> 180 for biological sciences

alone

Page 3: The blessing and the curse: handshaking between general and specialist data repositories

Which data goes where?Which is required?

Page 4: The blessing and the curse: handshaking between general and specialist data repositories

Addressing the long tail of orphan dataVo

lum

e

Rank frequency of datatype

Specialized repositories(e.g. GenBank, GBIF)

Orphan data

After Heidorn (2008) http://hdl.handle.net/2142/9127

Many datasets belong to the long tail. Though less standardized, they can be rich in information content and have unique value

Page 5: The blessing and the curse: handshaking between general and specialist data repositories

General purpose repositories cater to long-tail data

Page 6: The blessing and the curse: handshaking between general and specialist data repositories

General purpose repositories cater to long-tail data

Page 7: The blessing and the curse: handshaking between general and specialist data repositories

And that’s aside from the proverbial Babel of

data formats.

Page 8: The blessing and the curse: handshaking between general and specialist data repositories

Where does this leave the user?

Page 9: The blessing and the curse: handshaking between general and specialist data repositories

Where to deposit what, and how?

Page 10: The blessing and the curse: handshaking between general and specialist data repositories

Enter Publication:

Please enter your publication:

Publication:

Enter Publication:

Metadatahas to be

provisioned redundantly

Page 11: The blessing and the curse: handshaking between general and specialist data repositories

How to concisely link to the supporting data?

Page 12: The blessing and the curse: handshaking between general and specialist data repositories

Given the article, how do I find the data?

Page 13: The blessing and the curse: handshaking between general and specialist data repositories
Page 14: The blessing and the curse: handshaking between general and specialist data repositories

Given a data record, how

do I find related data?

Page 15: The blessing and the curse: handshaking between general and specialist data repositories

How do I assess quality and fitness for purpose?

Page 16: The blessing and the curse: handshaking between general and specialist data repositories

Lessons fromDryad/TreeBASE

handshaking

Page 17: The blessing and the curse: handshaking between general and specialist data repositories

• The End To make data archiving and reuse a standard part of scholarly communication.

• The Means Integrate data archiving with the process of publication. Make archiving easy and low burden for both authors and journals. Give researchers incentives to archive their data. Promote responsible data reuse. Empower journals, societies & publishers in shared governance. Ensure sustainability and long-term preservation. Work with and support trusted, specialized disciplinary repositories.

• The Scope Research data in sciences and medicine. (Early focus on evolution and ecology). Content must be complementary to existing disciplinary repositories. Data must be associated with a vetted publication (article, thesis, book chapter, etc.) Associated non-data content (e.g. software scripts, figures) where appropriate

Page 18: The blessing and the curse: handshaking between general and specialist data repositories
Page 19: The blessing and the curse: handshaking between general and specialist data repositories
Page 20: The blessing and the curse: handshaking between general and specialist data repositories
Page 21: The blessing and the curse: handshaking between general and specialist data repositories
Page 22: The blessing and the curse: handshaking between general and specialist data repositories

Lessons learnt

• Different priorities on deposit versus metadata richness may void benefits

• Advantages of one-stop deposition and when to use it are not obvious to users

• Custom-building handshaking protocols is not robust, doesn’t scale

Page 23: The blessing and the curse: handshaking between general and specialist data repositories

How to promote

• Minimum metadata reporting standards?

• Uptake of community specialist repositories?

• Archival of all long-tail data?

• Linking between repositories?

Page 24: The blessing and the curse: handshaking between general and specialist data repositories

DataMetadata Links

DataMetadata Links

Page 25: The blessing and the curse: handshaking between general and specialist data repositories
Page 26: The blessing and the curse: handshaking between general and specialist data repositories

Standards for repository & web of data

interoperability

Page 27: The blessing and the curse: handshaking between general and specialist data repositories

Standards for repository & web of data interoperability

Page 28: The blessing and the curse: handshaking between general and specialist data repositories

Promoting community rallying around standards

?

Page 29: The blessing and the curse: handshaking between general and specialist data repositories

Promoting community rallying around standards

?

Page 30: The blessing and the curse: handshaking between general and specialist data repositories

Repo: http://datadryad.orgBlog: http://blog.datadryad.orgWiki: http://datadryad.org/wikiCode: http://code.google.com/p/dryadList: [email protected] @datadryad Dryad