Instead of storing PGX information globally in a required .json object I have added a startup protocol that looks for pgx Data upon initial server initialization. This will parse the json object and put the data into two separate documents within the database.
Additionally, I built an interface that allows users to easily interact with the PGX data. They can now modify it in any way ie. add more markers to a haplotype, change haplotype names. They can even add new markers. The only thing they cannot do at this point is modify the current gene name. once assigned this is set (at least for the time being).
The next step will be implementing a similar page as this for markers, allowing you too add, delete or modify the current markers stored in the database.
Also in the FAR future, add an upload function to enable a file with MANY different haplotypes to uploaded.
Instead of storing PGX information globally in a required .json object I have added a startup protocol that looks for pgx Data upon initial server initialization. This will parse the json object and put the data into two separate documents within the database.
Additionally, I built an interface that allows users to easily interact with the PGX data. They can now modify it in any way ie. add more markers to a haplotype, change haplotype names. They can even add new markers. The only thing they cannot do at this point is modify the current gene name. once assigned this is set (at least for the time being).
The next step will be implementing a similar page as this for markers, allowing you too add, delete or modify the current markers stored in the database.
Also in the FAR future, add an upload function to enable a file with MANY different haplotypes to uploaded.