Setting Access Restrictions: Difference between revisions

From ADA Public Wiki
Jump to navigation Jump to search
Created page with "Access Restrictions can be applied to each individual dataset, as determined by the agreements entered into with the ADA under the License Agreement Form. At this stage, Acce..."
 
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Access Restrictions can be applied to each individual dataset, as determined by the agreements entered into with the ADA under the License Agreement Form.
*[[4. Population of 'Shell Dataverse & Dataset']]
Post-Uploading Activity
**[[Adding File Tags and Description Notes]]
**[[Editing and Entering Metadata]]
***[[Non-mandatory Metadata fields information]]
***[[Geospatial Metadata field information]]
***[[Social Science and Humanities Metadata field information]]
**[[Setting Access Restrictions]]
**[[Completion of License Document Suite]]
***[[The License Agreement Form.]]
****[[Download License Agreement Form]]
***[[The License Terms and Conditions of Use]]
****[[Download Terms and Conditions of Use (Undertaking Form) Selection Information]] document
***[[The License Access Guestbook]]
****[[Download License Access Guestbook Selection Information]] document
**[[Notify the ADA that the Self-Deposit process has been completed]]


At this stage, Access Restrictions will be applied to the datset(s) by the ADA Staff as part of their curation activities prior to publishing the Dataverse. This is required because the ADA Staff need to process the Submission Information Pack (SIP) and archive the files on the National Computer Infrastructure (NCI) before uploading the material to the Dataverse PRODUCE site.
==Setting Access Restrictions==


[[Glossary of Terms|Data Owners]] should now proceed to complete the License Document suite.
Access Restrictions can be applied to each individual file, as determined by the agreements entered into with the ADA under the License Agreement Form.


= Next Page =
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.
*[[Completion of License Document Suite]]


= Previous Page =
==Future Activity==
*[[Social Science and Humanities Metadata field information]]
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. Depending upon the outcomes of the automation, Data Owners may in the future need to set the dataset file restrictions. Instructions will be included here if this is required.


== Next Section ==
[[Glossary of Terms|Data Owners]] should for now proceed to [[Completion of License Document Suite|complete the License Document Suite]].
 
== Previous Section ==

Latest revision as of 02:48, 24 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. Depending upon the outcomes of the automation, Data Owners may in the future need to set the dataset file restrictions. Instructions will be included here if this is required.

Data Owners should for now proceed to complete the License Document Suite.