RO-Crate Photo Browser

People

Sub-collections

Settings

Write metadata into photo files

Writes confirmed faces, and any keyword, title, caption or rating you edit here, into the photo files themselves — so the metadata travels with the photo rather than living only in this collection's crates.

⚠️ This directly modifies your original photo files (via exiftool), with no backup of their previous bytes beyond whatever you already keep yourself. Off by default — only turn on if you understand the risk. Takes effect the next time rocphotos serve is restarted, not immediately.

Export path — where "Export Album" writes to. Leave blank to export to _exports/ inside the collection. An absolute path (or one starting with ~) exports outside the collection instead, and only works from rocphotos serve or the CLI, not a browser tab. Copy face regions and other metadata into the exported files

Writes what this app knows — confirmed faces and pets, keywords, title, caption, rating — into each exported copy, so it stands on its own in any other photo tool. Only ever touches the copies, never your originals. Needs exiftool, and rocphotos serve or the CLI.

Excluded directory patterns (one regular expression per line — matched against a directory's own name, not its full path) Excluded file patterns (one regular expression per line) Save

Preview pages

Rewrites every ro-crate-preview.html from the crates and index as they stand — including the People list on each page — without re-reading any photos.

Regenerate Preview HTML

MASP profile

The profile decides what can be recorded about a person and how it is checked — the fields on the People tab come straight from it. Each build of this app carries one; a collection can carry its own instead, so a change to the profile can be tried out here before it goes anywhere. The file is a MASP profile crate's ro-crate-metadata.json, and it is stored in the collection, so handing somebody the folder hands them the profile too.

Migrations

One-off sweeps that bring every ro-crate-metadata.json in this collection up to date with a change to the data model. No photo is re-read and no thumbnail is made, so this is quick even on a very large collection, and running it twice is harmless. Tick what to run, then Dry Run first to see what it would change.