Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to example dataset doesn't work #69

Open
rafwiewiora opened this issue Apr 2, 2016 · 7 comments
Open

Link to example dataset doesn't work #69

rafwiewiora opened this issue Apr 2, 2016 · 7 comments

Comments

@rafwiewiora
Copy link
Member

This is probably not meant to be like this, so pointing out:

* See the example dataset from [modeling all human tyrosine kinases](http://datadryad.org/review?doi=doi:10.5061/dryad.7fg32).

in README.MD gives this:
messages image 29891914 copy

@sonyahanson
Copy link

It says Content restricted ahead of article publication, which I think is correct. The article has not been published outside bioRxiv yet, I believe.

@jchodera
Copy link
Member

jchodera commented Apr 5, 2016 via email

@danielparton
Copy link
Collaborator

But the article is not actually published yet is it?

On Mon, Apr 4, 2016 at 8:33 PM, John Chodera [email protected]
wrote:

It was accepted, so we should let them know to release this.

@danielparton, any idea how to do this?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#69 (comment)

@jchodera
Copy link
Member

jchodera commented Apr 5, 2016

Proofs have been sent in.

@danielparton
Copy link
Collaborator

I don't think I have any control over it through their website, but you
could contact Dryad and ask if they can make the data available now the
proofs have been sent in. I have a feeling they will say no.
This would mean Dryad is not suitable if we want to keep a dataset
available throughout the whole pre- and post-publication process.

On Mon, Apr 4, 2016 at 9:09 PM, John Chodera [email protected]
wrote:

Proofs have been sent in.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#69 (comment)

@rafwiewiora
Copy link
Member Author

I see - well I just thought it strange for our lab to be restricting a dataset - why not have it available pre-publication?

@danielparton
Copy link
Collaborator

It's Dryad's policy, not ours - I'm not sure why they have that policy.
Maybe they think most researchers don't want to make their data available
until the paper is completely published. Or maybe they're worried about
changes (e.g. article title) which can happen shortly before publication.
Shouldn't be a problem really, but maybe they just haven't built in the
capability to automate this. Their upload infrastructure was not exactly
super streamlined.
See this quote from the FAQ ("What happens to data after it is submitted"):

The data package is publicly released once the online version of the associated publication is available (unless an alternative release option has been selected). Since paper titles, abstracts, authors etc. often change during the publication process, Dryad confirms and updates this information against the accepted/published article.

We weren't really aware of this when we decided to use Dryad. Or at least
we hadn't considered what would happen in the period between acceptance and
publication. So you guys might want to revisit how you make publication
data available in the future, if Dryad is not going to be suitable.

On Mon, Apr 4, 2016 at 10:07 PM, Rafal Wiewiora [email protected]
wrote:

I see - well I just thought it strange for our lab to be restricting a
dataset - why not have it available pre-publication?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#69 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants