I could also make the replay tags visible in the full list of results for a track. Would that help?
It would help; also it is, for unrelated reasons, a feature I have been wanting for a long time
The way I once imagined it was having little (G) and (N) indicators in the replay entries, like the (A) ones for automatic transmission laps; in any case, I'll be happy with however form of display you decide on.
On an additional note, another thing I would like to do is setting up some architecture for the Archive more resilient than a bunch of folders, textfiles and spreadsheets loosely correlated with each other. I'm not sure I will have time to play with that before the release, though.
Tell me more.
While I didn't really feel such things when I was making an effort to update my working version of the archive at the end of every race, the prospect of updating it after not having touched it in years makes the procedures seem a bit fragile -- prone to mistakes, and perhaps with sub-optimal results for users. More specifically, I would like to have a single point of truth for race information: it might be, for instance, a SQLite database from which the text file race lists and the spreadsheet could be generated, and which could also be used to perform consistency checks on the .TRK and .RPL files (if not storing the files themselves there, though there are some subtleties that would have to be dealt with for that to work well). In terms of amount of work to do, the main complication is that such a plan would entail not only designing the database schema and writing the program, but also getting the ~900 race entries into the database -- a process that in all likelihood can't be fully automated.
