ALBUM / PHOTO-ARKHIVE PHOTO-ARKHIVE POST-SCAN
Auto-rotate Restoration depth Metadata injection Family review

Everything after the scan needs its own workflow, not an afterthought.

The third research pass maps the real post-scan stack: normalize orientation, restore on copies, write portable metadata, date the uncertain images honestly, and use collaboration plus face tagging to turn a folder into a family archive.

Workflow

The post-scan stack should run in a disciplined sequence.

Each layer makes the next one cheaper and safer. Skip the order and the archive becomes harder to trust.

1. Normalize orientation

Scanners do not solve orientation for you. Bake rotation into pixels, then reset orientation state so later tools do not double-rotate files.

2. Preserve then restore

Keep the raw master first, then run tonal correction, dust cleanup, and AI enhancement on working copies with clear labels.

3. Write metadata to standards

Push dates, people, keywords, locations, and descriptions into EXIF, IPTC, and XMP instead of trapping them inside one app.

4. Date uncertain images honestly

Use anchor events, approximate dates, and confidence labels so chronology works without inventing fake certainty.

5. Share for identification

Use collaborative review albums, spreadsheets, and comments to pull names and stories out of family members while they still know them.

6. Tag faces in a local-first lane

Use face clustering and manual review to reduce repeated naming work, but keep a master archive outside platform lock-in.

Studios

Split the post-scan work into focused labs.

The research is too dense for one page. These labs separate image cleanup, metadata strategy, and family review/tagging.

Interview

Life-story questions and narration capture

Use this page to interview grandparents and older relatives with prompts that can feed an album voiceover, oral history, memorial piece, or family archive record.

gentle openers deep memory prompts audio / video / writing
Open Interview Page

Rules

Three rules should survive every app change.

These are the constraints that keep the archive durable even if tools, services, or preferences change later.

Original first

Always preserve the original scan or TIFF master, then derive rotated, restored, cropped, tagged, and shared variants from that source.

Standard metadata first

If names, dates, captions, and locations do not travel in standard metadata or sidecars, the archive is still dependent on one vendor database.

Human knowledge now

The hardest thing to restore later is identity. A kitchen-table naming session can be more valuable than another hour of pixel cleanup.

Golden rule: use cloud platforms as discovery and collaboration layers, not as the only authoritative archive.