History and restore¶
Every change to your collection is recorded, and a snapshot is taken before the first change of each day.
KCPARTS 2026-09-20 12:00:00 LEGHST HISTORY OF CHANGES User: admin (100%) Role: admin Source: ModernWMS ADMIN ──────────────────────────────────────────────────────────────────────────────── 1=Overview 2=PartDB Hub 3=Operations 4=Script Hub 5=LEGO Collection 6=Admin ──────────────────────────────────────────────────────────────────────────────── F1=Help F2=Go To F3=Exit F9=Undo F6=Quick Add F10=Lock F12=Cancel 5 recent change(s), newest first When Who What Item Colour Qty Note 10-24 04:41 system add set 10497 — 0 -> 1 Galileo Space Telescope 10-24 04:41 system add part 3004 White 0 -> 80 10-24 04:41 system add part 3023 Blue 0 -> 300 10-24 04:41 system add part 3001 Blue 0 -> 120 10-24 04:41 system add part 3001 Red 0 -> 24 Press R to refresh, Q / ESC to go back
The journal¶
LEGO → History of Changes or:
wms-go lego history # newest first: when, who, what, item, colour, before -> after
wms-go lego history --part 3001
Adds, quantity changes, deletes, minimum changes, bulk imports and restores are recorded with the user who did it (the signed-in
user in the interface, cli:<name> from the command line).
Snapshots and the growth chart¶
wms-go lego snapshots # restore points, with a pieces-over-time sparkline
wms-go lego snapshots take --label "before the big sort"
Restore¶
wms-go lego restore 2026-09-20 --dry-run # exactly what would change
wms-go lego restore 14 --yes
Restore puts your owned parts and sets back as they were. It saves the present first (as the newest snapshot), so a restore can itself be
undone by restoring that snapshot. Part-DB isn't touched: run wms-go lego sync-parts afterwards to bring it back in line. Parts that exist
both then and now keep their Part-DB link.
Up to 400 daily snapshots are kept (about a year).