Six pipeline stages and two checkpoints that are yours. Stages run from the Pipeline page (or the CLI — both share all state and either can pick up where the other left off):
- extract — every photo goes to Claude vision once; what it reads (titles plus edition cues: publisher, edition wording, year, language) lands on the Titles page. Boxes it can see but can't read become reshoot tickets on the Photos page. @@ -24,7 +24,7 @@
What each page is for
-Pipeline — run stages one at a time and watch their live output. Shows what's blocking (missing keys, stub data) and the counts at every step.
Photos — drag photos in (or drop them in the photos/ folder). Each photo has its own page listing every title read from it and any reshoot tickets — boxes seen but not identified. Photograph those up close, drop the new shot in, and extract again. Re-uploading a photo with the same name re-extracts it.
Titles — every read off your shelves, alphabetized, with its status and photos. This is the proofread checkpoint: edit, split, remove. Its badge counts shaky read lines — the model wasn't sure and nothing has verified them; filter to them, then press ✓ looks right or edit each one.
@@ -34,7 +34,7 @@Fixing the titles: edit, split, remove
-Vision reads aren't perfect, and you know things the photos don't show. Every line on the Titles page has curation actions, and every one of them is durable: the decision is saved in a small committed file and replayed on every rebuild, so re-running extract or resolve can never undo it.
edit — fix a misread title or add cues you already know (publisher, edition, year, language). A corrected misspelling automatically merges with a correctly-read sighting of the same game from another photo. If the line already had a BGG match, saving re-queues it so resolve searches again with the corrected data.
split into copies — one line, several physical boxes? Splitting makes each photo its own copy, and each copy picks its own edition afterward. Appears on any line whose title was seen in more than one photo. Splitting one game never affects a same-named different edition.
@@ -43,7 +43,7 @@What the status chips mean
-awaiting BGG extracted, not yet matched — usually waiting on the BGG API token.
auto matched confidently, no review needed. approved you picked the match yourself.
ambiguous several plausible games — needs your pick on Review. unmatched nothing plausible found — enter a BGG id or re-search on Review.
@@ -53,14 +53,24 @@Keyboard shortcuts
-Review: j/k move between cards · 1–9 pick a candidate · r reject · m manual BGG id · u edition unknown · v veto a merge.
Photo pages: ←/→ move between photos.
Your data, on disk
-Everything lives in flat files under data/ — inspectable, hand-editable, and git-friendly. The pipeline artifacts: titles.json (what was read), matches.csv (what it matched), to_add.csv/to_update.csv (what upload will do), upload_log.csv (what it did), games.json (the library). Your curation: title_edits.json, title_splits.json, title_removals.json, unidentified_dismissed.json.
Credentials never live in files — only environment variables, set up by bggpipe init. The app serves localhost only, unless started with --lan — that opens it to your network behind a per-run access key printed at startup (no login beyond the key; trusted networks only).
More depth: the README covers setup and photo technique; docs/bgg-upload-flow.md documents the upload automation.
The piper
+
+ Mascot art by Juniper, used with pride.
+BoardGameGeek and BGG are trademarks of BoardGameGeek, LLC. + bggpipe is an independent project, not affiliated with or endorsed by + BoardGameGeek.
+
bggpipeshelf → BGG pipeline
-