Link polyprotein and precursor ORFs to their processed protein products

オープン
#67 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
領域
data

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Python
スター
1
フォーク
1
平均マージ
10時間 11分
マージ済み PR(30日)
51

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

openvax/orfdata のほかの issue

openvax/orfdata の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。