loupekind records adopt¶
Description¶
Give a folder the records this computer holds for a shoot it can no longer reach. Use it
when a shoot's folder is gone and the same frames are now in another folder that
LoupeKind treats as a new shoot, such as after ingesting the card again or copying the
originals somewhere without their .loupekind.
loupekind doctor lists the shoots this computer can't reach, each with
its ID and where it was last seen. Pass that ID to adopt, with the folder that holds the
frames now:
loupekind doctor
loupekind records adopt 3f9c0a6e1b2d4c5e8f7a9b0c1d2e3f40 --shoot ~/Pictures/smith-wedding
The folder takes that shoot's ID, so from then on it opens with that shoot's verdicts,
ratings, edits and reviews, and its snapshot is written from them. The records the folder
had are kept in the database under its old ID, which adopt prints, and adopting that ID
puts them back. No folder holds them meanwhile, so doctor doesn't list them.
adopt refuses:
| When | Why |
|---|---|
| The ID isn't one this computer has records for | There's nothing to adopt. Check it against doctor's list |
| The shoot's folder is still where it was and still holds it | That folder is the shoot. Open it instead |
| The folder holds none of that shoot's frames unchanged | It's probably the wrong ID, and adopting would give this folder another shoot's work |
One unchanged frame is enough, so a folder you've already deleted rejects from can still adopt its shoot.
adopt isn't offered to an AI agent over MCP.
Usage¶
Flags¶
| Flag | Default | What it does |
|---|---|---|
--shoot |
the current directory | The folder to give the records to |
Plus the global flags on every command. With --output json it
prints the folder, the ID it took and the ID it had.
See also¶
- Shoot layout: when a folder keeps its shoot's ID, and when it doesn't
loupekind records