Validate CSV export → analytics template end-to-end workflow (ICD-11 evaluation)

[jamlung-ri]

Summary

Jonathan is building a plug-and-play spreadsheet analytics template so that CSV exports from OCL Mapper can be copy-pasted in and automatically recompute evaluation metrics. This ticket tracks completing that template and validating the end-to-end CSV → analytics workflow.

Context

• Andy ran a 20-row ICD-11 test session and downloaded the CSV output
• Jonathan is setting up a spreadsheet template where the CSV can be pasted in and metrics auto-recompute (rather than requiring manual formatting each time)
• Goal is to validate that the CSV output format from OCL Mapper is correct and usable for evaluation analytics

Tasks

• Andy sends Jonathan the downloaded CSV from the 20-row ICD-11 test (sent via Slack)
• Jonathan pastes CSV into analytics template and confirms it re-computes correctly
• Share results with the team
• Flag any CSV format issues back to the dev team (ref: Update the Mapper CSV Download to support evaluation #2308)

Notes

• This is primarily about validating the method and format, not the mapping content itself
• Raised during 2026-02-26 team call

[ocl-automation]

Automated Triage — 2026-04-06

Dimension	Score
Complexity	3
Scope	2
Clarity	4
Dependency	3
Risk	2

Decision: decision/human-review
Type: type/feature
Signals: signal/low-risk, signal/small-scope, signal/well-specified, signal/has-dependencies

This involves building and validating a new analytics template workflow with moderate complexity across a few components. The issue is well-defined with clear context and acceptance criteria, has some coordination dependency between team members, and carries low-moderate risk since it's primarily a new capability rather than modifying existing critical functionality.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).