Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provenance capture of all information in input yaml file #1889

Open
jjkoehorst opened this issue Aug 17, 2023 · 0 comments
Open

Provenance capture of all information in input yaml file #1889

jjkoehorst opened this issue Aug 17, 2023 · 0 comments
Assignees

Comments

@jjkoehorst
Copy link
Contributor

Expected Behavior

Not sure what to expect but what I would like to see if there are additional variables in the yaml file that they are also captured in the provenance RDF output. Why? This way we can add additional metadata about the job execution, perhaps a project identifier, description of other properties you would like to have at hand when digging through all the provenance information.

A current "workaround" is to add a basic field to the workflow that can potentially capture a lot. This way it is present in the provenance but it is not a best practice I think to capture it this way.

Actual Behavior

As expected I guess, the arguments that are not used by the workflow are ignored

Your Environment

  • cwltool version: 3.1.20230719185429
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants