You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No route allows to get meta for multiple genes, to avoid multiple calls to the API / SOLr.
The refactoring of the API is a long pending work that should be prioritized at some point.
Note: anti patterns to access directly those meta from SOLr are possible, but we do need to keep an abstraction level to stop being stucked with certain technologies and versions and allow to rewrite only isolated parts of the platform when needed.
The text was updated successfully, but these errors were encountered:
I second this. It would be great for my current project as I do not want to overwhelm the API by many requests and getting all the data at once would be awesome.
Right now, queries like https://api.geneontology.org/api/search/entity/autocomplete/WB:WBGene00019444?category=gene&rows=1 can be used to retrieve some basic meta of a gene. Equivalent can be done with http://api.geneontology.org/api/search/entity/WB%3AWBGene00019444?rows=20&start=0.
No route allows to get meta for multiple genes, to avoid multiple calls to the API / SOLr.
The refactoring of the API is a long pending work that should be prioritized at some point.
Note: anti patterns to access directly those meta from SOLr are possible, but we do need to keep an abstraction level to stop being stucked with certain technologies and versions and allow to rewrite only isolated parts of the platform when needed.
The text was updated successfully, but these errors were encountered: