Skip to content

variants.csv file rationale #4

@hforoughmand

Description

@hforoughmand

I don't understand the rationale behind the variants.csv file. I would be happy if you could answer my following questions:

  1. For the earlier lineages, all the subvariants of concern are listed and no "*" is used to indicate the variants, while that is not the case for more recent variants.

  2. Why in some more recent commits lineages are removed from the list? Does the list supposed to only contain the current list of VOCs?

  3. How can we contribute in keeping this list up to date? How do you gather all these information? What are the sources?

  4. Can we also include the source of the data in the variants.csv file? Then, everyone can check for the validity of the record.

  5. Can we also include the designation date for each VOC?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions