The ulterior motive here is having a non-trivial feature to start with. This should serve to confirm we can get data out of ES and on to a web page.
The page should present a form which, when submitted, will return a list of matching codes.
We can query the code index with something like:
{ "query": { "match": { "label": "car" } } }
It might be worth investigating search templates. We can worry about semantic search/ word embeddings later.
Initially we can use the database snapshot. Maybe we could subset this (e.g. codes index only) and pop something onto s3 for CI? Once the ETL pipeline is a bit further developed, we can look at having proper fixture data.
The results could just show URI ("_id") and label for now.
The ulterior motive here is having a non-trivial feature to start with. This should serve to confirm we can get data out of ES and on to a web page.
The page should present a form which, when submitted, will return a list of matching codes.
We can query the
code
index with something like:It might be worth investigating search templates. We can worry about semantic search/ word embeddings later.
Initially we can use the database snapshot. Maybe we could subset this (e.g. codes index only) and pop something onto s3 for CI? Once the ETL pipeline is a bit further developed, we can look at having proper fixture data.
The results could just show URI (
"_id"
) and label for now.