| Both sides previous revision Previous revision Next revision | Previous revision |
| rdms:workflows:archiving [2025/03/04 14:11] – [Step 4: Add/Approve Metadata] made bold jelte | rdms:workflows:archiving [2025/03/06 09:19] (current) – unstructured to unbundled jelte |
|---|
| {{indexmenu_n>2}} | {{indexmenu_n>2}} |
| ====== Archiving Workflow ====== | ====== Archiving Workflow ====== |
| {{ :rdms:workflows:rdms_archiving_workflow_wiki.png?900 |}} | {{ :rdms:workflows:rdms_archiving_workflow_wiki.svg |}} |
| |
| The archiving workflow in the RDMS allows the owner of a [[rdms:solution:projects|RDMS Project]] to archive the data contained in the project folder by following a step-by-step process in the web interface. An archive in the RDMS is **a bundled dataset**, called //data package//, that contains both data and related metadata, and has been **frozen by making it read-only** in the system. The archive is by default **labelled with a creation date** to inform the user of when the data was frozen. The archived dataset (data package) can then be pushed to the publication workflow (**still in development**), which will allow the publishing of the dataset metadata to the outside world, in compliance with the Open Science framework. | The archiving workflow in the RDMS allows the owner of a [[rdms:solution:projects|RDMS Project]] to archive the data contained in the project folder by following a step-by-step process in the web interface. An archive in the RDMS is **a bundled dataset**, called //data package//, that contains both data and related metadata, and has been **frozen by making it read-only** in the system. The archive is by default **labelled with a creation date** to inform the user of when the data was frozen. The archived dataset (data package) can then be pushed to the publication workflow (**still in development**), which will allow the publishing of the dataset metadata to the outside world, in compliance with the Open Science framework. |
| **Prerequisites**: Step 2 has finished. | **Prerequisites**: Step 2 has finished. |
| |
| In this step, the previously unstructured data that was moved to the project's archive space in the RDMS is bundled to a so called **data package**. This data package is a tar file containing the selected data, as well as RDMS file and folder metadata if the option to export it was selected in the previous step. | In this step, the previously unbundled data that was moved to the project's archive space in the RDMS is bundled to a so called **data package**. This data package is a tar file containing the selected data, as well as RDMS file and folder metadata if the option to export it was selected in the previous step. |
| |
| ---- | ---- |
| {{ :rdms:workflows:rdms_workflow_dp_1.png?direct&600 |}} | {{ :rdms:workflows:rdms_workflow_dp_1.png?direct&600 |}} |
| |
| If you select the //Create data package// option in the menu, the RDMS system will automatically bundle the previously unstructured data into a tar archive. Afterwards, the next step (adding metadata to data package) can follow. | If you select the //Create data package// option in the menu, the RDMS system will automatically bundle the previously unbundled data into a tar archive. Afterwards, the next step (adding metadata to data package) can follow. |
| |
| {{ :rdms:workflows:rdms_workflow_dp_4.png?direct&600 |}} | {{ :rdms:workflows:rdms_workflow_dp_4.png?direct&600 |}} |
| </code> | </code> |
| |
| If we have a look at the .json file with the metadata, we see that it contains info about the metadata related to the selected data, not the one related to the archive. The following is a snippet of that file that shows how this info is exported and included in the data package. | If we have a look at the JSON file with the metadata, we see that it contains info about the metadata related to the selected data, not the one related to the archive. The following is a snippet of that file that shows how this info is exported and included in the data package. |
| |
| <code> | <code> |