VPR Data Sharing

[EOGrady21]

With the goal of sharing VPR data on CIOOS & OpenData, I'm going to start an overhaul of vpr_save()

This function should be able to output data & metadata ready for publication, meeting a series of standards and using controlled vocabularies.

I've started a map of current metadata and data column names to BODC:P01 and DwC vocabularies. I will leave original column names intact within the package to avoid any unexpected errors.

Here are the tasks to be completed:

- [ ] confirm mapped (meta)data names with @kevinsorochan and OpenData expert (Brian Bower)
- [ ] translate historical data into standardized csv format with new column names

• confirm metadata requirements & list of values
  - [ ] column names & definitions (with units) from csv
  - [ ] spatial info (geographic)
  - [ ] collection info (platform & instrument)
  - [ ] QC info
• programmatically generate metadata files in R to accompany csv files
  - [ ] update vpr_save() to output standardized csv files
• functionalize metadata generation in R
  - [ ] push historical data to OpenData & CIOOS

[EOGrady21]

I decided to create a new function vpr_export() instead of messing with vpr_save(), in the interest of backwards capability.

vpr_export() is designed to output a csv file and json file, it takes a list of updated column names and metadata to streamline the process.

I've documented it's use on the package data, in the example (?vpr_export) as well as a vignette "Sharing VPR Data"

[EOGrady21]

Updated task list:

• Confirm metadata and data names with @kevinsorochan
• translate existing datasets (IML2018051, COR2019002, CAR2022299)
• Push historical data to OpenData (Brian Bower)
• Link OpenData record to CIOOS