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

Search/Browse: Improve facet UI for dates in fields such as "Publication Date" #70

Closed
eaquigley opened this issue Jul 9, 2014 · 12 comments
Labels
Feature: Search/Browse Type: Feature a feature request User Role: Guest Anyone using the system, even without an account UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@eaquigley
Copy link
Contributor

eaquigley commented Jul 9, 2014


Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3478, https://redmine.hmdc.harvard.edu/issues/3478
Original Date: 2014-02-03
Original Assignee: Philip Durbin


Date facets in DVN 3.x are sorted by count:

Production Date
2002 (2261)
1996 (1717)
1988 (424)
2010 (371)
2009 (314)

We should probably order by date:

2013-2014 (4)
2011-2012 (3)

Do we like this? Should we have a larger "span" than 2 years? What should the UI look like? Should there be a slider?

@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley eaquigley modified the milestones: Dataverse 4.0: Beta 5, Dataverse 4.0: In Review Jul 14, 2014
@eaquigley eaquigley assigned eaquigley and unassigned pdurbin Aug 15, 2014
@eaquigley eaquigley modified the milestones: Beta 5 - Dataverse 4.0, In Review - Post 4.0 Aug 15, 2014
@eaquigley
Copy link
Contributor Author

Review production data to figure out what the best range is. For post 4.0

@eaquigley
Copy link
Contributor Author

I'd like this date range slider to be like this where a user can either enter a range or slide to their preferred range:
image

@posixeleni could you identify the metadata fields that would need a date range slider?
@mheppler i've looked for date range slider components and found this one but don't think/know if it is compatible with Dataverse: https://github.com/projectblacklight/blacklight_range_limit Would you mind helping me look for more examples?
@pdurbin this seems to be the information from Solr on how to make this type of facet work: https://wiki.apache.org/solr/SimpleFacetParameters

@posixeleni
Copy link
Contributor

The following fields can benefit from the date range slider:

In the Citation Metadata

  • dsPublicationDate
  • dateOfDeposit
  • productionDate
  • distributionDate

But there are also compound fields with start and end dates that we can use the slider for:

  • Time Period Covered: timePeriodCoveredStart + timePeriodCoveredEnd (Citation Metadata)
  • Date of Collection: dateOfCollectionStart + dateOfCollectionEnd (Citation Metadata)

In the Astronomy Metadata:

  • coverage.Temporal: coverage.Temporal.StartTime + coverage.Temporal.StopTime

@pdurbin
Copy link
Member

pdurbin commented May 5, 2015

@eaquigley I like how that slider looks but I'm not sure it's compatible with JSF. There are a variety of Primefaces sliders here that may be of interest: http://www.primefaces.org/showcase/ui/input/slider.xhtml

I'd also like to point out that this issue has a hard dependency on #370 so that the data is available to Solr as numbers and dates rather than text.

@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@mheppler mheppler added the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jan 29, 2016
@pdurbin
Copy link
Member

pdurbin commented Feb 8, 2016

Feedback via @thegaryking at https://help.hmdc.harvard.edu/Ticket/Display.html?id=232324

"at https://dataverse.harvard.edu/dataverse/GovDept why is there a list of dates that goes only up to 2013 even though the individual items go until 2016? see screenshot" pubdate

It's probably time to take "finalize" out of the title of this issue. I'll try to come up with a better title. We should probably make this issue specifically about date ranges even though it depends on figuring proper indexing of range values as described in #370.

@pdurbin pdurbin changed the title Finalize UI for range facets (Citation Year facet) Search/Browse: Add UI and backend support for date range queries on fields such as "Publication Date" Feb 8, 2016
@eaquigley eaquigley added this to the 4.5 milestone Mar 30, 2016
@kcondon kcondon changed the title Search/Browse: Add UI and backend support for date range queries on fields such as "Publication Date" Search/Browse: Add UI and backend support for date and other range queries on fields such as "Publication Date" May 3, 2016
@kcondon
Copy link
Contributor

kcondon commented May 3, 2016

Including notes from and closing a similar, duplicate ticket #370. That also includes ranges for numbers generally such as wavelength.

@kcondon
Copy link
Contributor

kcondon commented May 3, 2016

From #370:
[Kevin]
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.
Right now, we are indexing all fields as text_en per #485 (comment)

[Phil]
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.

@djbrooke djbrooke removed this from the 4.5 milestone Jul 8, 2016
@djbrooke
Copy link
Contributor

djbrooke commented Jul 8, 2016

Removing from 4.5, will be reprioritized for a future release.

@mheppler mheppler changed the title Search/Browse: Add UI and backend support for date and other range queries on fields such as "Publication Date" Search/Browse: Improve facet UI for dates in fields such as "Publication Date" Oct 12, 2016
@pdurbin pdurbin added User Role: Guest Anyone using the system, even without an account and removed zTriaged labels Jun 30, 2017
@pdurbin
Copy link
Member

pdurbin commented May 23, 2018

The other day @rtreacy passed along some feedback to me from someone who looked at https://dataverse.harvard.edu and remarked something to the effect of "It looks like there's only old data here because it's 2018 and I don't see anything newer than 2016 under 'Publication Date'."

screen shot 2018-05-23 at 12 40 18 pm

If you click "More..." a couple times, you can tell there is in fact data from 2017 and 2018, but I'm sure we could do a better job with date facets like this:

screen shot 2018-05-23 at 12 43 14 pm

For all facets we show a count with the highest number on top but for dates it would probably be more interesting to see "all time" vs. "last five years" vs. "last six months" or whatever.

@pdurbin
Copy link
Member

pdurbin commented Aug 20, 2018

Over at #4977 @philippconzett suggests that we simply sort the publication year facet chronologically.

There was also a little discussion with @mdmADA about date facets at #4908 (comment)

@djbrooke
Copy link
Contributor

Closing in favor of #4977.

mderuijter pushed a commit to mderuijter/dataverse that referenced this issue Apr 28, 2021
JayanthyChengan added a commit to JayanthyChengan/IQSS-dataverse that referenced this issue Dec 1, 2021
@pdurbin
Copy link
Member

pdurbin commented Jun 23, 2022

I'd like this date range slider to be like this where a user can either enter a range or slide to their preferred range:
image

The idea of a date range UI component lives on in this new issue:

sekmiller pushed a commit that referenced this issue Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Search/Browse Type: Feature a feature request User Role: Guest Anyone using the system, even without an account UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

7 participants