Add hepatitis-virus coding catalogues: GDC HBV/HCV and a separate HDV reference

Abierto
#96 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
10/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo

Línea de trabajo

This is design work spanning several dependencies: it needs #65 for exceptional translation, #67 for mature polyprotein products, and parent issues #91 and #92. Start by reading those issues and the existing reference-ORF import code, and by pinning the GDC HBV/HCV accessions (NC_003977.1, NC_004102.1, NC_009823.1) and a chosen HDV accession. Done means the acceptance list in the issue is met: offline data, a coverage report, per-virus fixtures, and a test that selects the non-GDC HDV reference without altering the GDC snapshot.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Family import under https://github.com/openvax/orfdata/issues/91, reusing https://github.com/openvax/orfdata/issues/92.

Cover the GDC HBV and both HCV entries, and add HDV as a separately selected reference because it is absent from the GDC v1 viral inventory. HBV/HCV cancer relevance is described by NCI; HDV was classified Group 1 in IARC's June 2025 evaluation.

Historical GDC sources: HBV NC_003977.1, HCV NC_004102.1 and NC_009823.1. Choose and pin an authoritative HDV source accession/version explicitly during import. Keep current genotype/strain expansions separate from these compatibility references.

Acceptance:

  • Import source coding definitions with exact sequence identity, source RNA orientation/topology, ordered coding blocks, phase, genetic code, completeness and versioned protein products. Keep overlapping definitions distinct.
  • Preserve source-specified RNA/translation exceptions and report unsupported cases rather than changing reference sequence to force translation. Use existing #65 for exceptional translation; do not require its completion for ordinary CDSs.
  • Where a source defines a polyprotein, retain its precursor ORF. Model curated mature products through #67 and their processing evidence; do not turn cleavage products into independently translated ORFs.
  • Preserve source-native placements and validate circular-reference placement where applicable. Do not treat the genomic strand as proof of the coding RNA's orientation.
  • Release offline data with a coverage report and real-source translation/placement fixtures for each virus. Separately document unsupported products and missing reference annotations.
  • Explicitly test selection of the non-GDC HDV reference; no silent addition to or rewriting of the historical GDC snapshot.

Scope is coding-reference annotation, not infection reconstruction or generation of new viral sequences.

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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openvax/orfdata

Todos los issues de openvax/orfdata

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.