-
Capture workflow run crate provenance from Snakemake workflows similar to existing CWL. Note that WfExS already is doing something similar (but to figure out workflow structure)
-
-
The use case is:
As a workflow developer, I want to record what git repository and release tag/version of a tool was used within the workflow, as well as its dependencies, so that I can reproduce a s…
-
Using `docker_extract.py` from both [0.7](https://github.com/common-workflow-language/cwl-utils/releases/tag/0.7) and [0.8](https://github.com/common-workflow-language/cwl-utils/releases/tag/0.8) rele…
-
# Description
I am running WfExS with the config files shown below. When I run `WfExS-backend.py -L local-config.yml stage -W test-stage.yml` I get the following error: `NotADirectoryError: [Errno 20…
-
There is no way currently to get the output file path from the incoming crate. It is needed for the Wfexs stage file to be generated.
-
WfExS will upload RO-Crates to WorkflowHub. So, WfExS should support uploading those RO-Crates to WorkflowHub, using their RO-Crate Submission API.
See RO-Crate Submission API documentation: [https…
-
# Background
My team would like to use WfExS in Trusted Research Environment (TRE) which has data sources which can't be exposed to the outside world. We anticipate that the environment will contain …
-
# Description
When staging a workflow for the first time as non-sudo/root user I'm getting the error in the title. Oddly, deleting the cache dir and re-running the `stage` command seems to fix the is…
-
https://swissdatasciencecenter.github.io/renku-ontology/
and also
https://www.w3.org/TR/prov-o/