ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend

Evaluation UI: UX Inconsistency

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

A pull request for this has already been merged.

  • #118 by @Ayush8923 — merged
bug
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
10h 40m
Merged PRs (30d)
4

Description

Is your feature request related to a problem?

When uploading a new dataset, users provide a CSV with question and answer columns. These become the golden dataset's question and
ground truth.

Image

However, in evaluation results, we display columns: question, answer, and ground_truth — where answer is now the
generated response while question and ground_truth are from the original upload. This naming inconsistency creates confusion from a UX
perspective.

Image

Describe the solution you'd like

  • Rename the CSV upload columns to question and ground_truth (instead of question and answer)
  • This aligns the upload schema with the evaluation results display
  • Consistent naming: question = input, ground_truth = expected answer, answer = generated response

Alternative

Keep upload columns as-is but rename ground_truth column in evaluation results UI to expected_answer to differentiate it more clearly
from answer (generated response).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the CSV upload flow and the evaluation results UI to find where the column names are defined. Review the linked pull request and confirm which naming choice was implemented; done means the upload schema and results display use clear, consistent names for question, ground truth, and generated answer.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.