Desired State
The SNV Table on both the region and gene dashboard should indicate which variants are eQTLs.
Rationale
This would answer the question, "which of the variants are eQTLs?" while the user is on the SNV tab.
Context
The data backing the SNV table is large. The table makes requests to the API for data when it is initially mounted and whenever the user scrolls the table. That behavior avoids attempting to load a large quantity of data all at once.
The data backing the eQTLs is comparatively very small. However, attempting to merge it with the SNV data as the user loads data could be done, but there's considerations for how the data is subsequently handled by the tabulator tables library and how it needs to be updated when various table operations take place.
Proposed Solution
The backing database is mongo, and the individual documents of a collection don't need have the same fields. A field is_eqtl: true could be added to the SNVs that are eQTLs during or shortly after the import of the eQTL collection into the data backend. In this way, the SNV table would still be powered by a single API call, and a column could be added with a Y|N indicating if a variant is an eQTL.
Desired State
The SNV Table on both the region and gene dashboard should indicate which variants are eQTLs.
Rationale
This would answer the question, "which of the variants are eQTLs?" while the user is on the SNV tab.
Context
The data backing the SNV table is large. The table makes requests to the API for data when it is initially mounted and whenever the user scrolls the table. That behavior avoids attempting to load a large quantity of data all at once.
The data backing the eQTLs is comparatively very small. However, attempting to merge it with the SNV data as the user loads data could be done, but there's considerations for how the data is subsequently handled by the tabulator tables library and how it needs to be updated when various table operations take place.
Proposed Solution
The backing database is mongo, and the individual documents of a collection don't need have the same fields. A field
is_eqtl: truecould be added to the SNVs that are eQTLs during or shortly after the import of the eQTL collection into the data backend. In this way, the SNV table would still be powered by a single API call, and a column could be added with aY|Nindicating if a variant is an eQTL.