[dataflow] (DATAFLOW-364) Why have the default embargo of Databank as 70 years, rather than the default being open

[Anusha Ranganathan (Created) (JIRA)]

Why have the default embargo of Databank as 70 years, rather than the default being open
----------------------------------------------------------------------------------------

Key: DATAFLOW-364
URL: http://dataflow-jira.bodleian.ox.ac.uk/jira/browse/DATAFLOW-364
Project: DataFlow
Issue Type: Improvement
Components: DataBank
Reporter: Anusha Ranganathan
Assignee: Anusha Ranganathan


Comments from David Shotton

Files uploaded from DataStage under a CC0 license should NOT BE EMBARGOED by default on submission to DataBank. Rather, they should be open, as this CC0 license requires, not requiring the owner's DataBank password to view them. The whole point of DataBank is to PUBLISH DATA OPENLY!!! The default should be no embargo!

Later, you can add back to DataStage and/or DataBank the possibility for the user to specify an embargo date, as Bhavana had it originally. But we must make the user work for this privilege, by providing a reason for why the data should be embargoed and a reason for the length of the embargo period selected. The default period for a selected embargo should be one year, with a normal maximum of two years. Longer periods should require special justification and permission.

Comments from Anusha
The current behaviour is that every Data package is embargoed for a default period of 70 years and the user can modify the default behaviour to make the package openly accessible. If we are to embrace open access, we certainly need to reverse our default behaviour

Note: Excerpt from email dated 14 June 2014 from DS


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: http://dataflow-jira.bodleian.ox.ac.uk/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira