Skip to content
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

Closed
eaquigley opened this issue Jul 9, 2014 · 4 comments

Comments

@eaquigley
Copy link
Contributor

eaquigley commented Jul 9, 2014


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


@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2014-03-27T18:00:09Z


Note: there is already a ticket related to date range facets, #3478

@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-06-03T01:44:30Z


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.

@eaquigley eaquigley modified the milestones: Dataverse 4.0: Beta 5, Dataverse 4.0: In Review Jul 15, 2014
@eaquigley eaquigley modified the milestones: In Review - Dataverse 4.0, Beta 9 - Dataverse 4.0, 4.1 Nov 10, 2014
@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
@pdurbin pdurbin removed their assignment Jan 21, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@kcondon
Copy link
Contributor

kcondon commented May 3, 2016

Closing as a duplicate and merging with #70.

@pdurbin
Copy link
Member

pdurbin commented Sep 27, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants