I'll copy in my comments from another thread and update it (EDIT - updated to include Joe's input):
Title / Name - KEEP this existing field
Year of release - KEEP this existing field
Number printed - KEEP this existing field
Producer/Creator - convert the current 'brand' field to this field that is simply the person or company who put the project together. I think this is the same as Joe's "Production Company" which yes it some cases it can be multiple. Some decks may need updates as a result, but this is the closest match I think
Manufacturer - who printed the deck...however, do we specify USPCC Ohio vs Kentucky? What about EPCC and Legends?
Brand - already handled via naming convention, but perhaps this could be moved into distinct field. Assume all recent Hoyle, Kem, etc would be USPCC and these would then be properly implemented as brand? In some cases this may be the same as Manufacturer if self produced and branded.
Artist - Could be multiple, but any collaboration (Ultimate Deck, goverdose, etc) could just be 'Varied'
Tags - free form mulit-select input, but ability to select or type ahead previously used values. Can be used for things like Transformation, Novelty, Photo, Souvenir/Advertising, Facsimile/Reproduction, Casino, Flourishing, Magic, Art, embossed, foil, inside tuck printing, gilded edges, etc... It's possible some of these would be better served as a checkbox stand alone field instead, especially Vintage (with guideline of >20 years old or a reproduction), but if you are able to make tags searchable and results sortable I think you'll accomplish the same thing with more flexibility.
Country of Manufacture
Edition - Already covered in naming convention, I don't see a need to group by this so not essential in my mind. It's also not used often unless there is a new version. Unless I am missing something?
Variant - same as above
Platform - Joe, what was this? I had a note of you mentioning it before.
I would also really like to emphasize the User defined values
that people can use within their own collections which would handle a lot of the categorizing/sorting specialty requests. This would be good for features that only a small subset of users would need or care about.