map formats and artifact classes to EDAM (types and data, respectively?) #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If possible input parameters and collections should always set the
format
attribute. I exemplify this here for somefastq.gz
inputs. Probably the implementation should not be done here in this repo?For fastq.gz Galaxy has a few datatypes, fastq.gz, fastqillumina.gz, and
fastqsanger.gz
(and colorspace fastqsanger).fastq.gz
would allow all of them.Let me know if you need help with mapping other qiime2 datatypes to Galaxy data types.