Link polyprotein and precursor ORFs to their processed protein products
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- data
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 1
- Forks
- 1
- Merge medio
- 10 h 11 min
- PR fusionados (30 d)
- 51
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de openvax/orfdata
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
openvax/orfdata#194 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Los mantenedores suelen responder en 1 día
Todos los issues de openvax/orfdata
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pearu/agent-sandbox#451 ·
Los mantenedores suelen responder en 1 día
-
run_gate loads a custom tasks file from outside the working directoryPosiblemente ocupada @Ru0k3 la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
MakazhanAlpamys/Soup#3189 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
review developer setup docAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
NYCPlanning/data-engineering#2996 ·
Los mantenedores suelen responder en 1 día