search

eco4cast / EFIstandards

Exploring possible metadata and data formatting standards for comparing Ecological Forecasts
BSD 2-Clause "Simplified" License
14 stars 8 forks source link

Fix/logistic metadata and pkgdown site #21

Closed ashander closed 3 years ago

ashander commented 3 years ago

I don't know how to properly write to inst/extdata during vignette build and these files weren't being updated by building vignettes. (Still aren't after the changes I made.) So, added some commented text about how to rebuild the files in inst/extdata.

ashander commented 3 years ago

I added an optional (non eval'd) chunk that writes the files to inst @mdietze if you like this then I think the netcdf example should probably be updated to do this too.

Also on netcdf topic, in terms of having a metadata file to go along with that .nc file -- can we just add another entry in the physical of the same eml file? or do we need an entire duplicated eml w/ different physical? I could make those changes on this branch too if one of those options makes sense.

mdietze commented 3 years ago

EML: that would be a duplicated eml file with different physical. Sorry for pulling this before catching the bit about updating the netcdf example (that's the one that's most important to not automatically update because it's binary)

mbjones commented 3 years ago

@ashander @mdietze On the EML physical section, it is technically repeatable, specifically to handle the case when the same entity (say a dataTable) is physically serialized in both a csv and netcdf format. The online/url and serialization format would differ, but the represent the same data entity, so they would be distinct physical sections within the entity. That said, I don't know of any operational systems that use this flexibility of the EML model. You can see the schema definition and the physical is repeatable here: https://eml.ecoinformatics.org/schema/eml-datatable_xsd#DataTableType