Build the scanning guide page #35

New issue

Open

opened 2026-07-28 04:57:32 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-28 04:57:32 +00:00

Context

The quality of every date in the system depends on how the photos were scanned in the
first place â€” resolution, whether backs were scanned, and how files were named so the
filename parser can read album and sequence. The spec includes a scanning guide page for
exactly this reason.

Scope

An in-app scanning guide documenting conventions and recommended settings.

Implementation notes

Document the filename convention the parser actually implements, with worked examples of
both valid and invalid names. Generate or test these examples against the real parser so
the guide cannot drift from the code â€” a scanning guide that documents a convention the
parser does not accept is worse than no guide, because it produces a whole batch of
unparseable scans.
Recommended DPI and format, and why originals should be kept lossless.
How to scan backs and why they matter for dating.
Album and sequence numbering, including how to handle inserted or missing photos.
What good EXIF looks like and the scanner-timestamp pitfall (the scan date is not the
photo date).
A short pre-scan checklist a family member can follow without reading the whole page.
Reachable from the main navigation, not buried in an admin area â€” the people scanning
are often not the people administering.

Done when

The guide documents the real filename convention with tested examples
Scanner settings, back scanning, and numbering are covered
A concise checklist is available
The page is reachable from the main navigation

References

backend/app/services/filename_parser.py (source of truth for conventions)
docs/circa-spec.md Phase 3

## Context The quality of every date in the system depends on how the photos were scanned in the first place â€” resolution, whether backs were scanned, and how files were named so the filename parser can read album and sequence. The spec includes a scanning guide page for exactly this reason. ## Scope An in-app scanning guide documenting conventions and recommended settings. ## Implementation notes - Document the filename convention the parser actually implements, with worked examples of both valid and invalid names. Generate or test these examples against the real parser so the guide cannot drift from the code â€” a scanning guide that documents a convention the parser does not accept is worse than no guide, because it produces a whole batch of unparseable scans. - Recommended DPI and format, and why originals should be kept lossless. - How to scan backs and why they matter for dating. - Album and sequence numbering, including how to handle inserted or missing photos. - What good EXIF looks like and the scanner-timestamp pitfall (the scan date is not the photo date). - A short pre-scan checklist a family member can follow without reading the whole page. - Reachable from the main navigation, not buried in an admin area â€” the people scanning are often not the people administering. ## Done when - [ ] The guide documents the real filename convention with tested examples - [ ] Scanner settings, back scanning, and numbering are covered - [ ] A concise checklist is available - [ ] The page is reachable from the main navigation ## References - `backend/app/services/filename_parser.py` (source of truth for conventions) - `docs/circa-spec.md` Phase 3

claude-bot added this to the v0.5.0 milestone

2026-07-28 04:57:32 +00:00

claude-bot added the

docs

frontend

labels

2026-07-28 04:57:32 +00:00