summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2023-09-05 05:44:50 +0300
committerFrederick Muriuki Muriithi2023-09-05 05:44:50 +0300
commit0ae120928d65dd04edc5bc195d03d7b611311310 (patch)
treefe9bf57c3614eca8eee1da8de2b7509a19225944
parent2a94a9bbd2d65c78cbda00814ed07d46c5c95951 (diff)
downloadgn-gemtext-0ae120928d65dd04edc5bc195d03d7b611311310.tar.gz
Link to GN1 case-attributes code.
-rw-r--r--topics/editing/case_attributes.gmi8
1 files changed, 3 insertions, 5 deletions
diff --git a/topics/editing/case_attributes.gmi b/topics/editing/case_attributes.gmi
index a328e46..a93a47b 100644
--- a/topics/editing/case_attributes.gmi
+++ b/topics/editing/case_attributes.gmi
@@ -30,11 +30,9 @@ We need to differentiate two things:
As is currently implemented (as of before 2023-08-31), both the labels and values are set at group level.
-Having the labels at the group level is (arguably) acceptable; the value on the other hand, vary from experiment to experiment (dataset), and could be different for the same strain/sample.
-
-For posterity, I (Frederick) do not think the labels should go much beyond the group level, e.g Sex as an attribute applies for Human, and mice, but not so much for yeast and E. Coli.
-
-The focus now is to modify the database schema to allow the case-attribute values to vary by dataset (experiment).
+A look at
+=> https://github.com/genenetwork/genenetwork1/blob/0f170f0b748a4e10eaf8538f6bcbf88b573ce8e7/web/webqtl/showTrait/DataEditingPage.py Case-Attributes on GeneNetwork1
+is a good starting point to help with understanding how case-attributes were implemented and how they worked.
## Status