Closed njmattes closed 8 years ago
yes, i'll put the JSON blob into global_meta
(and add a filetype column) and get rid of netcdf_meta
. i will have to reingest the netcdfs and for that reason won't ingest many, say only a dozen or so, just for testing purposes. the bigger ingest i have done was to see whether my ingestion script can handle all these netcdfs (though they really seem to be of the same kind, or better: of one of two kinds).
Yep, makes perfect sense.
i want to commit my changes for this issue soon but would be glad to resolve #17 first, so i know in the future how to best edit + test code on our server without getting in the way of your editing / testing, thanx
done, see latest commits to develop
branch. also tested ingestion again with new schema, it works.
@legendOfZelda In the current db, there's a
netcdf_meta
table that stores a JSON representation of the metadata from the original NetCDF file. I thought we were including these JSON blobs in theglobal_meta
table, along with afiletype
column, since a variety of filetypes will have metadata that needs storing.I bring it up mostly because it affects the code in the API. In some ways it doesn't really mater to me how we store the info (though my gut says to use the latter method).