A Capability Maturity Model for Research Data Management

Changes for document 5.2 Ability to Perform

Last modified by Arden Kirkland on 2014/06/06 13:02
From version 20.1
edited by Arden Kirkland
on 2014/03/14 14:37
To version 21.1
edited by Arden Kirkland
on 2014/03/14 14:43
Change comment: contextual links

Content changes

... ... @@ -14,7 +14,7 @@
14 14
15 15 Projects need to select the hardware and software technology platforms on which they will store their data. The selection process should be started early in the project to allow time to collect and evaluate information on available options, such as system documentation or experiences from other users ([[DataONE, 2011a>>||anchor="DataONEa"]]). Larger projects may want to pilot several alternatives before making a choice. Relevant system features include functionality, in particular, support for multimedia data ([[DataONE, 2011e>>||anchor="DataONEe"]]), fit to project needs (e.g., capabilities compared to the expected volume of data and number of users), ease of use and support. Relevant hardware features include capacity, reliability and expected lifetime (e.g., for hard drives) ([[DataONE, 2011c>>||anchor="DataONEc"]]).
16 16
17 -Project may develop their own data archives in addition to working stores for data being actively used. Rather than archiving data themselves, projects may decide to deposit data in an existing repository. Again, the process of selecting a repository should start early to provide enough time to identify and evaluate alternatives. As well, repositories may have particular requirements that will shape the project's data management plan ([[DataONE, 2011d>>||anchor="DataONEd"]]). A further possibility for data preservation is joining a digital preservation network, that is, collaborating with other institutions or projects to cooperatively archive data (e.g., the Digital Preservation Network, http:~/~/dpn.org/, or Chronopolis, http:~/~/chronopolis.sdsc.edu).
17 +Project may develop their own data archives in addition to working stores for data being actively used. Rather than archiving data themselves, projects may decide to deposit data in an existing repository. Again, the process of selecting a repository should start early to provide enough time to identify and evaluate alternatives. As well, repositories may have particular requirements that will shape the project's data management plan ([[DataONE, 2011d>>||anchor="DataONEd"]]). A further possibility for data preservation is joining a digital preservation network, that is, collaborating with other institutions or projects to cooperatively archive data (e.g., the Digital Preservation Network, [[http:~~/~~/dpn.org/>>url:http://dpn.org/||rel="__blank"]], or Chronopolis, [[http:~~/~~/chronopolis.sdsc.edu>>url:http://chronopolis.sdsc.edu||rel="__blank"]]).
18 18
19 19 == 5.2.2 Develop business models for preservation ==
20 20

XWiki Enterprise 5.1-milestone-1 - Documentation