ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Dashboard: FAQs and query insights
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 18
- Forks
- 10
- Merge medio
- 2 d 20 h
- PR fusionados (30 d)
- 14
Descripción
Context
Once an NGO finalizes their program and releases it to end users in production, they currently have no way to see how it is performing in the field. Within the first 2–4 weeks of a release, program teams should have visibility into how the program is going: what kinds of questions end users are asking, which topics come up most often, and whether the assistant is handling them well.
Today that feedback loop doesn't exist — teams cannot tell whether the assistant's knowledge base covers real user needs, which questions are going unanswered or answered poorly, or how to refine the prompt and content based on actual usage.
What NGOs need
A simple view of their top frequently asked questions over a chosen time window, with query volumes, so they can:
- Spot recurring themes in end-user queries
- Verify the knowledge base has good answers for those questions
- Use this data to improve the assistant (prompt + content) with each iteration
What can be done from our end
Kaapi already persists every user question and response with assistant and timestamp, so the raw data for time-windowed FAQ mining exists today without new capture infrastructure. On top of it:
- Clustering of semantically similar queries (via embeddings or similar techniques) to surface top FAQs with counts
- Aggregation by time period
- Periodic summaries (e.g. a daily rollup)
Since most NGOs operate at modest query volumes, lightweight clustering approaches are viable, keeping the solution simple while giving program teams actionable insight from real production usage.
Status
PRD being drafted; picking up in this iteration.
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.
Línea de trabajo
Comienza con el PRD que se está redactando e inspecciona dónde persiste Kaapi cada pregunta y respuesta del usuario, incluidos los campos del asistente y de la marca de tiempo. Define la vista de FAQ basada en ventanas temporales, la agrupación semántica de consultas, los recuentos, la agregación y los resúmenes periódicos; se considera terminado cuando el diseño y la implementación cumplen los requisitos acordados del PRD.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- analytics, data, machine-learning
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100