Skip to content

loupekind records

Description

Work with a shoot's records directly: its verdicts, ratings, edits, reviews and export history. They live in this computer's database, and a copy of them, the snapshot, travels in the shoot's folder as .loupekind/records.db. records is a command group; use a subcommand:

Subcommand Purpose
loupekind records restore Replace this computer's records for a shoot with its folder's snapshot
loupekind records dump Print a shoot's records as YAML or JSON
loupekind records rebuild Rebuild this computer's records database from your shoots' snapshots
loupekind records adopt Give a folder the records of a shoot this computer can no longer reach

How the snapshot is kept

LoupeKind writes the snapshot at the end of a cull, after an export, when the studio closes, and once when a shoot is first opened. It doesn't write one on every verdict, so a snapshot can be a little behind the database until the next of those.

When a shoot is opened:

  • This computer has never seen the shoot. Its records come from the snapshot, with no question asked.
  • The snapshot holds work this computer doesn't have, because it was worked on another computer. That's judged by the newest change in each, then by comparing the records, so work this computer sent and got back isn't counted. LoupeKind keeps using this computer's records and says so: the CLI prints a notice, and the studio shows a banner with when each side last changed and a Use the records in this folder button. It never overwrites that snapshot. Run records restore to take it. If you carry on here instead, your work is kept in this computer's database, but no snapshot is written until you restore or remove the folder's.
  • Otherwise the snapshot is older or the same, and the next write brings it up to date.

Usage

loupekind records <subcommand> [flags]

See also