Provenance and authenticity: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
To ensure clear provenance and authenticity tracking of each deposit, the ADA is basing its workflow in the OAIS model (see R11 for detailed workflow). | |||
To ensure clear provenance and authenticity tracking of each deposit, the ADA is basing its | |||
Depositors are required to sign an ADA Data License (see | Depositors are required to sign an ADA Data License (see R02 Rights Management) confirming ADA has the right to share the data. The original data and metadata a depositor submits to the ADA Deposit Dataverse instance (see R14 Storage and Integrity) is preserved unchanged as a Submission Information Package (SIP) by the ADA Processing Tool (ADAPT). ADAPT is a web-based tool developed by ADA to ensure that data and metadata in the archive are programmatically moved between Dataverse instances and ADA’s archival storage. ADAPT implements PROV-O [3] to express basic classes to log these activities. Any curation required is done on a copy of the data. | ||
The curation and processing of the data are recorded in a processing report supplied to and approved by the depositor, and also programmatically for quantitative data in SPSS or R syntax. These documents are stored under a unique six-digit identification number (ADAID) 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 | The Dissemination Information package (DIP) is generated from the AIP and is made accessible on separate instances of dataverse, first on the Test Dataverse for the depositor to review, then on the Production Dataverse for user access (see R14 Storage and Integrity). | ||
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, which includes identification checks by ensuring contact information matches the corresponding verified user account on 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, which includes identification checks by ensuring contact information matches the corresponding verified user account on Dataverse. | ||
Once the data is published on the | Once the data is published on the Production Dataverse, any changes to files and metadata are tracked in Dataverse’s versioning with details of any changes accessible to all users. | ||
==References== | |||
[3] PROV-O – (https://www.w3.org/TR/2013/REC-prov-o-20130430/) | |||
[31] Provenance and authenticity – (https://docs.ada.edu.au/index.php/Provenance_and_authenticity) | |||
Latest revision as of 02:16, 14 September 2024
To ensure clear provenance and authenticity tracking of each deposit, the ADA is basing its workflow in the OAIS model (see R11 for detailed workflow).
Depositors are required to sign an ADA Data License (see R02 Rights Management) confirming ADA has the right to share the data. The original data and metadata a depositor submits to the ADA Deposit Dataverse instance (see R14 Storage and Integrity) is preserved unchanged as a Submission Information Package (SIP) by the ADA Processing Tool (ADAPT). ADAPT is a web-based tool developed by ADA to ensure that data and metadata in the archive are programmatically moved between Dataverse instances and ADA’s archival storage. ADAPT implements PROV-O [3] to express basic classes to log these activities. Any curation required is done on a copy of the data.
The curation and processing of the data are recorded in a processing report supplied to and approved by the depositor, and also programmatically for quantitative data in SPSS or R syntax. These documents are stored under a unique six-digit identification number (ADAID) 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 separate instances of dataverse, first on the Test Dataverse for the depositor to review, then on the Production Dataverse for user access (see R14 Storage and Integrity).
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, which includes identification checks by ensuring contact information matches the corresponding verified user account on Dataverse.
Once the data is published on the Production Dataverse, any changes to files and metadata are tracked in Dataverse’s versioning with details of any changes accessible to all users.
References
[3] PROV-O – (https://www.w3.org/TR/2013/REC-prov-o-20130430/)
[31] Provenance and authenticity – (https://docs.ada.edu.au/index.php/Provenance_and_authenticity)