summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--issues/quality-control/enumerate-all-qc-checks.gmi4
-rw-r--r--issues/quality-control/gene-symbols.gmi4
-rw-r--r--issues/quality-control/qc-checks.gmi4
-rw-r--r--issues/quality-control/qc.gmi4
-rw-r--r--issues/quality-control/rewrite-qc-and-qc-uploads-in-python.gmi8
-rw-r--r--issues/quality-control/ui-design.gmi4
6 files changed, 18 insertions, 10 deletions
diff --git a/issues/quality-control/enumerate-all-qc-checks.gmi b/issues/quality-control/enumerate-all-qc-checks.gmi
index 90addc5..095eca1 100644
--- a/issues/quality-control/enumerate-all-qc-checks.gmi
+++ b/issues/quality-control/enumerate-all-qc-checks.gmi
@@ -5,8 +5,8 @@ We need to enumerate all QC checks and platforms that we want to test against.
## Tags
-* assigned: jgart, arthur
-* status: in progress
+* assigned: fredm, jgart, arthur
+* status: closed
* type: feature-request
* priority: high
* keywords: quality control
diff --git a/issues/quality-control/gene-symbols.gmi b/issues/quality-control/gene-symbols.gmi
index 63265ea..9a901cf 100644
--- a/issues/quality-control/gene-symbols.gmi
+++ b/issues/quality-control/gene-symbols.gmi
@@ -8,6 +8,6 @@ I'll need that mapping information for every strain, symbol etc... that has an a
Ideally, I can have those mappings in some machine-readable format like csv, json, etc...
-* assigned: jgart, arthur
+* assigned: fredm, jgart, arthur
-* in progress
+* status: closed
diff --git a/issues/quality-control/qc-checks.gmi b/issues/quality-control/qc-checks.gmi
index dc18f94..7568f8e 100644
--- a/issues/quality-control/qc-checks.gmi
+++ b/issues/quality-control/qc-checks.gmi
@@ -48,8 +48,8 @@ is allowed into the GeneNetwork will be 22,000 entries.
## Tags
-* assigned: jgart
+* assigned: fredm, jgart
* type: feature-request
* priority: high
-* status: unclear
+* status: closed
* keywords: quality control
diff --git a/issues/quality-control/qc.gmi b/issues/quality-control/qc.gmi
index 7b5d1e4..34eb077 100644
--- a/issues/quality-control/qc.gmi
+++ b/issues/quality-control/qc.gmi
@@ -34,8 +34,8 @@ The tricky part is still how the data is handled in escrow.
## Tags
-* assigned: jgart
+* assigned: fredm, jgart
* priority: high
* type: feature-request
-* status: in progress, beta
+* status: closed
* keywords: quality control
diff --git a/issues/quality-control/rewrite-qc-and-qc-uploads-in-python.gmi b/issues/quality-control/rewrite-qc-and-qc-uploads-in-python.gmi
index d17d637..a5e28b7 100644
--- a/issues/quality-control/rewrite-qc-and-qc-uploads-in-python.gmi
+++ b/issues/quality-control/rewrite-qc-and-qc-uploads-in-python.gmi
@@ -25,6 +25,14 @@ and were written in Common-Lisp. The two applications are:
In this document, the discussions of what is necessary to get the application in an acceptable state will be detailed and discussions to get there will also be included.
+Some other related issues for consideration, and superseded by this issue are:
+
+=> /issues/quality-control/enumerate-all-qc-checks Enumeration of QC checks for all platforms to test against
+=> /issues/quality-control/gene-symbols Mappings between representations of symbol names
+=> /issues/quality-control/qc-checks Some checks to run against files
+=> /issues/quality-control/qc Notes on original QC App ideas
+=> /issues/quality-control/ui-design Some UI design notes on the QC app
+
### Requirements
diff --git a/issues/quality-control/ui-design.gmi b/issues/quality-control/ui-design.gmi
index 029a2b8..db906d9 100644
--- a/issues/quality-control/ui-design.gmi
+++ b/issues/quality-control/ui-design.gmi
@@ -42,8 +42,8 @@ dataset so that we can inspect it."
## Tags
-* assigned: jgart
+* assigned: fredm, jgart
* type: feature-request
-* status: unclear
+* status: closed
* priority: medium
* keywords: UI, quality control