Working On An Offline Collection

Hi everyone,

Because I don't want my collection data stored in a third-party cloud or tied to a monthly subscription, I started building a lightweight, 100% offline Windows desktop application (stores everything locally on your own PC in a private database).

Question for you.

1. What specific fields or details are an absolute "must-have" for you when cataloging an item?
2. For those who have insured their collection: what information did your insurance company require in your documentation report?
3. Looking at the screenshot, is there anything you would change or add to make daily cataloging faster?

Thanks in advance for any thoughts or suggestions!

I built an Excel sheet that included what you have plus a field for certificate numbers and organizations, price paid and from where/whom and final disposition if sold with sold price. Also, a field for special notes.

I insured with Hugh Woods and nothing other than a lump sum value was necessary. My worksheet was my backup along with scanned in receipts and certificate images in case a claim was ever necessary.

My images were not linked to my worksheet, but what you have done looks useful. I do like being able to sort out what I need versus what I have or want to replace.

Thank you so much for sharing this, that insight about Hugh Wood only requiring a lump sum upfront while keeping your own backup with receipts and certificates for a potential claim is super helpful!

Linking multiple images (like scanned receipts and certificates) directly to each item so they aren't separated from the sheet was actually my main reason for building this.

Your point about tracking "final disposition / sold price" and having a status for items you "want to replace/upgrade" (alongside "owned" and "wishlist") is a fantastic idea. Do you keep sold items in the same list with a "Sold" status, or do you prefer moving them to a separate archive tab?

I would suggest you have a look at https://www.lastdodo.nl/nl to see what basic information would be required. It, also, will show you the problems with creating an app for collections of different types.

For an individual stamp collector, information on the actual stamp in the collection, also, would be required.
Certificate numbers and issuers, as suggested, would be very interesting.
Not just price paid, but also the source may be interesting (keep in mind a platform may also involve a seller).
You might want to add specialist items, or formats (e.g. block of four, or cylinder block, sheet header, etc.).
Colours, types, dies, luminescence (incl. layout, colour, etc.) etc.
For stamps with overprints: similar information might be required for the basic stamp and the overprint, with a cross reference to the original stamp.

The end purpose(s) of any spreadsheet or database will determine what fields you will find useful to create - whether it is primarily a "have list", a "want list", an "insurance inventory", etc. The "must have" fields may differ significantly depending on the end purpose. Since we know very little about the extent, value, focus, goals of your collection, etc., these are largely questions only you can truly answer. A collection of a few thousand items may also suggest a different approach than one with 100,000 items.

Beyond that, is the purpose to spend time with your computer or your collection? Why spend time recreating a listing which largely repeats stamp catalog listings versus creating a unique database of new knowledge like a census of postal history items where sorting by various fields can reveal unseen trends.

Thank you both, your replies inspired me to do a deep dive into LastDodo and philatelic certificates (PF, PSE, APEX, BPP, RPSL, NVPH)!

To serve stamp collectors without cluttering the screen, I'm adding an optional "Philately" preset with:
- Certificate Issuer, Cert #, Date, Opinion & direct lookup links
- Format (block of 4, cylinder block, sheet header, cover), luminescence, die & overprint cross-reference
- Split fields for Buying Platform vs. Individual Seller

And spot on regarding spending time with your collection instead of re-typing a catalog! The real value is tracking what is unique to YOUR specimen (provenance, certificates, insurance proof, or a searchable postal history census).

One idea I came up with myself is a button to generate a 1-page printable "Item Report" per piece (showing the stamp photo, certificate scan, and specs) to place in an album or folder — is that something you would find useful?

For some speciality collections like Machins I use excel but for general worldwide I use Liberty Street's software Stamp Manage mainly because 1) it includes Scott numbers (licensed) and 2) I own the data and can use it outside of the app like in another database app.

The software uses Microsoft Access database and the inventory file is fully open meaning you can view the database directly. It is a local file (no cloud). It has a powerful report system but I rarely do much except to export to an excel file.

SM provides the data for some files and some aspects are incomplete (missing issues, images, data). You can add them yourself. In any given year, they do provide a couple of updates.

Here are fields they provide.

To John's point about number of items I did not enter every stamp I owned into the DB. While I did not create my DB for the sole purpose of insurance documentation, value was the trigger for being entered. My triggers was $100 PAID, not catalog value. Hugh Wood would not expect every $2 catalog value stamp to be individually documented since we all know the market value is a small percentage. We also know that a $500 cv stamp can be had for 5 or 10 percent of cv when it has issues. My parameters kept time spent on data entry in check IMO. Those hours would payoff if the unthinkable happened.

Note: All receipt and certs were in binders with images backed up digitally on a portable drive I could travel with and easily and safely store.

In the first post, I assumed we were talking about a collector's personal spreadsheet/database, but now it feels like we're talking about a product? Am I reading this wrong?

Fair question, and I really appreciate you asking it directly!

To be completely transparent: yes, I am an independent Windows software developer building a desktop application. I originally started building it for my own collection because I was frustrated by modern tools turning into cloud subscriptions with data lock-in.

I deliberately did not include any website links, pricing, or sales pitches in my post because I genuinely came here to learn. Most software developers build generic inventory apps in a vacuum without ever consulting real philatelists, which is why most tools are useless for stamps.

The Stamp Manage column list you shared is absolute gold (and I completely agree that owning your own local data file without cloud lock-in is essential). The $100 paid threshold for Hugh Wood insurance is also a brilliant perspective that solves the data entry dilemma.

My only goal was to listen to experienced collectors so I don't build the wrong things. If discussing member-developed software is outside the scope of this board, I sincerely apologize and will gladly keep it to reading, I am truly grateful for everyone's generous time and expertise here!