Which fields needed in a database should I have one custom made for SAKs?

[FolderBeholder]

I'm in communication with the gentleman who makes a database for fountain pens.
Fields such as nib size, filling system, nib material, etc. are specific to pens.

Which fields would you all like to see in a program written for Swiss Army Knives?

Here's a screen shot of the fountain pen database:

[ReamerPunch]

What? 

[VICMAN]

I'm in communication with the gentleman who makes a database for fountain pens.
Fields such as nib size, filling system, nib material, etc. are specific to pens.

Which fields would you all like to see in a program written for Swiss Army Knives?

Here's a screen shot of the fountain pen database:

How about these:


MODEL
LIST OF TOOLS ON PARTICULAR MODEL
TYPE OF BOX
PRICE PAID
YEAR MADE
DATE OF PURCHASE
PURCHASED FROM
HANDLE COLOR
HANDLE MATERIAL

[FolderBeholder]

Yes Vicman, and maybe:

Back Layer Tools
Scale Tools
Size, 91mm etc.
Tang Stamp (maybe this would be a photo field)

[FolderBeholder]

What? 

I'm trying to figure out a way to categorize all the different characteristics of the SAKs in my collection. 
And keep track of value, for when someone ends up having to sell it off.

[VICMAN]

Yes Vicman, and maybe:

Back Layer Tools
Scale Tools
Size, 91mm etc.
Tang Stamp (maybe this would be a photo field)

That sounds good!

[NorCalJim]

How timely!

I have just been working on a solution for my own SAK collection.

Ever since you mentioned in one of your posts that you were entering SAK info in a database, it got me thinking that I should be using a collection database and I wanted something more than Excel spreadsheet.  I use a Mac for my personal computing needs and expected to find a gold mine of choices on Apple's App store for my MacBook Air.  I didn't find a gold mine but I felt like a prospector spending way too much time looking for it.  After weeks of research, I purchased Ninox.  It is a database management application with all the data types that I need and the ability to easily modify the database structure as my needs change.  I installed it yesterday and spent around an hour or so playing with it.  I haven't looked at the online manual yet but it is pretty straight-forward with drag & drop capabilities for database table creation.  There is cloud support for synchronization.  So far, it looks great for my needs.

Here is what my record structure looks like (keep in mind that I wanted to exercise some of the data types like "Color" and fully expect further changes):

Model
Model Number
Brand (Manufacturer such as Victorinox or Wenger)
Purchase Date
Unit Cost
Shipping
Total (formula data type to perform a calculation on unit cost & shipping cost)
Size (pre-defined choices for selection with 91 mm set as default)
Condition (pre-defined choices for selection with new set as default)
Layers (currently text data type)
Scales (Alox, Cellidor & Nylon defined as my choice selection with Cellidor set as default)
Color (color data type that I probably with change to a choice data type)
Plus (logical data type)
Logo (currently a text data type but will probably change to a choice data type)
Retired (logical data type)
Photo (image data type)
Notes (rich text data type)

[Mechanickal]

I've got the fields in a "DIY collection software program":

Picture,
Brand, model name, model nr, purchase date, production date, purchase price, new price, average second hand price, condition and nr of tools/implements.

[FolderBeholder]

Thank you all for the information, keep the ideas coming. 

[philodemus]

I currently keep a list in Excel for my alox collection. You may need slightly different fields for features that are specific to cellidor models.

BRAND (Victorinox, Wenger)
MODEL
YEAR
SCALE MATERIAL (alox, stainless, sterling silver)
SIZE (58mm, 74mm, 84mm, 93mm)
LAYERS
SCALE COLOR
SHIELD COLOR
SHIELD TYPE (old cross, new shield, Soldier shield, WK cross, old Cadet shield)
TANG STAMP
BAIL (yes/no)
KEYRING (yes/no)
ORIGINAL BOX (yes/no)
ADVERTISING
PRICE
CONDITION
NOTES (blade engravings, limited editions, available in specific markets, special features, etc.)

I hope that gives you some ideas. 

[FolderBeholder]

I currently keep a list in Excel for my alox collection. You may need slightly different fields for features that are specific to cellidor models.

BRAND (Victorinox, Wenger)
MODEL
YEAR
SCALE MATERIAL (alox, stainless, sterling silver)
SIZE (58mm, 74mm, 84mm, 93mm)
LAYERS
SCALE COLOR
SHIELD COLOR
SHIELD TYPE (old cross, new shield, Soldier shield, WK cross, old Cadet shield)
TANG STAMP
BAIL (yes/no)
KEYRING (yes/no)
ORIGINAL BOX (yes/no)
ADVERTISING
PRICE
CONDITION
NOTES (blade engravings, limited editions, available in specific markets, special features, etc.)

I hope that gives you some ideas. 

Yes, it does give me ideas, I specifically like "Original Box".  I am over the moon for those. 

[Ron Who]

I would suggest creating a simple prototype and start using it. You'll find out soon enough what is right and what is missing. Getting everything right before actual use is quite difficult, and for most database applications known to be impossible. That's what I learned in 20 years in IT.

[FolderBeholder]

Sound advice Ronald.   

[ColoSwiss]

In my excel spread sheet I have columns for : Brand, Description (including name, number of blades, handles, etc), Model number, Length, Box (yes or no), Price, Remarks (bought on a trip, gift, etc)

I sort by Brand, Length, Description; so all the Vics are together then all the 58mms, then all the Classics. The Description field could be broken up into a number of fields and expanded in a data base, but I don't have room in the spread sheet. I have a data sheet in each box, listing what's in each slot. Try and make sure the descriptions match those in the spreadsheet, to help keep track of everything. I don't list which box an item's in, since things are likely to get moved around as new stuff comes in.

[FolderBeholder]

Sounds great CS.  I just added the length column to Excel in mine as well.  Mainly have 91mm and 84mm at this time.
Only have one Wenger, and one inbound....I'm going to try and resist going down the Wenger slippery-slope.   

[sir_mike]

Good suggestions being given.

My advice is also to think about how you will want to "sort" or "view" the information that you are collection.  Then create a field for that way.  Like a column in a spreadsheet, that is the way sorting/reporting is done.

I know you already listed this but for an example, since you have size as a field, you will be able to list or view a report on any 91mm, 84mm, etc.  so for sure cost is one, date purchased, purchased from, date sold (just in case), amount sold for, new or used, etc. may all be considered.

Personally, unless you literally have like hundreds of sak's, a spreadsheet is more than enough whereas a database is kinda overkill but it is a preference thing! 

[ColoSwiss]

Sounds great CS.  I just added the length column to Excel in mine as well.  Mainly have 91mm and 84mm at this time.
Only have one Wenger, and one inbound....I'm going to try and resist going down the Wenger slippery-slope.   

But its such a nice slippery-slope!   

In my SAK spread sheet I have four brands; Delemont (the new Wenger Vics), Victorinox, Wenger, Wenger/Swiss Buck.

Have another spread sheet for the non-SAKs. Slightly different lay-out, and different sorting criteria. The big ones there are brand (Buck, Case, etc) and description (Stockman, Trapper, fixed blade, etc).

Have fun!   

[FolderBeholder]

I'm going to try and resist going down the Wenger slippery-slope.   

But its such a nice slippery-slope!   

Oh, I can tell it is, I just got a Wenger Pathfinder today, and I liked it immediately.
I have a small plier inbound as well (can't recall the name of it).