Allow for custom attributes and read type description of fastq #102
+205
−3
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.
Implements #86
Allows to add "schema_attribute[tag]" (e.g. sample_attribute[treatment]) in the input schema tables (tsv only) where the schema ('sample', 'run', 'experiment', 'study') e.g. a new
sample_attribute[treatment]
column in theena_sample.tsv
. These extra headers are injected in the XML generation stream, and injected in the generated XML as aATTRIBUTE
sequence (templates where modified accordingly). For samples, only the default ERC000011 was modified to support these additional attributes. Unit is not yet supported.Additionally, support for
read_type
andread_label
(as new headers in the ena_run.tsv) is added to the run XML for files of typefastq
to support single cell situations where more than 2 fastq files are available (ENA then requires to have read_type described). Multiple values can be passed using CSV format egpaired,cell_barcode
Limitations:
read_label
is not fully supported as it would require to supportSpotDescriptorType
in the run XML but it is unclear how this information could be passed. Basic support forSPOT_DECODE_SPEC
with aREAD_SPEC
usingBASE_COORD
(see SRA.common.xsd) could be provided with:READ_SPEC 1
...READ_SPEC n
where the header number is theREAD_SPEC's READ_INDEX
READ_LABEL:READ_CLASS:READ_TYPE:BASE_COORD:SPOT_LENGTH
. For example:UMI1:Application Read:Other:1:8
.