Procedures for GEUS Dataverse AWS data releases
We release up-to-date PROMICE/GC-Net automated weather station data on our GEUS Dataverse at the beginning of each month. This repository can be found here.
We point users to the data here, so that they can use a version-controlled dataset with a cite-able DOI for publications.
Automatic uploading to the GEUS Dataverse
Automatic uploading occurs at the beginning of each month. This procedure is defined here. We also perfom uploads in between these monthly releases if there are big updates to the processing pipeline or new data ingestions.
The automated procedue creates a draft release of the updated Dataverse repository that needs to be manually verified and published. We could publish automatically, but feel that manual intervention is needed currently.
Checking a draft release
The draft Dataverse release should be checked, looking at these specific things:
-
Does the last data entry in a given active station file correspond to the end of the preceeding month (i.e. does the dataset cover up to the time of the Dataverse draft?)
-
Make sure there are no duplicate files in the dataset.
-
In the changelog file, does the latest version match the Dataverse release version? Also, does anything need to be added to the changelog (e.g. big pypromice updates, new stations)
-
Is the authorship list up-to-date?
-
Is the pypromice version in the metadata up-to-date?
Publish and advertise
You can publish the draft release when you have checked it and are happy. Remember to advertise the new release where appropriate.