Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
rdms:webapp:archiving [2023/05/02 13:45]
burcu [Step 3:] 		rdms:webapp:archiving [2023/12/11 13:02] (current)
jelte indexmenu number adjusted + Title Change
Line 1: Line 1:
-{{indexmenu_n>7}} +{{indexmenu_n>5}} 
-====== Archiving ======+====== Archiving Workflow ======
 The RDMS web interface offers the possibility to archive a project once the data is not in use any more or following a publication. In order for you to be able to start the archiving process, the data you want to archive needs to be stored in a project. The RDMS web interface offers the possibility to archive a project once the data is not in use any more or following a publication. In order for you to be able to start the archiving process, the data you want to archive needs to be stored in a project.
  
Line 38: Line 38:
 Active role: Data Manager Active role: Data Manager
  
-The Data Manager can check the archive one last time before the procedure is final. Here both the data and the metadata can be inspected and approved. This is the final step and the last point of no return in the process. After approval is given here, all secondary products generated in the archiving process are removed and the final archive is generated. From this point forward the archive itself, as well as the data it contains, cannot be deleted anymore (except by a system administrator).+The data manager can check the archive one last time before the procedure is final. Here, both the data and the metadata can be inspected and approved. This is the final step and the last point of no return in the process. After approval is given here, all secondary products generated in the archiving process are removed and the final archive is generated. From this point forward the archive itself, as well as the data it contains, cannot be deleted anymore (except by a system administrator).