Originally Posted by _Chimera
Guys the product database is growing to be an epic mess, do you understand the difference between Product and Model?
In cases, add one (only one !) product for each case, then add models (black, white, pink, whatever), I don't think you should make a new product for each model.
· Silverstone Temjin Series TJ07
· Silverstone Temjin Series TJ11
Now, on the "MODELS" tab you have the silver, the black, with and without window with the part number.
I dont like how the database looks, with one product for each model, and messed up product names.
I agree with you, but the problem is the problem is that the product match doesn't seem to even care about the model number.
Also, how do we decide what "model" means. I mean, I have an i7-2600K. Which is technically a submodel of the i7-2600, which is technically a model of the Second Generation Core i7 Series. So if I matched to "Second Generation Core i7 Series," what processor do I really have? If I match to "i7-2600," I can see people responding to OCing questions as, "well you don't have an OCable processor," which wouldn't be the case.
Furthermore, if the intent of the database is to track products, then I image you want to track them model by model rather than on a product level. For certain things, like colors, I don't think it matter that much. But, in the case of RAM, it would be interesting and useful to know who got the 1600MHz model vs the 1866MHz model. Or with motherboards: are people buying the P8Z68-V Pro, the Deluxe, the Gen3?
I think that we need more guidelines on what constitutes models, and what OCN wants from the product database. Also, we need a style for a naming convention.