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
With the aim of extending/encouraging use of COR, I’m interested in implementing autocomplete plugins for various frameworks e.g. JQuery (as an example), which would enable easy autocomplete functionality for query bars based upon terms present in COR.
Related code for this can be located here however ideally we would want to make it asynchronous such that every character entry results in a refined list of terms.
The text was updated successfully, but these errors were encountered:
This has been a very desirable feature for a long time. As you say, realized in the form of client modules that can be used in common frameworks. Of course, besides UX features on the client side, this will also demand improved backend performance especially as the triple store grows.
Question: Are you thinking of autocomplete for a particular ontology, or across all ontologies? The former is extremely valuable; the latter only valuable within the context of the repository (i.e., within a search within COR).
I will throw in also that the holy grail is to be able to autocomplete within a branch of an ontology.
Fast response in any case ends up being dependent on an indexing of the terms in ElasticSearch or similar. I don't think any triple store will natively be able to autocompletely that quickly (unless the triplestore explicitly implements that index).
With the aim of extending/encouraging use of COR, I’m interested in implementing autocomplete plugins for various frameworks e.g. JQuery (as an example), which would enable easy autocomplete functionality for query bars based upon terms present in COR.
Related code for this can be located here however ideally we would want to make it asynchronous such that every character entry results in a refined list of terms.
The text was updated successfully, but these errors were encountered: