tasks/workstreams/graph-library/archive/investigate-auto-generated-chart-titles-from-axis-semantics.md


type: task id: GRAPH_LIBRARY-INVESTIGATE_AUTO_GENERATED_CHART_TITLES_FROM_AXIS_SEMANTICS title: Investigate auto-generated chart titles from axis semantics description: Explore whether standard charts should support an optional fallback title generated from axis semantics, such as Revenue vs. Age, when no explicit chart title is authored. milestone: m1-ft-analytics-analyst-pilot owner: data-viz-designer-engineer status: not_started priority: p2


Investigate auto-generated chart titles from axis semantics

Superseded (2026-03-27). This narrowly scoped follow-on was consolidated into Consolidate semantic chart defaults and rendering control-surface follow-ons so the active backlog carries one M2 umbrella task instead of many M1 leaf items. Keep the notes below as reference detail, not as a separately scheduled task.

Problem

Explore whether standard charts should support an optional fallback title generated from axis semantics, such as Revenue vs. Age, when no explicit chart title is authored.

Context

During M1 structure critique, the question came up whether Dataface should be able to generate a chart title from axis semantics when no explicit title is authored. A simple example is:

Current system behavior appears to be:

Relevant evidence:

Constraint:

Possible Solutions

  1. Recommended: Add an optional fallback title policy for standard charts when title is empty. Example rule: - if both x and y semantics exist and the chart family is axis-based, synthesize Y vs. X - prefer x_label / y_label over raw field names - fall back to humanized field names only when labels are absent This keeps authored titles primary while giving untitled charts a more meaningful default.

  2. Add a chart-level explicit setting such as settings.title_fallback: axis_semantics. This would be more explicit and avoid surprising authors, but it introduces another authored control surface.

  3. Keep titles fully manual and do nothing. This is the simplest implementation story, but it misses a chance to provide more useful default behavior in exploratory or minimally authored charts.

  4. Generate titles only in the playground or editor surfaces, not in final rendering. This could help authors see a suggested title without baking it into the rendering contract, but it splits behavior between authoring and runtime.

Plan

  1. Confirm the current title ownership model in standard charts, layered charts, KPI, and geo charts.
  2. Decide whether Y vs. X should be: - a renderer fallback - an authored opt-in - or only a suggestion surfaced in tooling
  3. If fallback behavior is chosen, define the exact precedence: - authored title - semantic labels (x_label, y_label) - humanized field names
  4. Identify chart-family exclusions: - pie/donut - KPI - tables - other forms where Y vs. X is semantically wrong or awkward
  5. Update the chart property catalog and related docs if a new fallback or authored control is added.

Implementation Progress

QA Exploration

<!-- For UI/browser tasks: use Playwright MCP to explore the running app. Record bugs found, fixes applied, and suggestions for future work. Skip for non-UI tasks (mark N/A). -->

Notes:

Review Feedback

<!-- Reviewer comments, what was changed in response, and sign-off. -->