Working On An Offline Collection

Wow, this is absolute gold, thank you so much, everyone! This is exactly the kind of deep, real-world insight no developer can figure out from behind a desk without talking to real collectors.

A few specific takeaways that I am immediately incorporating:

The Scott Sorting Order nuance (@ZebraMan):
That point about standard alphanumeric sorting breaking down with philatelic numbering (599A having to follow 599b, and JQ following Q) is brilliant. Standard database collation completely wrecks catalog order here. Adding a dedicated, customizable sort_order field (pre-filled with the catalog number but fully overridable) solves this cleanly without forcing rigid sorting rules that fail on edge cases.

Keyboard-First Workflow & Tabbing (@ZebraMan):
Loud and clear on the UI! Reaching for the mouse every three seconds during a long cataloging session is pure friction. All dropdowns and date pickers will fully support tab-navigation and quick typing to select, so your hands never have to leave the home row.

Avoiding 60-Field Clutter & Free-form Descriptions:
I completely agree that facing 60 empty boxes is exhausting. The goal is to keep the default entry clean and modular (collapsible field groups), anchored around a Short Description (for quick duplicate disambiguation like "Baltimore cancel") and a generous Long Description where you can simply paste the exact auction or dealer write-up without having to click ten different dropdowns.

Multiple Catalog IDs & Varieties:
The example of the Russia collection illustrates perfectly why forcing a single catalog field fails. International and specialty collecting requires side-by-side identifiers (e.g. Scott # + Michel / Specialized #) so varieties that carry high premiums aren't lost in translation.

Sub-collections & Topicals (@angore):
Having clean separation between a master inventory and topical/thematic sub-sets (like that Christmas collection example) without messy duplicate data is a great architectural pointer.

Thank you all for taking the time to write such detailed responses, this is shaping CollectRef into something genuinely useful rather than just another generic spreadsheet clone!