This repo is getting quite big (~1GB). We should move all data-files out of this repo and put them on the vforwater machine. Then then scripts could look out for that location or check the parameters cell for a connection string to a google S3 bucket. Alternatively we put them on cloud storage and provide public url for all data that is open.
Our own data could also go to Zenodo, den the upload script reads that data, puts the metadata to meta catalog, adds a Zenodo source and dumps a iso xml to Zenodo.
Hey @AlexDo1
This repo is getting quite big (~1GB). We should move all data-files out of this repo and put them on the vforwater machine. Then then scripts could look out for that location or check the parameters cell for a connection string to a google S3 bucket. Alternatively we put them on cloud storage and provide public url for all data that is open. Our own data could also go to Zenodo, den the upload script reads that data, puts the metadata to meta catalog, adds a Zenodo source and dumps a iso xml to Zenodo.