Curate host associations and virus-type hierarchy across the viral reference 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
- 12/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- bioinformatics
- Área
- bioinformatics
Línea de trabajo
Start from the released HPV16 seed and the existing ViralProteome.host_taxon_ids and host_source fields, then trace how host -> group -> type -> reference selection currently works in the code and its tests. The issue asks for curated host and taxonomy metadata across 200 GDC viral contigs, with per-association evidence, multi-host support, and tests that keep exact-sequence matching guarding ORF placement. Done means the HPV16 regression fixture passes, the new selection tests cover the listed cases, and offline metadata and source receipts are published.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The released HPV16 seed now has a source-backed human association, a virus group/type label, and offline reference bases. Extend that host -> group -> type -> exact reference selection to the rest of the GDC viral inventory and separately qualified strains, as part of #91 and family issues #93–98. This is reference curation, not a claim that every sequence in a human sample represents an infection or cancer target.
Data contract
- Keep host NCBI taxon IDs separate from the virus's taxon ID and ICTV species. HPV16 is a virus type in ICTV species Alphapapillomavirus 9;
HPVis a convenience group label, not a formal rank. Support many-to-many host associations, with source and date or accession per association. Distinguish documented/curated host, isolation host and unknown host range. Do not infer humans from a name, related type, or GDC inclusion. - NCBI Virus states that its host field records the specific host from which a sequence was isolated, not necessarily a virus's whole known host range: https://www.ncbi.nlm.nih.gov/labs/virus/vssi/docs/help/ . Use ICTV, PaVE, source records and primary literature as appropriate to qualify each host link; retain disagreements and missing evidence.
- Keep exact full-reference sequence identity, accession/version, strain or lineage, source/annotation status and ORF coverage distinct from the group/type labels. A host/type query should return all qualified reference variants without silently selecting one. A negative query is not proof of infection absence or inability to infect that host.
- Reuse
ViralProteome.host_taxon_ids/host_sourceconcepts while permitting each host association to carry its own evidence when viruses have multiple hosts. Do not transfer coding coordinates or proteins between strains based only on type or host membership.
Acceptance
- Curate host and taxonomy metadata for each of the 200 historical GDC viral contigs under #91, with explicit unavailable/uncertain rows. Preserve the historical GDC sequence pins. Expanded modern lineages are separate references.
- Test selection by a supported host and virus type, a source-backed multiple-host case, an unqualified host, variants within one type, and separation of host and virus taxon IDs. The tests must show that exact-sequence matching still guards ORF placement.
- Publish offline metadata, source receipts and a small example of host -> group -> type -> reference navigation. The initial HPV16 seed is the regression fixture, not evidence that all 189 GDC HPV entries have been annotated.
- 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