This PR adds a metadata.Rmd document to the top level. This could be run after workflow.Rmd to generate metadata. Specifically, this generates the EML metadata that is required for EFI forecasts (well, most of it; I've tried to keep the code clean simple and so I cut some corners)
It also includes commands to publish the forecast to the permanent data archive at KNB / DataONE -- these commands require the user has a token from KNB, and tokens expire daily... DataONE does have test servers that use test-tokens, so I tested with those and things seem to work. This would complement or provide an alternative to the 'publish' commands shown in workflow.md, which just posts the data to server bucket with a permanent content-based identifier. The publication to DataONE uses the same content-based identifiers shown in workflow.md
Hi @annaspiers and team,
This PR adds a
metadata.Rmddocument to the top level. This could be run afterworkflow.Rmdto generate metadata. Specifically, this generates the EML metadata that is required for EFI forecasts (well, most of it; I've tried to keep the code clean simple and so I cut some corners)It also includes commands to publish the forecast to the permanent data archive at KNB / DataONE -- these commands require the user has a token from KNB, and tokens expire daily... DataONE does have test servers that use test-tokens, so I tested with those and things seem to work. This would complement or provide an alternative to the 'publish' commands shown in workflow.md, which just posts the data to server bucket with a permanent content-based identifier. The publication to DataONE uses the same content-based identifiers shown in workflow.md
cc @amoeba