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
It is sometimes the case that individuals that appear in the janno of a package do not appear in the ENA table for the package (if, say, some of the data was not properly uploaded to the ENA), or vice versa (e.g. when individuals were excluded from analyses and supplementary tables of a paper, but the sequencing data was still uploaded to the ENA).
This will pose a challenge for automatic processing of packages in the future.
The text was updated successfully, but these errors were encountered:
Yes, we explicitly allowed that for now, knowing the imperfections of the ENA data basis. I agree we need to eventually be stricter on this. So let's leave this issue as a reminder.
Poseidon to ENA has a many-to-many relationship. Sometimes there are multiple ENA entries to a single Poseidon ID (genotype, mt data etc...) , another scenario is some samples don't available in ENA.
It is sometimes the case that individuals that appear in the janno of a package do not appear in the ENA table for the package (if, say, some of the data was not properly uploaded to the ENA), or vice versa (e.g. when individuals were excluded from analyses and supplementary tables of a paper, but the sequencing data was still uploaded to the ENA).
This will pose a challenge for automatic processing of packages in the future.
The text was updated successfully, but these errors were encountered: