Robert Sheridan
Robert Sheridan
Some fields in the return type are not currently supported, but they may be there for future use. Candidates for cleanup: - flatten return to not include "meta" and "data"...
MainTypes are currently not first class objects, but are properties of oncotree nodes. Do we want to capture the set of MainTypes independently and have a reference from the oncotree...
Should deprecate oncotree nodes be added into topbraid? Should we write code to support the display or filtering of oncotree nodes marked with Deprecated?
Some output types are not in sync with the true return types. Also some global meta information of the api (such as version, ...) needs to be set in order...
When expanding nodes in the oncotree, sometimes labels of nodes are rendered to the left of the node. We should make the label placement more consistent if possible (maybe this...
We can drop the branches for supplying the tumor_type.txt files for different versions.
Possible enhancements to "Version" class: - add a "modification_timestamp" property ... to show the time of last modification. Or add a new api endpoint to compute a stable md5checksum of...
This issue is related to #391 The /annotation web API endpoint will fail for hgvs format requests containing delete (del), indel, or duplication (dup) variant types when using the genome-nexus-vep...
There are 5 public interface functions implemented in class GenomicLocationAnnotationServiceImpl: - getAnnotation(GenomicLocation) - getAnnotation(String) - getAnnotations(List<GenomicLocation>) - getAnnotation(String genomicLocation, ...extra_args...) - getAnnotations(List<GenomicLocation> genomicLocations, ...extra_args...) It appears that function members (named...
This problem is evident when hgvs queries are submitted to a genome-nexus server running with a VEP prediction configuration using the embedded command line tool for the backend (using genome-nexus-vep...