Skip to content

Automatically name artifacts with originating process information instead of dflt_name #2190

Closed
@adswafford

Description

@adswafford

Can we name artifacts more meaningfully, especially on the processing pipeline?

Example, when debluring data, the two files generated are both named dflt_name, so there is no feedback to the user as to which is the reference hit and which is all sequences unless they click on the artifact and read the available .biom files available.

Instead we could name them more informatively: "16S_ref_deblur" and "all_seqs_deblur"

For closed ref "16S_closed_ref", rarefied data "rarefied_[#features]". The [#features, could be divided and appended with 'K'"

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions