A Capability Maturity Model for Research Data Management
CMM for RDM » 5. Repository Services and Preservation » 5.1 Commitment to Perform

Changes for document 5.1 Commitment to Perform

Last modified by Arden Kirkland on 2014/05/18 23:10
From version 18.1
edited by crowston
on 2014/03/10 10:15
To version 19.1
edited by crowston
on 2014/03/10 11:13
Change comment: There is no comment for this version

Content changes

... ... @@ -8,17 +8,17 @@
8 8
9 9 === 5.1.1 Develop data backup policies ===
10 10
11 -To backup data means to make a copy of the data that can be used in case the primary data store is damaged or lost. The goal of developing data back up policies is to provide guidance to data curators about how data should be backed up and to identify roles and responsibilities of personnel for creating, maintaining and using backups ([[DataONE, 2011a>>||anchor="DataONEa"]]).
11 +To backup data means to make a copy of the data that can be used in case the primary data store is damaged or lost. The goal of developing data backup policies is to provide guidance to data curators about how data should be backed up and to identify roles and responsibilities of personnel for creating, maintaining and using backups ([[DataONE, 2011a>>||anchor="DataONEa"]]).
12 12
13 13 It is important to define backup policies to ensure that data are being backed up appropriately, that backups are properly protected and that responsibilities are clearly delineated.
14 14
15 -The backup policy should describe what data need to backed up and how frequently, where backups are kept and for how long, and who can access them ([[DataONE, 2011b>>||anchor="DataONEb"]]). The policy may also dictate the hardware and software to be used. If backups are not automatic, the policy should state who performs the backups. The policy should also state how and how often backups are validated.
15 +The backup policy should describe what data need to backed up and how frequently, where backups are kept and for how long, and who can access them ([[DataONE, 2011b>>||anchor="DataONEb"]]). The policy may also dictate the hardware and software to be used. If backups are not automatic, the policy should state who performs the backups. The policy should also state how and how often backups are validated and what metrics are used to evaluate backups.
16 16
17 17 === 5.1.2 Develop data curation policies ===
18 18
19 -Projects create a variety of kinds of data, as well as data documentation and analysis scripts or tools. Data curation policies state what data should be preserved long-term and what data can be discarded. The goal of developing data curation policies is to provide guidance for data curators and users on deciding what data should be preserved long-term.
19 +Projects create a variety of kinds of data, as well as data documentation and analysis scripts or tools. Data curation policies state what data should be preserved long-term and what data can be discarded. The goal of developing data curation policies is to provide guidance for data curators and users on deciding what data should be preserved.
20 20
21 -Developing curation policies is necessary because keeping all data is neither practical nor economically feasible ([[DataONE, 2011c>>url:http://rdm.ischool.syr.edu/xwiki/resources/js/xwiki/wysiwyg/xwe/69418DB5FB08918068E66A3255D5BA3F.cache.html#DataONEc]]). Only datasets that have significant long-term value and that cannot be recreated or that are costly to reproduce should be preserved.
21 +Developing curation policies is necessary because data may have long-term value that should be preserved, but keeping all data is neither practical nor economically feasible ([[DataONE, 2011c>>url:http://rdm.ischool.syr.edu/xwiki/resources/js/xwiki/wysiwyg/xwe/69418DB5FB08918068E66A3255D5BA3F.cache.html#DataONEc]]). Only datasets that have significant long-term value and that cannot be recreated or that are costly to reproduce should be preserved.
22 22
23 23 In developing curation policies, consider the tradeoff between the cost of preservation due to the dataset size or repository policies against the potential value of the data to the user community ([[Hook et al, 2010>>url:http://rdm.ischool.syr.edu/xwiki/resources/js/xwiki/wysiwyg/xwe/69418DB5FB08918068E66A3255D5BA3F.cache.html#Hook]]). Funding agencies or institutions may also have requirements and policies governing contribution to repositories ([[DataONE, 2011c>>url:http://rdm.ischool.syr.edu/xwiki/resources/js/xwiki/wysiwyg/xwe/69418DB5FB08918068E66A3255D5BA3F.cache.html#DataONEc]]).
24 24

XWiki Enterprise 5.1-milestone-1 - Documentation