Link polyprotein and precursor ORFs to their processed protein products

未关闭
#67 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 分钟
30 天内合并 PR
51

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openvax/orfdata 的其他 Issue

查看 openvax/orfdata 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。