Results

Workflow outputs are captured in the STAGEOUT step of the Workflow Runner, extracted by reading the generated catalog.json file. These are then exported to an S3 bucket in a workspace-specific directory depending on the workspace which invoked the workflow (and therefore the namespace in which it is executed). After this step, the outputs are harvested into the invoking user’s workspace sub-catalog within the Resource Catalogue. Any workflow outputs are currently saved to a new sub-catalog within the “processing-results” sub-catalog of the workspace catalog, for example https://dev.eodatahub.org.uk/api/catalogue/stac/catalogs/user-datasets/<user-workspace>/processing-result

The output catalog name will have the following format:

containing the generated collection

and then any items beneath that. Workspace-specific sub-catalogs are private to the workspace owners, so you must make sure to authenticate before attempting to retrieve your results from the Resource Catalogue.

If you wish to view the asset data in any of your generated items, the links to these will have been updated to be links that allow you to access the data directory from S3 via HTTPS, provided you are authenticated and authorized. You can open these links in a browser once you are logged into the Hub or via an authenticated GET request with an API token in the Authorization header as before.