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 6.1
edited by Arden Kirkland
on 2013/11/30 18:03
To version 7.1
edited by Arden Kirkland
on 2013/11/30 18:12
Change comment: inserting more citation links

Content changes

... ... @@ -9,17 +9,17 @@
9 9 ==== Versions ====
10 10
11 11 • Provide versions of data products with defined identifiers ([[DataONE, n.d.-g>>||anchor="DataONE-g"]])
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) ====
12 +• Use appropriate tools, such as version control tools, to keep track of the history of the data files ([[Hook et al., 2010>>||anchor="Hook"]])
13 +• Be aware of, and document, any changes in the coding scheme ([[Hook et al., 2010>>||anchor="Hook"]])====
14 14
15 15 ==== Save original as is ====
16 16
17 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)
18 + ([[Borer et al., 2009>>||anchor="Borer"]])
19 +• Do not make any changes / corrections to the original raw data file ([[DataONE, n.d.-f>>||anchor="DataONE-f"]])
20 +• Consider making your original data file read-only ([[DataONE, n.d.-f>>||anchor="DataONE-f"]])
21 +• using your original data as input, but saving the changes to a separate data file ([[Borer et al., 2009>>||anchor="Borer"]])
22 +• Always store an uncorrected data file with all its bumps and warts. ([[Borer et al., 2009>>||anchor="Borer"]])
23 23 • Keep copies of your raw data as collected or as received, before any processing has been done. (Source #2)
24 24 • Unaltered images should be preserved at the highest resolution possible. (Source #51)
25 25
... ... @@ -26,7 +26,7 @@
26 26 === 5.3.2 Store data ===
27 27
28 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)
29 +• Store data in nonproprietary hardware formats. ([[Borer et al., 2009>>||anchor="Borer"]])
30 30 • Handle and Store Your Media With Care (Source #39)
31 31 • Routinely Inspect and Replace Data Discs (Source #39)
32 32
... ... @@ -48,7 +48,7 @@
48 48 ==== Devices ====
49 49
50 50 • Use a reliable device when making backups Source #4
51 -• Copies of original notebooks should be kept elsewhere for safekeeping. (Source #71)
51 +• Copies of original notebooks should be kept elsewhere for safekeeping. ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
52 52
53 53 ==== Process ====
54 54
... ... @@ -60,8 +60,8 @@
60 60 ==== What to backup ====
61 61
62 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)
63 +• Electronic data should be backed up on a disk with a hard copy ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
64 +• it is also advisable to create additional copies of your data that are off-line (not on the ([[Borer et al., 2009>>||anchor="Borer"]])
65 65
66 66 ==== Personnel ====
67 67
... ... @@ -70,11 +70,11 @@
70 70
71 71 === 5.3.4 Curate data ===
72 72
73 -• Electronic records need to be carefully monitored. (Source #71)
73 +• Electronic records need to be carefully monitored. ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
74 74
75 75 === 5.3.5 Provide data security ===
76 76
77 -• confidential data has to be stored in such a way that access cannot be available (Source #71)
77 +• confidential data has to be stored in such a way that access cannot be available ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
78 78
79 79 === 5.3.6 Perform data migration ===
80 80
... ... @@ -82,7 +82,7 @@
82 82
83 83 • maintain a redundant copy of your data for 30 days until the new device “settles in.” (Source #39)
84 84 Software
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)
85 +• continue using the version of the software that was originally used to create the data file to view and manipulate the file contents ([[DataONE, n.d.-f>>||anchor="DataONE-f"]])
86 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
87 87
88 88

XWiki Enterprise 5.1-milestone-1 - Documentation