A Capability Maturity Model for Research Data Management
CMM for RDM » 4. Data Dissemination » 4.1 Commitment to Perform

Changes for document 4.1 Commitment to Perform

Last modified by Arden Kirkland on 2014/06/06 13:01
From version 17.4
edited by Jian Qin
on 2014/03/08 11:32
To version 18.1
edited by crowston
on 2014/03/10 10:20
Change comment: There is no comment for this version

Metadata changes

Document author
XWiki.JiacrowstonQin

Content changes

... ... @@ -19,10 +19,10 @@
19 19 * What to be shared: this item usually involves data classification based on legal and/or contractual restrictions, public or internal domains, and so on.
20 20 * Compliance: whether submitting data to a data repository is a requirement or option for the members of the organization and when such submission should be completed. This lay out the expectations for sharing data. ([[Hale et al, 2003>>||anchor="Hale"]]). For example, "Datasets will be uploaded to the data catalog for availability within PISCO within one year of collection" ([[DataOne, 2013>>||anchor="PISCO"]]).
21 21 * Standards: tools for capturing metadata during data submission should be based on community and/or disciplinary metadata standards for ensuring metadata quality and interoperability.
22 -* Constraints: whether there is any legal or contractual bindings for the data to be shared and how such legal or contractual procedures should be followed. These constraints define (% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19.600000381469727px; text-align: start;" %)data access capabilities needed by community(s) of users ([[(%%)DataONE, 2011a>>||anchor="DataONE-a" style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: start; line-height: 19.600000381469727px; text-decoration: underline;"]](% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19.600000381469727px; text-align: start;" %)) and the likely final destination and likely mode of dissemination of your data ([[(%%)Hook et al, 2010>>||anchor="Hook" style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: start; line-height: 19.600000381469727px; text-decoration: underline;"]](% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19.600000381469727px; text-align: start;" %)).
22 +* Constraints: whether there is any legal or contractual bindings for the data to be shared and how such legal or contractual procedures should be followed. These constraints define (% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19.600000381469727px; text-align: start;" %)data access capabilities needed by community(s) of users ([[DataONE, 2011a>>||anchor="DataONE-a" style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: start; line-height: 19.600000381469727px; text-decoration: underline;"]]) and the likely final destination and likely mode of dissemination of your data ([[Hook et al, 2010>>||anchor="Hook" style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: start; line-height: 19.600000381469727px; text-decoration: underline;"]]).
23 23
24 24 (((
25 -(% style="font-size: 14px; line-height: 1.4em;" %)Sharing is good for the research enterprise as a whole ([[(%%)Columbia Center for New Media Teaching and Learning, n.d.>>||style="font-size: 14px; line-height: 1.4em;"]](% style="font-size: 14px; line-height: 1.4em;" %)), and having data sharing policies ensures the institutional commitment to making it happen and to reducing the level of effort required to prepare data for sharing. ([[(%%)Hook et al~~,~~, 2010>>||style="font-size: 14px; line-height: 1.4em;"]](% style="font-size: 14px; line-height: 1.4em;" %)).
25 +(% style="font-size: 14px; line-height: 1.4em;" %)Sharing is good for the research enterprise as a whole ([[Columbia Center for New Media Teaching and Learning, n.d.>>||style="font-size: 14px; line-height: 1.4em;"]]), and having data sharing policies ensures the institutional commitment to making it happen and to reducing the level of effort required to prepare data for sharing. ([[Hook et al~~,~~, 2010>>||style="font-size: 14px; line-height: 1.4em;"]]).
26 26 )))
27 27
28 28
... ... @@ -36,6 +36,14 @@
36 36
37 37 == 4.1.3 Develop data confidentiality policies ==
38 38
39 +
40 +Project data may be sensitive. For example, data about identifiable human subjects and medical records must be protected from disclosure. In other cases, projects may want to restrict access to data that is still being processed.
41 +
42 +Developing data access policies is necessary to ensure that sensitive data are identified and properly protected and that responsibilities for data security are understood.
43 +
44 +Projects should develop policies that identify what kinds of data are being collected, who may access the data and under what circumstances and who may make changes to data and under what circumstances.
45 +
46 +
39 39 Because:
40 40 Consider that the release of early data before publication can jeopardize the ability of an investigator to be the first to publish a research finding ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
41 41 Data that can lead to patents also cannot be shared prematurely. ([[Columbia Center for New Media Teaching and Learning, n.d.>>||anchor="Columbia"]])
... ... @@ -45,7 +45,6 @@
45 45 • Determine if the data has any confidentiality concerns ([[DataONE, 2011b>>||anchor="DataONE-b"]])
46 46 • Document data concerns identified and determine overall sensitivity
47 47
48 -
49 49 == References ==
50 50
51 51 {{id name="Black-Rock"/}}Black Rock Forest Consortium. (2007). Data submission protocol. Retrieved from [[http:~~/~~/www.blackrockforest.org/docs/scientist-resources/DataResources/DataSubmission.html>>url:http://www.blackrockforest.org/docs/scientist-resources/DataResources/DataSubmission.html||rel="__blank"]].

XWiki Enterprise 5.1-milestone-1 - Documentation