Provenance and authenticity: Difference between revisions

From ADA Public Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


Depositors are required to sign an ADA Data License confirming they have the right to share the data. The original data and metadata a depositor submits is preserved unchanged as a Submission Information package (SIP).  
Depositors are required to sign an ADA Data License confirming they have the right to share the data. The original data and metadata a depositor submits is preserved unchanged as a Submission Information package (SIP).  
"**JM Refer to ADAPT and PROV log.  Can also point https://docs.ada.edu.au/index.php?title=Technical_Infrastructure&action=edit&redlink=1 as ADAPT is included as an ADA Web based tool". 


Any curation required is done on a copy of the data.   
Any curation required is done on a copy of the data.   

Revision as of 06:54, 21 August 2024

To ensure clear provenance and authenticity tracking of each deposit, the ADA is basing its workflow in the Open Archival Information System (or OAIS).

Depositors are required to sign an ADA Data License confirming they have the right to share the data. The original data and metadata a depositor submits is preserved unchanged as a Submission Information package (SIP).

Any curation required is done on a copy of the data.

Curation and processing of the data are recorded in a processing report and also programmatically for quantitative data in SPSS or R syntax. These documents are stored under a unique ADA ID with the SIP as part of the Archival information package (AIP), see R10 Quality Assurance for details of the curation.

The Dissemination Information package (DIP) is generated from the AIP and is made accessible on a separate instance of dataverse, the Production Dataverse.

Changes or updates to the data files of an already published deposit are treated like a new deposit, i.e. a new SIP, AIP and DIP are created. Metadata changes by depositors are managed through the ADA ticketing system.

Once the data is published on the Production Dataverse, any changes to files and metadata are tracked in Dataverse’s versioning.