Closed tmushayahama closed 3 years ago
I think that autocomplete is likely out of scope for minerva--this sounds like a Solr job. I don't think it's wise to use Minerva as a wrapper for another service.
Also see: https://github.com/geneontology/simple-annoton-editor/issues/50#issuecomment-516625957
Given some extra time, I think its worth doing the experiment to see if the go-lego blazegraph now lurking in Minerva could support this issue. If it could, it would provide the very nice feature of making all of the ontology-related things that Noctua needs be delivered directly from Minerva. This makes testing, coherence, maintenance and long term understanding easier.
@goodb It's possible, but I'm honestly a little dubious, as I think that things like wildcards (exact matches over partial matches), weighted search against different fields (label and synonyms), and facets/pins will still be needed and I'd like to avoid multiple AC sources if possible. That said, if you think that this could be an easy thing or a big win without starting to re-implement Solr, it can be explored a little.
Add autocomplete (search) API to Minerva - for use of clients to have same data and order
Endpoint
api/search/xyz it is still kinda search not autocomplete
Parameters
Return
A list of matched entities
Implementation: a wrapper of the current solr. Keep in mind that this can be used for function companion or search database function by adding apect to the request and adding evidence on the return
tagging @lpalbou @goodb @cmungall @kltm @balhoff any thoughts?