You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using ncbi datasets to download data from NCBI we recently realized that the strain name is not added when we download all Oropouche assemblies.
datasets download virus genome taxon 118655
For example AF164550.1 has strain="MD023" but this is not included as a field in ncbi_dataset/data/data_report.jsonl.
To Reproduce
Download all oropouche sequences with metadata using datasets download virus genome taxon 118655
Unzip the file using /usr/bin/unzip ncbi_dataset.zip
Search for strain, search for MD023 in the file -> not found.
Expected behavior
We would expect to find the strain field (if this is renamed this is not a problem) when we download the data. This would be quite useful as some submitters use this a sample identifier. Thanks in advance for any help!
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue. I've passed your request along to Eneida Hatcher and the NCBI Virus team, as they are the group responsible for the underlying data. They're looking into it and any updates they make will flow through to the the Datasets report.
Describe the bug
We are using ncbi datasets to download data from NCBI we recently realized that the strain name is not added when we download all Oropouche assemblies.
datasets download virus genome taxon 118655
For example AF164550.1 has
strain="MD023"
but this is not included as a field inncbi_dataset/data/data_report.jsonl
.To Reproduce
datasets download virus genome taxon 118655
/usr/bin/unzip ncbi_dataset.zip
strain
, search forMD023
in the file -> not found.Expected behavior
We would expect to find the strain field (if this is renamed this is not a problem) when we download the data. This would be quite useful as some submitters use this a sample identifier. Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: