A Capability Maturity Model for Research Data Management
CMM for RDM » 5. Repository Services and Preservation » 5.3 Activities Performed

Changes for document 5.3 Activities Performed

Last modified by crowston on 2014/06/01 12:07
From version 21.1
edited by crowston
on 2014/03/21 07:33
To version 22.1
edited by crowston
on 2014/03/21 07:36
Change comment: There is no comment for this version

Content changes

... ... @@ -24,7 +24,7 @@
24 24
25 25 == 5.3.4 Backup data ==
26 26
27 -Data, processing codes, and documentation should be regularly backed up ([[Hook et al., 2010>>||anchor="Hook"]]) according to the defined procedures to ensure that there are at least two (and preferably more) copies of all important data. Backup devices should be selected for and regularly checked for reliability. Backups should be regularly tested for completeness and correctness to ensure that backup copies have the same content as the original data file ([[DataONE, 2011c>>||anchor="DataONE-c"]]). The backups should also be checked to ensure that they are secure and and that only those who need access to backups have proper access ([[DataONE, 2011c>>||anchor="DataONE-c"]]). Contact information should be available for the persons responsible for the backed up data ([[DataONE, 2011c>>||anchor="DataONE-c"]]).
27 +Data, processing codes, and documentation should be regularly backed up ([[Hook et al., 2010>>||anchor="Hook"]]) according to the defined procedures to ensure that there are at least two (and preferably more) copies of all important data. Backup devices should be selected for and regularly checked for reliability. Backups should be regularly tested for completeness and correctness to ensure that backup copies have the same content as the original data file ([[DataONE, 2011c>>||anchor="DataONE-c"]]). Backups might include periodic full backups (i.e., all files) as well as more frequent incremental backups (i.e., backing up only data that have changed since the last backup). The backups should also be checked to ensure that they are secure and and that only those who need access to backups have proper access ([[DataONE, 2011c>>||anchor="DataONE-c"]]). Contact information should be available for the persons responsible for the backed up data ([[DataONE, 2011c>>||anchor="DataONE-c"]]).
28 28
29 29 A copy of the backup should be kept at a trusted off-site location ([[DataONE, 2011b>>||anchor="DataONE-b"]]). As well, keeping backup copies of data off-line will help ensure that they will are not affected by any system problems or software errors that damage the primary copy ([[Borer et al., 2009>>||anchor="Borer"]]). Copies of physical data stores such as lab notebooks and samples should also be regularly stored off-site for safe keeping ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]]).
30 30
... ... @@ -77,4 +77,3 @@
77 77
78 78 (% style="text-align:center" %)
79 79 [[<~~-~~-Previous Page>>doc:5\.2 Ability to Perfor]] / [[Next Page ~~-~~->>>doc:5\.4 Measurement and Analysis]]
80 -

XWiki Enterprise 5.1-milestone-1 - Documentation