Paper to pixels

Use with: build-website, ship-on-github. Resume line when done: Built {project_name}, digitizing {org}'s paper records into a structured public dataset — live at {url}

Brief

Your club or team keeps a logbook, sign-in sheet, or scorebook on paper. Turn it into a structured data file and a page that presents it, with the keeper of the book checking your transcription. The hard part is faithful transcription: the messy margins, the crossed-out entries, the pages where the format changed halfway through.

Personalize

• The book you have standing to digitize. One from a group you belong to, offered with the keeper's permission. The keeper signs off on the finished version.
• What the paper format becomes. Study a few pages before designing the data record; the paper always has cases the obvious schema misses. Document the mapping in the README.
• Names need consent. Sign-in sheets contain other people. Agree with the keeper what is public: full names, initials, or counts only.

Milestones

1. Get permission; photograph or scan every page so the original is preserved.
2. Design the record format from the paper's own patterns; write the mapping rules in the README, including how ambiguous entries are handled.
3. Transcribe everything into one data file; flag entries you could not read or interpret.
4. Build the page: the data browsable and totaled, with a link to the repo holding the file.
5. Review session with the keeper; correct the record where they spot errors.
6. Publish repo and page; hand the keeper the link and the file.

Done means

• Live page presenting the data, backed by a public repo with the structured file
• Every page of the original scanned and kept
• Illegible or ambiguous entries flagged in the data, never invented
• The keeper reviewed and approved the transcription and the naming policy
• README documents the paper-to-data mapping in your words
• SESSIONS.md has an entry per session, written by you