Skip to main content

UX-ML-002 — Expand the EDA pipeline-stage acronym

FieldValue
StatusOpen UX finding; source-verified
SeverityLow
Componentssparqd/oqullus
Associated issuesNot opened pending finding review

Concrete observed case​

The AutoML progress stepper receives the backend stage key eda. Oqullus sends every stage key through one generic title-casing function, which renders this key as Eda. The visible step therefore neither preserves the recognized acronym EDA nor explains that it means Exploratory Data Analysis.

Expected condition​

Render this stage as EDA — Exploratory Data Analysis wherever pipeline progress or results identify it. Use an explicit display-name mapping for known stage keys so acronyms and product terminology are not inferred through generic capitalization. Keep the backend identifier eda unchanged.

Why it matters​

Users who do not already know the ML workflow cannot tell what Eda means or what work the stage performs. The casing also makes an established acronym look like an unexplained product-specific term.

Existing controls and workarounds​

The completed-stage details expose row count, column count, data-quality score, and duplicate-row information, which helps explain the output after completion. There is no explanation in the progress label itself while the stage is pending or running.

Alternatives considered​

  1. Recommended: map eda to EDA — Exploratory Data Analysis in the shared stage-label formatter.
  2. Show EDA with a tooltip containing the expansion. This saves horizontal space but keeps the meaning hidden from keyboard, touch, and scanning users unless the tooltip is implemented accessibly.
  3. Rename the backend stage key. Rejected because this is a presentation issue; changing the API identifier would create unnecessary compatibility work.

Component involvement​

  • Oqullus owns the stage label and its accessible explanation.
  • The AutoML backend can retain eda as its stable machine-readable stage key.

Reproduction and verification​

Follow ML-S013.

Resolution conditions​

Close when every visible occurrence preserves EDA as an acronym and expands it to Exploratory Data Analysis at least once in the immediate workflow context, including while the stage is pending or running.

Validation and blockers​

The rendering path is source-verified. A deployed visual check remains pending after the label is changed.