Search - Control over and’d and or’d search fields
Status
-
Proposed -
Trialing -
Under review -
Approved -
Retired
Context & Scope
- If specify by well name, they’re or’d together; in another scenario the combined results are and’ed
- Ideally would like to specify this in standardized way, maybe in terms of Elastic query syntax
- Would it make sense to have a plugin which lets you add index/denormalized info where special behaviours are required? - Raj
- In early parts of project typically need broad searches, then later need deep search.
R2 workaround is they clients run multiple queries and combine together.