4 like 0 dislike
1.0k views
in Open Science by (725 points)

I wonder why publicly-funded grants do not systematically demand from the recipients that code and data to be released, and results/papers to be publicly accessible. (put aside data that raise privacy issues)



This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (215 points)
0 0
Some do. 654321

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (0 points)
0 0
This requirement has become much more common in the past few years; I suspect a combination of institutional inertia and uncertainty regarding the best long-term archival options has thus far arrested its progress. At least NSF and NIH both require *some* form of data plan now.

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (185 points)
0 0
In the UK, [this is now the case](http://www.rcuk.ac.uk/research/datapolicy/) as the default policy from the major public research funders. This is being driven by a number of things: public investment should lead to public knowledge, being able to validate results more easily, and better ability of business to innovate.

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)

1 Answer

1 like 0 dislike
by (190 points)

Because there has not been a strong enough push to require it and some researchers prefer to keep code/data confidential. This is currently a topic of discussion at the national level led by organizations such as EFF. This is hopefully a situation that will soon change for the better.



This post has been migrated from the Open Science private beta at StackExchange (A51.SE)

Ask Open Science used to be called Open Science Q&A but we changed the name when we registered the domain ask-open-science.org. Everything else stays the same: We are still hosted by Bielefeld University.

If you participated in the Open Science beta at StackExchange, please reclaim your user account now – it's already here!

E-mail the webmaster

Legal notice

Privacy statement

Categories

...