Roadmap: publish sequence-qualified viral coding references for cancer RNA and the GDC panel
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
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- data
Línea de trabajo
This is a tracking roadmap, so start from a child issue rather than this one. The HPV16 seed (#92, shipped in ORFdata 0.29.0) shows the pattern: native SourceRNA and TranscriptORF objects, source-validated RefSeq CDSs, and the offline consumer example. Any new coverage must keep the pinned inventory SHA256 unchanged and match sequence content before transferring annotation.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
ORFdata should distribute versioned viral coding references that Isovar can apply to reconstructed sample RNA. This is reference annotation work, building on the existing native RNA/ORF models rather than introducing a viral ORF class hierarchy.
Deliverables
- Publish a small offline HPV16 CDS catalogue using existing SourceRNA and TranscriptORF APIs
- Expand the viral CDS catalogue across GDC HPV types and qualified HPV lineages
- Import source-qualified EBV and KSHV coding references with supported RNA splice paths
- Import CMV coding references with explicit strain and annotation coverage
- Add hepatitis-virus coding catalogues: GDC HBV/HCV and a separate HDV reference
- Add HTLV-1 and GDC HIV coding references with source-defined translation paths
- Add Merkel cell polyomavirus and SV40 coding references with distinct cancer evidence
The first release should be the independently qualified HPV16 seed; the broader panel should not delay that small useful release.
Coverage and reference identity
Account for every one of the 200 viral contigs in GDC GRCh38.d1.vd1's published inventory: 189 HPV entries plus CMV, EBV, HBV, two HCV entries, HIV-1/2, KSHV, HTLV-1, Merkel cell polyomavirus and SV40. Report per-reference source accessions/versions, sequence identity, coding-model counts, available versus incomplete annotation, unresolved features and validation status. A contig being listed must not imply that its coding catalogue is complete.
Keep this historical GDC compatibility snapshot separate from explicitly selected, current strain/lineage expansions. Match actual sequence content, including circular rotation and strand when relevant, before transferring annotation. Never update historical checksums or apply new coordinates by virus name alone. The pinned inventory SHA256 used by Isovar is f221e758f47e4784714b4a89198b89536ddacdc905da9c778a6802d3e1e51c56.
Broader cancer coverage must include HDV, which is absent from that inventory. Maintain source-dated cancer-evidence and inclusion-reason metadata independently from sequence availability. IARC's June 2025 assessment classifies HDV and MCPyV as Group 1 and HCMV as Group 2B. NCI's infectious-agent overview supports prioritizing HPV, EBV, KSHV, HBV/HCV and HTLV-1. Do not label all GDC viruses as established human cancer causes or treat HIV-associated immunosuppression as proof that a tumor expresses an HIV target. Consider additional candidate viruses through evidence review, not an unsupported exhaustive-causality claim.
Shared contract and scope
- Reuse
SourceRNA,TranscriptORF.at, catalogue manifests/cache and existing provenance. Keep source RNA/CDS fragments distinct from fully defined transcripts; preserve ordered coding blocks, strand, phase, translation table and start/stop completeness. - Provide deterministic, explicitly installed, offline data selection by exact viral reference. Coordinate with #70/#71 without forcing viral inputs through a human/PyEnsembl-only entry point.
- Reference coding annotation is distinct from reference protein FASTA layers already supported by
ViralProteome. RNA support is distinct from direct translation or protein evidence. - Preserve unsupported recoding/processing explicitly and link #65/#67; ordinary source-validated CDS imports should ship independently.
- Isovar owns observed RNA reconstruction, read support and sample-specific protein predictions. It must preserve variation and incomplete coding sequence rather than fill missing bases from reference. Downstream integration: openvax/isovar#465.
Acceptance: versioned reference releases, an offline consumer example using native ORFdata objects, qualified real-source fixtures, and a coverage manifest that exposes gaps. Keep the verified HPV16 smoke test available throughout expansion.
Seed release: ORFdata 0.29.0 is published, via #99 (closes #92). It provides nine source-validated RefSeq NC_001526.4 CDSs, qualified against both native and GDC HPV16 DNA. The downstream coding consumer is Isovar PR #516. Remaining family issues retain explicit coverage and unsupported-feature requirements.
- 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