From 0ba858d638b8cfaf0a0f099452795fef94dc9914 Mon Sep 17 00:00:00 2001 From: larssand Date: Sun, 1 Nov 2026 21:44:42 +0100 Subject: [PATCH] docs(roadmap): plan race day CSV export and results publishing to external sites --- ROADMAP.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/ROADMAP.md b/ROADMAP.md index 6e3211c..303f4be 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -976,6 +976,14 @@ The decoder kept showing offline on the club PC although AMMC on 9443 was reacha Verified: unit tests in `tests/local_cache.test.js`; `tests/browser_decoder_url.js` makes the state key throw `QuotaExceededError` and checks that Connect still reaches a fake decoder, the URL is saved to the server and the local copy is dropped. It fails without the fix ("Timed out: connects although the browser storage is full"). 269 unit and 81 browser scenarios pass. +## Race day export and result publishing (planned 2026-11-01) + +Asked for after the first ÖRC Winter round, where a qualifying went wrong and the club had to rebuild the day's result by hand. Today the only exports are a summary PDF per race (practice/qualifying/final standings, no heat details or lap times) and a raw JSON package. Nothing covers "everything run today, per class" in a form people can read or open in Excel, and results only live in RC RaceCore. + +- [ ] **CSV export for a whole race day.** Pick a date and a class (or all classes). One row per lap from every session that day: class, session (in running order), driver, transponder, lap number, lap time, time of day, plus a session summary (position, laps, total time, best lap, average). Frontend only: reuse `buildLeaderboard`, `orderSessionsForRunning` and the existing file download helper; no server or schema change. Button in the Results archive when filtered on a date, with a shortcut on the series round. +- [ ] **Readable day PDF per class (optional, after the CSV).** The day result used for series points (manual ✎ Result if set), then every session in running order with its full result. Lap-by-lap times stay in the CSV. +- [ ] **Publish to an external results site (e.g. House of RC).** Create the race / series there over its API and push the results (and optionally laps) after each session or at the end of the day, so the club's racing gets more exposure. Open questions before building: is there a public API and how is it authenticated (club account / API key stored in Settings), what format it expects (class, heats, qualifying, finals, points), whether it can be updated afterwards when a result is corrected by hand, and what happens when the club PC is offline (queue and retry). Start by investigating the API; keep the integration as a separate server module so a different site can be added later. + ## Documentation maintenance - [x] Update the architecture's module/dependency inventory as modules change.