Open EOGrady21 opened 9 months ago
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"
Updated task list:
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- [ ] updatevpr_save()
to output standardized csv files- [ ] push historical data to OpenData & CIOOS