Species metadata to report (e.g. for ERGA assembly reports)#306
Species metadata to report (e.g. for ERGA assembly reports)#306CormacKinsella wants to merge 5 commits intomainfrom
Conversation
There was a problem hiding this comment.
@mahesh-panchal - this section adds to the content of the params.yml.
Could you confirm that it's ok to remove Channel.value, since I'm replacing it with a channel object.
For the BUSCO lineages I've used a different method, but if you prefer we could also emit the settings metadata as part of the sample_meta subMap into ASSEMBLY_REPORT, and then use a similar method here.
There was a problem hiding this comment.
Yes, it's fine to remove the Channel.value, although it might not be needed if reading all the data from the files.
|
|
||
| ```{python} | ||
| #| output: asis | ||
| if tax_id: |
There was a problem hiding this comment.
Could we perhaps then load the data from TOL_SEARCH, ENA_TAXQUERY, and GOAT into a set of tables, or a single table. That should also take care of the busco lineages. I think only the ENA_TAXQUERY stuff needs to be written to a file, like TOL_SEARCH is.
There was a problem hiding this comment.
Yes, it's fine to remove the Channel.value, although it might not be needed if reading all the data from the files.
CormacKinsella
changed the title
CormacKinsella
changed the title
2 participants
Draft section for easy transfer of EAR metadata from the report.