Skip to content

Split out 'Locations' and 'SequenceReference' into their own tables #204

@jennifer-bowser

Description

@jennifer-bowser

As part of our storage refactor, we have decided to split out Locations and SequenceReferences into their own tables. See the LucidChart and GitHub Discussion. for reference.

This will require the following:

  • Modify functionality when registering variants to store the location and sequencereference in the new tables

  • Make the 'vrs_objects' table into an 'Allele' table as part of this. (Copy number variants will be supported in future tickets)

Note that the SequenceReference names should be the refseq aliases from Seqrepo

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions