From 37e17b9a2c50a9f388ba00099b983a6bda4f4ae3 Mon Sep 17 00:00:00 2001
From: Ted Laderas <roshioshi@gmail.com>
Date: Fri, 9 Aug 2024 10:23:58 -0700
Subject: [PATCH] update

---
 filtering.qmd | 44 ++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 42 insertions(+), 2 deletions(-)

diff --git a/filtering.qmd b/filtering.qmd
index 9b9b807..dd518c8 100644
--- a/filtering.qmd
+++ b/filtering.qmd
@@ -13,8 +13,6 @@ A secondary purpose of filtering is when you want to view your results in the re
 
 # Filtering Roadmap
 
-
-
 ```{mermaid}
 flowchart TD
   A["Results Viewer"] --> B
@@ -178,6 +176,48 @@ graph TD
 
 Filters can be exported and saved as JSON files for further reuse. They can be applied to a new set of variants in the GUI, or can be applied to result SQLite files on the command line. 
 
+Here's an example of what a filter looks like in the JSON format:
+
+```
+{
+  "sample": {
+    "require": [],
+    "reject": []
+  },
+  "genes": [],
+  "variant": {
+    "operator": "and",
+    "rules": [
+      {
+        "operator": "and",
+        "rules": [
+          {
+            "column": "clinvar__sig",
+            "test": "hasData",
+            "value": null,
+            "negate": false
+          },
+          {
+            "column": "clingen__disease",
+            "test": "hasData",
+            "value": null,
+            "negate": false
+          }
+        ],
+        "negate": false
+      }
+    ],
+    "negate": false
+  },
+  "smartfilter": {},
+  "samplefilter": {
+    "operator": "and",
+    "rules": [],
+    "negate": false
+  }
+}
+```
+
 # Applying JSON filters in the GUI