Closed lexvand closed 3 years ago
@lexvand Hi Lex,
Just want to check with you the work-flow for this timeseries export modal:
Is it correct?
@hoanphungt That's correct. With the addition that in step 1 in case the observation type filtering is active the user only selects those specific timeseries of the locations that are being selected. In case of no observation type filtering all related timeseries are added to the list.
@Derryrover Hi Tom,
Could you also review this PR: https://github.com/nens/lizard-catalogue/pull/256/? I think this is a good improvement for the work flow of the timeseries export task. I'd like to hear your opinion.
Kr, Hoan
@hoanphungt
Hi Hoan, Looks good ready to merge kr Tom
It is not intuitive that when you filter locations on a specific observation_type, select a location and make an export, you export all available timeseries of that location. Even the ones that have a different observation_type than you filtered on. This is very messy.
Instead of locations (and with that all related timeseries) you would like to select the separate timeseries. Can we change this in the TIMESERIES modal?