Closed edwardlavender closed 1 year ago
the timestamp column relates to the when the data were retrieved for creating the dataset, and it's not related to the sampling time. We'll try to reformat if enough time, but it's really just to indicate when the integration of datasets was done. This is implications for when we matched the surveys with the taxonomy for instance
Thanks for this clarification! That makes sense. If possible, you might want to consider renaming the timestamp
column to make its meaning clearer & prevent accidental misuse (e.g., timestamp_data_retrieval
). A separate column with the time stamps of surveys (year/month/day + time where available) could be useful.
since it's detailed in the manuscript in Table 2, I won't change the name
This repo is a fantastic resource!
I noticed an issue with the match between time stamps and recorded years/months/days:
I think the years/months/day columns are probably correct and the
timestamp
column has been incorrectly defined? The entities in that column vary in structure (e.g. yyyy-mm-dd, yyyy-mm and mm/yyyy).I think at least some surveys record the time of day of each trawl deployment and/or retrieval as well. It might be useful to retain that information.