dondi

@ntran18 observes that the gene tables for GRNs and PPIs are distinct as of now. The GRN gene table appears to have an additional column over the PPI gene table....

With PR #1111 merged, we will need a database reload to test the off-by-one fix. @ntran18 can choose whether to try this first before moving on to the unioned gene...

Intermediate plan: before going into the Intermine API logic, the gene tables can be unioned after the fact for now. Further analysis can be the next step

Time to revisit this next, to ensure robustness of the next release. 1. Audit and add new features to the client-side testing document 2. Update derived files (wiki, Markdown) 3....

@igreen1 @luluriffic @Onariaginosa can review this with @dondi at the next available windows in order to perform these updates and use it to identify further potential bugs.

This type of documentation is always good to have but is more of a moving target due to continuing addition of features…may take a while before we either have enough...

We will table the full union work for after this semester due to what’s involved; we’ll explore the SQL `UNION` command in order to make the database do the heavy...

So the immediate goal for now is to ensure that @ntran18’s code refactor is indeed functional and we can close the semester with that as the final accomplishment

Here is a PDF capture of the Google Doc above as of 10/2: [GRNsight database.pdf](https://github.com/user-attachments/files/17235636/GRNsight.database.pdf)

Returning to this issue will require multiple steps: 1. Review the _featureList.json_ file and just update _what's there_ to make sure that it's in sync with the latest version of...