The element can accept two URLs to files with reads. These URLs come from file list reads, where files to read are set separately. One can make a mistake and pass URLs to the readers in the incorrect order. Usually paired reads are in files with very close names. Maybe we should add a check that URLs are similar enough? In this case we can show a warning and continue reads processing.

Note that the output slot of the element should have type "Taxonomic classification", but the modification of the slot will be done in terms of UGENE-5893.

The element is not user-friendly:

• user should setup slots manually instead of automatically match the right ones
• if 'Input data' is set to 'SE reads or scaffolds', there are still two slots instead of one and the warning appears on the workflow run.
• database setup is unclear - one cannot see the folders content

user should setup slots manually instead of automatically match the right ones

This has been fixed in terms of UGENE-6011.

if 'Input data' is set to 'SE reads or scaffolds', there are still two slots instead of one and the warning appears on the workflow run.

See UGENE-6038.

database setup is unclear - one cannot see the folders content

I mentioned this in UGENE-6039.

Reviewed