Actions such as zenodo, dataverse, possibly dataone or d4storagehub are actions that may need to be triggered at the end of the workflow (as last action), in case we want to upload all entity-related content (data, metadata, etc), generated during the geoflow execution. This is not a strict re-ordering, as these actions should also be triggered initially in the list of actions (related to #156 )
Examples:
a Zenodo action is triggered early in the workflow, to inherit a DOI from Zenodo (in order to inject it in other resources such as ISO 19115) but should be triggered also at the end to manage the upload of all files produced (including data, and metadata)
a D4Science action could also be triggered early in the workflow, eg. to upload the main data file (~ data features), inherit a D4Science resource hyperlink (in order to inject it in other resources such as ISO 19115), but should be triggered also at the end to manage upload of all files to D4science (including, data/metadata)
In general these actions can be considered as "generic" resource uploaders.
Actions such as
zenodo,dataverse, possiblydataoneord4storagehubare actions that may need to be triggered at the end of the workflow (as last action), in case we want to upload all entity-related content (data, metadata, etc), generated during the geoflow execution. This is not a strict re-ordering, as these actions should also be triggered initially in the list of actions (related to #156 )Examples:
In general these actions can be considered as "generic" resource uploaders.