From f3706645d0eec4dba2a8ff4159bbb4a945c6e540 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Wed, 23 Mar 2022 08:41:03 +0300
Subject: Add `Phenotype state in a hash` Issue from GitHub

---
 issues/capture-phenotype-state-in-a-hash.gmi | 30 ++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 issues/capture-phenotype-state-in-a-hash.gmi

(limited to 'issues')

diff --git a/issues/capture-phenotype-state-in-a-hash.gmi b/issues/capture-phenotype-state-in-a-hash.gmi
new file mode 100644
index 0000000..558f018
--- /dev/null
+++ b/issues/capture-phenotype-state-in-a-hash.gmi
@@ -0,0 +1,30 @@
+# Capture state of phenotypes in a HASH
+
+## Tags
+
+* assigned: pjotrp, zsloan
+* type: enhancement, feature-request
+* status: in progress
+* priority: medium
+* keywords: phenotypes, REST, UI
+
+## Description
+
+=> https://github.com/genenetwork/genenetwork2/issues/551 From GitHub
+
+To represent the state of the database we need to start using HASH values or UUIDs. For phenotypes we should create these for phenotype columns within a dataset - i.e. the column one uses for mapping. @zsloan this is metadata and I suggest we use RDF so we can have a historic view of changes in datasets. A change can be described as table - mapped to RDF:
+
+```
+dataset -> hash -> date -> submitter
+```
+
+The hash can be computed over data that is streamed over the REST API - so people van validate client side (as a feature).
+
+
+
+
+This mentions RDF - which I think
+
+* aruni
+
+was involved in. I (fredm) have tagged them here, for their evaluation of the relevance of this issue to them.
-- 
cgit v1.2.3