-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index: Index according to data type to facilitate range facets and queries. #370
Comments
Original Redmine Comment Right now, we are indexing all fields as text_en per #485 (comment) In practice, these are all astro fields right now (resolution.Spatial, coverage.RedshiftValue, etc.) and there's a doc called "Astro range queries" at https://docs.google.com/a/harvard.edu/document/d/19DB4heSUMTm2CNTJFjt9AUDfaaZUZvdoh1QGhedXWkk/edit?usp=sharing where I tried to spur some discussion of what the UI should look like. See also #3478 which was originally asking about the UI for dates. |
Closing as a duplicate and merging with #70. |
Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 3785, https://redmine.hmdc.harvard.edu/issues/3785
Original Date: 2014-03-27
Original Assignee: Philip Durbin
This ticket is a placeholder for indexing fields that contain something other than strings, eg. dates and floats, to support range queries for either facets or searches, depending on what is finally decided.
Example date: production date
Example float: Coverage Central Wavelength(m)
Related issue(s): #70, #485
Redmine related issue(s): 3478, 3900
The text was updated successfully, but these errors were encountered: