Define v0, v1, v2 search features for TERRA

[max-zilla]

Restructuring from #46 and #47. This issue is a discussion to decide critical features to support searchwise. I'll make a first cut based on past discussions. We can create action item tasks for v0, v1 features as we begin work on them.

v0 https://opensource.ncsa.illinois.edu/bitbucket/projects/CATS/repos/clowder/pull-requests/994/overview this is my initial pull request to overhaul ElasticSearch in Clowder. Forms necessary foundation for future improvements, but benefits limited to Clowder only. Should generally support finding datasets by time, metadata properties.

• [x] properly index arbitrary metadata fields by type, allowing for numeric searches, date range searches, autocomplete suggestions on field selectors
• [x] substantial performance speedups

v1 This could focus on the geospatial search aspects, which I think will be critical for an intuitive user experience. Among other ideas:

• [ ] find datasets by location within a bounding box
• [ ] view map visualization of field that can be used to define bounding box of interest
• [x] GeoDashboard integration for tile visualizations and filtering
• [ ] filter by genotype, experiment, date range

v2 merged w/ v1 At this point we have discussed an "overlord" search page that acts as a frontend to searching Clowder, Bety, and future databases.

• [ ] UI and design for faceted search page that could act as landing page as well
• [ ] integration between databases - find traits in BETY according to identified datasets in Clowder and vice versa
• [ ] potentially aggregate or visualize traits/data resulting from searches
• [ ] link to original data in home web apps as appropriate

https://github.com/terraref/reference-data/issues/9 These search capabilities should be reflected in API endpoints as well. There is some discussion in this issue of use cases; closing that old issue so discussion can continue here.

[dlebauer]

Additional use cases:

• 222 query polygons to clip hyperspectral images

• https://github.com/terraref/reference-data/issues/112: find images from which traits in BETYdb were derived

[max-zilla]

@craig-willis and I should talk about this and how we might break the task down between us.

[max-zilla]

we should schedule a meeting: max @dlebauer @Zodiase @craig-willis @robkooper and/or Luigi (geodashboard rep) @jterstriep (if so inclined)

...to figure out v1 with regard to:

• whether or not to use Geodashboard, v2 (w charts) or v3 (react.js, no charts)
• whether to create our own mapping/visualization component
• whether faceted search could be sufficient to make map views less necessary

Basically nail down initial search offering.