diff options
| author | Frederick Muriuki Muriithi | 2023-08-11 12:12:33 +0300 |
|---|---|---|
| committer | Frederick Muriuki Muriithi | 2023-08-11 12:13:13 +0300 |
| commit | 4e016e43fd05202287730915d129daaed1a02efc (patch) | |
| tree | 7cdc85263bc4cf201d391aaf216fea62c4527dbb | |
| parent | 4c916b6533c72eaf5ee3b0f5bfc7ed69281c43f0 (diff) | |
| download | gn-gemtext-4e016e43fd05202287730915d129daaed1a02efc.tar.gz | |
Update issue: Only approved diffs are stored.
| -rw-r--r-- | topics/editing/improving-metadata-audit.gmi | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/topics/editing/improving-metadata-audit.gmi b/topics/editing/improving-metadata-audit.gmi index dc9f65b..5bcf01c 100644 --- a/topics/editing/improving-metadata-audit.gmi +++ b/topics/editing/improving-metadata-audit.gmi @@ -23,7 +23,13 @@ This document proposes that we do improvements to the existing system to mitigat ## Notes -Identifying trait diffs: +### Saving Diffs in Database + +It turns out, we only store diffs in the database that have been approved. The diffs awaiting processing, or those that have been rejected are not stored. + +This makes it a little easier to handle some of the newer features requested. + +### Identifying Trait Diffs * Phenotype diffs can be identified with the `trait_name` and `phenotype_id` keys in the `json_diff_data` field * Probesets diffs can be identified with the `probeset_name` key in the `json_diff_data` field |