Overview
TargetAccession and TargetSequence have diverged significantly in their metadata representations. Accession-based targets carry user-supplied free-text fields (assembly, gene) with no validation against the actual accession, and have no structured organism/taxonomy representation despite the organism being fully deterministic from the accession. Sequence-based targets carry a full Taxonomy FK, but it is stored on the wrong model — taxonomy is a property of the gene target, not of the sequence representation.
This parent tracks two child issues that together resolve the drift:
These issues are sequenced: #697 depends on #696 because the mapping job changes in #696 establish the derivation pattern that #697 extends to taxonomy. We also have created #698 to track API response normalization that must be coordinated with clients at a later time.
Overview
TargetAccessionandTargetSequencehave diverged significantly in their metadata representations. Accession-based targets carry user-supplied free-text fields (assembly,gene) with no validation against the actual accession, and have no structured organism/taxonomy representation despite the organism being fully deterministic from the accession. Sequence-based targets carry a fullTaxonomyFK, but it is stored on the wrong model — taxonomy is a property of the gene target, not of the sequence representation.This parent tracks two child issues that together resolve the drift:
assemblyandgenefromTargetAccession; derive from accession during mapping #696taxonomy_idtoTargetGene; populate via mapping for accession-based targets #697These issues are sequenced: #697 depends on #696 because the mapping job changes in #696 establish the derivation pattern that #697 extends to taxonomy. We also have created #698 to track API response normalization that must be coordinated with clients at a later time.