Closed leeharland closed 12 years ago
I agree that the search boxes can be improved and with the new onces that use the ConceptWiki API they get a lot better. Further improvements could be pagination on the results of the dropdown and formatting of the list. However, I am not sure we want to allow for free text entry to start a search. The queries fired against the CoreAPI needs to be initiated with an URI. Free text searches is not suited for the architecture as I understand it besides its lookup in ConceptWiki.
Agree, all queries against the core API must be on URI. I think this is more about how people enter text and search and whether or not the box is too intrusive i.e. it does autocomplete too well. By default, i think the user should be allowed to type and underneath options are presented but not automatically filled in but user has to select
In essence, make a box that works exactly like the google search box wired to the concept wiki api
Can be done more or less now. Only issue is responce time between the user input and the reply from ConceptWiki. Now it is fixed at 500 ms delay and only after the users puts in 4 chars. If the reply performance from the ConceptWiki API is fast enough we can make it Google-like quite easy. It is something we will have to test.
The interaction with the search boxes tends to throw people off. We should allow arbitrary text entry and search but this gets to be a bit off with the suggestion box. Google style