Data Management Plan

[gracelewin]

1. How much data will be collected and how will it be treated?

   • We are starting with a single day of data, and planning to scale it up to the data from the entire year of 2020.
   • For all of 2020, for an 8 day composite, there are 588,350 observations per buoy.
   • We plan to get the data for 3 buoys.
   • We are extracting the data for each buoy and using rbind() to bind the data from the different buoys together into one dataframe.
   • We are going to join the buoy data to the satellite data by time.
   • The data that will be collected from the NASA Aqua satellite will be sea surface temperature and chlorophyll.
   • We created a 0.5 latitude by 0.5 longitude grid around the East, West, and Santa Monica buoy. The satellite data will be collected within this box around the buoys.

2. How much time is needed to manage the data and who will be responsible for doing so?

   • 3 weeks is needed to create the database, and once completed, it will not be updated for the year 2020dataset.
   • All members of the team will be responsible for managing the data.

3. How long should the data be preserved and where is the best location to do so?

   • The data will be preserved on the KNB data repository indefinitely.
   • The KNB repository is set up to store data for long periods of time.

4. Are there any legal constraints associated with acquiring, using and sharing project data?

   • There are no restrictions for using this data from NOAA, but it is not intended to be used for legal purposes, as it may contain inaccuracies.

Data Provenance: Sea_Breeze_NCEAS_Data_Provenance

[brunj7]

Looking great! Generally, it is a good practice to try to detail roles (getting the data, cleaning the data, doing analysis X, ...) a little bit more as it helps to think about the various tasks that will be required, including their potential dependancies