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 1.1
edited by Jian Qin
on 2013/06/15 04:16
To version 2.1
edited by Jian Qin
on 2013/06/15 04:19
Change comment: There is no comment for this version

Content changes

... ... @@ -1,62 +1,86 @@
1 -==5.3 Activities Performed==
1 +== 5.3 Activities Performed ==
2 2
3 3 {{box cssClass="floatinginfobox" title="**Contents**"}}
4 4 {{toc/}}
5 5 {{/box}}
6 6
7 -===5.3.1 Control changes to data files===
8 -**Versions**
9 -• Provide versions of data products with defined identifiers (Source #57)
10 -• Use appropriate tools, such as version control tools, to keep track of the history of the data files (Source #1)
11 -• Be aware of, and document, any changes in the coding scheme (Source #2)
7 +=== 5.3.1 Control changes to data files ===
12 12
13 -**Save original as is**
14 -• By saving the original data set with copious notes, you can maintain your data integrity for the long term.
15 - (Source #67)
16 -• Do not make any changes / corrections to the original raw data file (Source #52)
17 -• Consider making your original data file read-only (Source #52)
18 -• using your original data as input, but saving the changes to a separate data file (Source #67)
19 -• Always store an uncorrected data file with all its bumps and warts. (Source #67)
20 -• Keep copies of your raw data as collected or as received, before any processing has been done. (Source #2)
21 -• Unaltered images should be preserved at the highest resolution possible. (Source #51)
22 -===5.3.2 Store data===
23 -• all storage devices, locations and access accounts should be documented and accessible to team members (Source #1)
24 -• Store data in nonproprietary hardware formats. (Source #67)
25 -• Handle and Store Your Media With Care (Source #39)
26 -• Routinely Inspect and Replace Data Discs (Source #39)
9 +==== Versions ====
27 27
28 -**Images**
29 -• Storage of images solely on local hard drives or servers is not recommended. (Source #51)
30 -• Store original images in separate locations (Source #51)
31 -===5.3.3 Backup data===
32 -**Schedule**
33 -• Manage schedules for archive generation, validation and delivery
34 -• back-up your data at frequent intervals and in multiple locations Source #4
35 -• Backup your data at regular frequencies Source #4
36 -• Backup strategies… should be optimized for the data collection process Source #4
37 -• Streaming data should be backed up at regularly scheduled points in the collection process Source #4
38 -**Devices**
39 -• Use a reliable device when making backups Source #4
40 -• Copies of original notebooks should be kept elsewhere for safekeeping. (Source #71)
41 -**Process**
42 -• replicate data to a set of centralized servers (Source #68)
43 -• Create, at a minimum, 2 copies of your data Source #4
44 -• Place one copy at an “off-site” and “trusted” location Source #4
45 -• ensure that backup copies have the same content as the original data file (Source #38)
46 -**What to backup**
47 -• data, processing codes, and documentation at all stages of development be routinely copied and backed up on secure and retrievable media (Source #2)
48 -• Electronic data should be backed up on a disk with a hard copy (Source #71)
49 -• it is also advisable to create additional copies of your data that are off-line (not on the (Source #67)
50 -**Personnel**
51 -• Have contact information available for the person responsible for the [backup] data (Source #38)
52 -• Ensure that those who need access to backups have proper access (Source #38)
53 -===5.3.4 Curate data===
54 -• Electronic records need to be carefully monitored. (Source #71)
55 -===5.3.5 Provide data security===
56 -• confidential data has to be stored in such a way that access cannot be available (Source #71)
57 -===5.3.6 Perform data migration===
58 -**Hardware**
59 -• maintain a redundant copy of your data for 30 days until the new device “settles in.” (Source #39)
11 +• Provide versions of data products with defined identifiers (Source #57)
12 +• Use appropriate tools, such as version control tools, to keep track of the history of the data files (Source #1)
13 +• Be aware of, and document, any changes in the coding scheme (Source #2) ====
14 +
15 +==== Save original as is ====
16 +
17 +• By saving the original data set with copious notes, you can maintain your data integrity for the long term.
18 + (Source #67)
19 +• Do not make any changes / corrections to the original raw data file (Source #52)
20 +• Consider making your original data file read-only (Source #52)
21 +• using your original data as input, but saving the changes to a separate data file (Source #67)
22 +• Always store an uncorrected data file with all its bumps and warts. (Source #67)
23 +• Keep copies of your raw data as collected or as received, before any processing has been done. (Source #2)
24 +• Unaltered images should be preserved at the highest resolution possible. (Source #51)
25 +
26 +=== 5.3.2 Store data ===
27 +
28 +• all storage devices, locations and access accounts should be documented and accessible to team members (Source #1)
29 +• Store data in nonproprietary hardware formats. (Source #67)
30 +• Handle and Store Your Media With Care (Source #39)
31 +• Routinely Inspect and Replace Data Discs (Source #39)
32 +
33 +==== Images ====
34 +
35 +• Storage of images solely on local hard drives or servers is not recommended. (Source #51)
36 +• Store original images in separate locations (Source #51)
37 +
38 +=== 5.3.3 Backup data ===
39 +
40 +==== Schedule ====
41 +
42 +• Manage schedules for archive generation, validation and delivery
43 +• back-up your data at frequent intervals and in multiple locations Source #4
44 +• Backup your data at regular frequencies Source #4
45 +• Backup strategies… should be optimized for the data collection process Source #4
46 +• Streaming data should be backed up at regularly scheduled points in the collection process Source #4
47 +
48 +==== Devices ====
49 +
50 +• Use a reliable device when making backups Source #4
51 +• Copies of original notebooks should be kept elsewhere for safekeeping. (Source #71)
52 +
53 +==== Process ====
54 +
55 +• replicate data to a set of centralized servers (Source #68)
56 +• Create, at a minimum, 2 copies of your data Source #4
57 +• Place one copy at an “off-site” and “trusted” location Source #4
58 +• ensure that backup copies have the same content as the original data file (Source #38)
59 +
60 +==== What to backup ====
61 +
62 +• data, processing codes, and documentation at all stages of development be routinely copied and backed up on secure and retrievable media (Source #2)
63 +• Electronic data should be backed up on a disk with a hard copy (Source #71)
64 +• it is also advisable to create additional copies of your data that are off-line (not on the (Source #67)
65 +
66 +==== Personnel ====
67 +
68 +• Have contact information available for the person responsible for the [backup] data (Source #38)
69 +• Ensure that those who need access to backups have proper access (Source #38)
70 +
71 +=== 5.3.4 Curate data ===
72 +
73 +• Electronic records need to be carefully monitored. (Source #71)
74 +
75 +=== 5.3.5 Provide data security ===
76 +
77 +• confidential data has to be stored in such a way that access cannot be available (Source #71)
78 +
79 +=== 5.3.6 Perform data migration ===
80 +
81 +==== Hardware ====
82 +
83 +• maintain a redundant copy of your data for 30 days until the new device “settles in.” (Source #39)
60 60 Software
61 -• continue using the version of the software that was originally used to create the data file to view and manipulate the file contents (Source #52)
62 -• When forced to use a newer version of a software package to open files created with an older version of the application, first save a copy of the original file
85 +• continue using the version of the software that was originally used to create the data file to view and manipulate the file contents (Source #52)
86 +• When forced to use a newer version of a software package to open files created with an older version of the application, first save a copy of the original file

XWiki Enterprise 5.1-milestone-1 - Documentation