11–14 of 14 posts
my 2 cents...
Hmmm... interesting concept.. I would add some features personally. A lot of the time typeahead calls for more than just a string, there should be away to display rich data objects in a template. Also there needs to be an API post endpoint so that data insertion/updates can be automated through an ETL process of some kind. my 2 cents...
Hmmm... interesting concept.. I would add some features personally. A lot of the time typeahead calls for more than just a string, there should be away to display rich data objects in a template. Also there needs to be an API post endpoint so that data insertion/updates can be automated through an ETL process of some kind. my 2 cents...
If you look at the Documentation section do you manage to find the API post you're looking for?
e.g
instead of PUT /api/datasource/ overriding the entire datasource each time..
allow an api user to insert lines of text or rich objects.
POST /api/datasource//suggestion
{
...
}
POST /api/datasource//suggestion
[
{ ...
},...
]
I also think you should support rich objects, allow for things like boosting rules, different templates for object types, spelling correction, synonyms. I think this type of service would be really useful.
Earlier quoted context omitted.
If you look at the Documentation section do you manage to find the API post you're looking for?
Hmm If I were to design this... I would make it so that you don't have to replace the entire data source each time... I think a "suggestion" entry in the data source should be represented as it's own entity in the API... e.g instead of PUT /api/datasource/ overriding the entire datasource each time.. allow an api user to insert lines of text or rich objects. POST /api/datasource/ /suggestion { ... } or support bulk i…
Anyway, if you're interested most of the code in the web-service relies on: