-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata in download: aminoAcidInsertions included, serialization to be discussed #1421
Comments
They shouldn't be, that's a bug.
That's also a bug. In a TSV/CSV, I think that unknown values should just be left empty (please not
LAPIS does not yet support timestamps as a type. We could provide it as |
Thanks! How do we distinguish an empty list from I guess having a unix timestamp is ok for now, was just not sure if this was intended. |
what's would the former mean? (if the answer is: "preprocessing pipeline configured not to provide frameshifts" then let's just not have the column at all in those cases) |
Maybe frameshifts is not the best example, what about something else like associated biosamples: there might be a difference between not knowing about them and knowing there are none. |
Thanks to GenSpectrum/LAPIS-SILO#354 and GenSpectrum/LAPIS#715, insertions are no longer included in the metadata file. |
The insertions have been fixed, there's a new issue for the timestamp |
I've just tried the metadata download from the ebola-zaire instance on main. This is an example row. Few points for discussion:
aminoAcidInsertions
(and nuc ones) included at all? We can include them but it's more related to alignments rather than metadata proper. After all we don't include snps, or deletions. Insertions allow the reconstruction of a sequence from alignments, but that's all.aminoAcidInsertions
and (nuc ones)null
? It seems we usenull
fornot provided
, should we use that or rather use something like N/A?null
seems to be simply the default in kotlin.submittedAt
andreleased at
is a unix timestamp, should we rather serialize it as human readable timestamp, something like2023-01-05Z23:11:56
?The text was updated successfully, but these errors were encountered: