Thanks for reminding me, @LenaLapidot. This is something I've been meaning to do this release.
I just made the changes to allow this, but my gut feeling is it will not make it into the 2019.7 release (out at the end of this month). Keep an eye on the changelog that comes out with that release, and/or this pull request to keep track of this feature.
In the meantime, here is a convoluted workaround (no guarantees it will work "as is"!):
- export your taxonomy classifications
- concatenate your feature IDs and taxonomy IDs and add this as an additional column to your taxonomy.tsv file, maybe something like this would work (or maybe not!):
tr '\t' ': ' < taxonomy.tsv | paste taxonomy.tsv - > new-taxonomy.tsv - re-annotate your feature IDs. Use `feature-table group --i-table table.qza --p-axis feature --m-metadata-column 'feature-id: Taxon' --m-metadata-file new-taxonomy.tsv --o-grouped-table table-with-new-feature-ids.qza
- use that new table to make your heatmap
Again, no guarantees this will work as-is! The goal is to get a taxonomy text file that looks like this:
| feature-id | Taxon | feature-id: Taxon |
|---|---|---|
| feature1 | Bacteria | feature1: Bacteria |
| feature2 | Bacteria;Listeria | feature2: Bacteria;Listeria |
| et cetera |
Then whatever is in the third column (which can be named whatever you like!) will be used to relabel your taxon IDs. As long as it is a unique value for each feature, you will keep the unique ASVs and just give them new names. So you can also try making this by hand (e.g., in excel) rather than following the nasty hack I've ad libbed above.
That would work but is probably not what you want, since you would potentially be collapsing individual ASVs that are important features in their own right (if your ASVs all have unique taxonomies, you could just follow my convoluted workaround starting at step 3 and using your taxonomy.qza file, no need to attempt the rusty hack of steps 1-2).