Open falkamelung opened 3 years ago
stackTom
commented
3 years ago These could be put into the search form we currently have. If by startDate and endDate, you mean these to be url parameters, they must be called something different, as we use these parameters to specify the start and end date for the plots now that we have bookmarkable URL's.
falkamelung
commented
3 years ago Issue https://github.com/geodesymiami/insarmaps/issues/21 is related. This is addressed in the last image.
These items could be addressed by replacing 'All items, Show last year data' by a simplified date search: 'Last month' 'Last two months' 'Last year' 'All data'
The date search is the most used search (the others are almost never used). Any ideas how to highlight the data search? Giving immeadiately the options is one possibility (without the need to hover over the dropdown symbol). Maybe you have some other ideas.
stackTom
commented
3 years ago I am a bit confused. So, we need a new Date search bar. When you click on the little upside down triangle, it sets the mode for the date search. And then the actual datasets matching that date search appear under the last ingests search bar?
falkamelung
commented
3 years ago the Date and Last ingest ingest are completely independent search functions. The Date search does nearly the same as we currently have, except that there are three options and it is at the top. This is high priority.
The Last ingest would give you the last ingests. They could be displayed anywhere. Under the search bar is a possible siggestion. I did a mistake with the screenshot. Below a correction. When clicking on one of the granule names it would show them in the same way as selecting from the map. Is that easy to implement? It is of low priority.
stackTom
commented
3 years ago Last ingests would be easy to implement. The problem is we don't have this information in the database. And there is no way to see the date a table was ingested into postgresql database, I just googled. So, we would have to add this as a new attribute in the ingest script and reingest the datasets.
falkamelung
commented
3 years ago We have a 'history' attribute. But I am not sure it contains the time.
Given that our time-series are now 5 years or longer we should think about more options. I am just summarizing some ideas. Don't do anything we should discuss whether it is worth and how to implement it.
After an eruption people will be interested into the period after the eruption but not before the eruption. It would be good to have the option to give a start date and end date (preferably remembered by the system -- how? a locally stored file?) When you click on a time series everything will be displayed starting with this date. But through the regular clicking you can go to display the entire time series if you wish.
if startDate and endDate have been selected, it should show only those datasets that fall within this time period. If I say startDate=2019-01-01 it should not show anything that ends in 2018.
Updating frequency: do we have this information? Then we could use it:
in the search window (or elsewhere) the user could select 1 month or 6 months. If selected only those data sets with at least 2 updated in the last month (6 months) will be displayed.