Link polyprotein and precursor ORFs to their processed protein products

Aperta
#67 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
data

Direzione di ricerca

The issue is a design task, so start by reading the existing ORF contract and the extra_orfs handling that #61 defines, then decide how a processed product attaches to its precursor ORF. Use the pinned POMC record (UniProt P01189) as the first worked example, with the processed peptide intervals and a two-ORF transcript control. Done means a design agreed with maintainers, plus fixtures that show processed products stay distinct from independently translated ORFs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Varcode consumers need to distinguish several proteins translated from different ORFs on one RNA from several mature products processed from one translated precursor. The latter should be represented alongside ORFs, without inventing extra starts/stops or standalone ORFs for each processed peptide. This completes the product side of #61's public ORF contract.

Required behavior

  • Keep the translated precursor attached to its coding model. Add source-defined mature-chain/peptide and processing-feature records with stable namespaced identifiers, precursor accession/version, amino-acid intervals, sequences and evidence.
  • Link each processed product to its precursor ORF placement(s), actual transcript/gene context and codon/genomic mappings where available. Preserve uncertain cleavage boundaries and alternative or nested processing products, including tissue/condition information when supplied.
  • Import existing authoritative precursor/product annotations, starting with qualified UniProt or RefSeq/INSDC records. Preserve cross-references and source evidence; do not treat every in-silico cleavage candidate or detected peptide as a mature functional product.
  • Keep true polycistronic/multiple-ORF RNAs, proteolytic processing, and translational mechanisms that yield separate chains distinguishable. A polyprotein is ordinarily one coding translation with related processed products, while independently initiated ORFs remain individually addressable through extra_orfs.
  • Provide native product/processing access from the ORF contract so Varcode can map a precursor coding change into each affected mature product's coordinates and report overlap with a cleavage signal. Actual loss of processing or altered abundance requires evidence or an explicit prediction; a sequence overlap alone does not establish either.

Acceptance

Use a pinned human precursor example such as POMC, UniProt P01189, plus a curated viral polyprotein example if viral scope is claimed. Verify product IDs/sequences/intervals, alternative processing, cleavage-boundary variants and lossless serialization. Include a true two-ORF transcript control to prove that independently translated products and processed products are not conflated. Genomic mapping must retain splice boundaries and reference versions.

Align terms with INSDC mat_peptide / propeptide features and source protein annotations. ORFdata owns reference products and mappings; Varcode owns mutation consequences. Missing processing support must not prevent ordinary coding-effect annotation of the precursor ORF.

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
10h 11m
PR unite (30g)
51

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openvax/orfdata

Tutte le issue di openvax/orfdata

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.