summaryrefslogtreecommitdiff
path: root/issues/modelling-phenotype-data.gmi
diff options
context:
space:
mode:
authorMunyoki Kilyungi2023-08-09 13:06:05 +0300
committerMunyoki Kilyungi2023-08-09 13:06:05 +0300
commitc6d155dcba795541f0f6216b4886521dc75d008f (patch)
tree50ff8da26e68a52bcebe0e1abc259b54dda401d2 /issues/modelling-phenotype-data.gmi
parent82b37aa36de9633c225df619abce21bcbbc7dd8f (diff)
downloadgn-gemtext-c6d155dcba795541f0f6216b4886521dc75d008f.tar.gz
Re-order agenda
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
Diffstat (limited to 'issues/modelling-phenotype-data.gmi')
-rw-r--r--issues/modelling-phenotype-data.gmi4
1 files changed, 2 insertions, 2 deletions
diff --git a/issues/modelling-phenotype-data.gmi b/issues/modelling-phenotype-data.gmi
index 203c38d..7438aef 100644
--- a/issues/modelling-phenotype-data.gmi
+++ b/issues/modelling-phenotype-data.gmi
@@ -106,8 +106,8 @@ Lipoteichoic acid (LTA) IL6 response of peritoneal macrophages in vitro (overnig
Date: TBA
+* We have inconsistent data as pointed above. What are peoples comments about it?
+
* How do we handle private/public data and metadata? Data is the vectors of numbers; metadata include pre/post publication/abbreviation. Is there a difference between the terms confidential public when it comes to storing data?
* Given the above problem, what's the FAIR way to go about it? How do we allow sharing data that even encourages the paranoid?
-
-* We have inconsistent data as pointed above. What are peoples comments about it?