Document how NameRes relates to Babel and NodeNorm, and whether it reports a version
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 66/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- python
Línea de trabajo
Start with the NameRes README sections on Node Normalization and conflation, then trace how the index is built and how lookup requests are handled to establish the relationship and whether conflation can vary per query. Check the service routes for a status or version endpoint. Document the verified answers, including whether NameRes exposes a version; answering how its data relates to Babel and NodeNorm is enough to complete the issue.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Companion to NCATSTranslator/Babel#1077 and NCATSTranslator/NodeNormalization#412, which ask the same of those two repositories.
babel-explorer is a debugging tool for Babel cliques. It does not use NameRes today, but two open PRs add NameRes-backed frontends — a lookup tool (#23) and an autocomplete playground (#24) — so it is about to. Writing the agent documentation for that repository turned up questions about NameRes that the README does not answer.
This is a smaller ask than the other two: mostly about provenance, so a consumer can tell which Babel release a given answer reflects.
What we could not find
1. How NameRes relates to Babel and NodeNorm. The README says results are normalized through Node Normalization and "conflated using both GeneProtein and DrugChemical conflation", linking to Babel's conflation documentation — but not whether the NameRes index is built from Babel output, built from NodeNorm, or built independently and normalized afterwards. That difference determines whether a NameRes answer can be stale relative to a NodeNorm answer, which is exactly what a tool showing both side by side needs to know.
2. Whether there is a version or status endpoint. NodeNorm exposes babel_version via /status, and babel-explorer uses it to refuse to mix a NodeNorm built from one Babel release with Parquet files from another. If NameRes has an equivalent, it is not documented; if it does not have one, that is worth knowing too, because a UI showing NameRes and NodeNorm results together has no way to warn that they disagree about the world.
3. Whether conflation is fixed or per-query. The README states results are conflated both ways. Is that a property of the index, or a request parameter a caller can vary? A lookup tool would want to expose the choice if there is one.
Documents in babel-explorer worth reading
AGENTS.md→ "Domain context" (in PR #31) — how we currently describe the three services to a coding agent, with what we could not verify marked as such. NameRes gets one line there, precisely because we could not establish the relationship in point 1.core/nodenorm.pyandcli.py→check_babel_versions()— the version-skew check we would want an equivalent of for NameRes, if the concept applies.
Answering point 1 alone would be enough to make the other two easy to reason about.
- Lenguaje dominante
- Python
- Estrellas
- 5
- Forks
- 4
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
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 NCATSTranslator/NameResolution
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 43/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de NCATSTranslator/NameResolution
Issues similares
-
cognition facet:consolidation memory ready size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
proposal
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
j3ko/agent-plugins#29 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
-
area:cli area:security bug priority:medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
rtk-ai/rtk#5127 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
Gathin23/cleanyourtv#4026 ·
Los mantenedores suelen responder en 1 día