Open adamovanja opened 2 years ago
hi @valentynbez,
the error that should appear in your case is not the same one as the one described above: above no error is falsely raised because multiple BioProjectIDs are queried with the get-metadata
action and only one of them contains matching runIDs. In your case, you are querying just one BioProjectID with another methods (get-ids-from-query
).
Could you open a separate issue for your case?
Hi,
I inspected the error further and yes, it is a separate issue. Sorry.
As a plugin user, I want
get-metadata
to return a warning or a Q2 error in case one aggregate ID (e.g. BioProject ID, Study ID) of many has no linked run ID entires in the SRA database.Steps to reproduce:
get-metadata
with an input artifact containing the following accession IDs within:PRJNA290381
&PRJNA18197
.Current behaviour:
get-metadata
exits with an empty SRAFailedIDs artifact and the outputSRAMetadata
only containing metadata of the second accession IDPRJNA18197
and no information on the first accession ID (PRJNA290381
) for which no run IDs are linked in the SRA:Expected behaviour: A warning or an error should be raised in case the run IDs of one aggregate ID could not be fetched (by
q2_fondue.entrezpy_clients._pipelines._get_run_ids
).