Setting Access Restrictions: Difference between revisions
Dahaddican (Sọ̀rọ̀ | contribs) No edit summary |
Dahaddican (Sọ̀rọ̀ | contribs) |
||
Line 18: | Line 18: | ||
==Setting Access Restrictions== | ==Setting Access Restrictions== | ||
Access Restrictions can be applied to each individual file | Access Restrictions can be applied to each individual file, as determined by the agreements entered into with the ADA under the License Agreement Form. | ||
Currently, Access Restrictions will be applied to | Currently, Access Restrictions will be applied to these file(s) by the ADA Staff as part of their curation activities prior to publishing your Dataverse. The ADA Staff conduct this function as they need to manually archive the dataset contents, known as the Submission Information Pack (SIP) on the National Computer Infrastructure (NCI) before conducting their Quality Assurance checks and uploading the final dataset material to the Dataverse PRODUCE site. Thus any Access Restrictions that you apply at this stage will need to be re-entered by ADA Staff onto the Dataverse TEST and PRODUCE environments. | ||
==Future Activity== | ==Future Activity== |
Revision as of 21:10, 22 January 2020
Post-Uploading Activity
Setting Access Restrictions
Access Restrictions can be applied to each individual file, as determined by the agreements entered into with the ADA under the License Agreement Form.
Currently, Access Restrictions will be applied to these file(s) by the ADA Staff as part of their curation activities prior to publishing your Dataverse. The ADA Staff conduct this function as they need to manually archive the dataset contents, known as the Submission Information Pack (SIP) on the National Computer Infrastructure (NCI) before conducting their Quality Assurance checks and uploading the final dataset material to the Dataverse PRODUCE site. Thus any Access Restrictions that you apply at this stage will need to be re-entered by ADA Staff onto the Dataverse TEST and PRODUCE environments.
Future Activity
The ADA intend to introduce a means of automating some of their processing activity and it is expected that this will include the automatic copying of the dataset contents from the DEPOSIT Dataverse Site to the TEST and PRODUCE environments ahead of the final publishing of the dataset. At this point in time, this section may warrant review.
Data Owners should now proceed to complete the License Document Suite.