api
api copied to clipboard
Autocomplete on non-q query params? -
Should there be a way to autocomplete on the URI index, rather than on the text index? I would expect not, but it seems asymmetric if query terms are not required (e.g. for semantic tag search).
Nullified by the change to include URIs in the q param.
Discussed use cases for autocomplete on other params (especially user) but while we can see the potential, we don't want to go there yet. Other params are either not susceptible to autocomplete (e.g. date), limited in number of possibilities (e.g. motivation) or will be provided by the user or client (q and box)
Should this be included in Search 3.0? (thumbs up/down on the comment please)
I don't see convincing use case for autocomplete on motivation
, date
or user
(a URI)
Closing, won't fix