too many attributes :(

[MachaNeko]

i cant do that. these are not jewelry theyre scales. the type you weigh things with. but the bigger kind for trucks and such. each product is unique and has its own model to purchase. the items are broken down as fasr as possible already so that idea wont work.

[fairestcape]

each product is unique and has its own model to purchase.

Do you mean that the scales are CUSTOMIZED by the client when they place an order?

[MachaNeko]

no but its premade like that by the company. capacity and diameter determine the model.


here is what i mean.
One product that has models. these models only exist becuase the capacity is different for them.

My Site Example

im sorry if this doesnt make much sense.

btw the attributes are at the bottom of the page

[Zinfandel]

MachaNeko,

Based on what I see from the example link, you've already simplified it to where the model number has been attributized to represent the various permutations of attributes.

I don't believe it can get any simpler than that.

The problem is that each product requires it's own set of attributes.
Unless you consider this approach:
category > subcateogry > product > no attributes needed

Digital Force Gauges > DPS Series > DPS-005> no attributes
Digital Force Gauges > DPS Series > DPS-010> no attributes
Digital Force Gauges > DPS Series > DPS-040> no attributes
Digital Force Gauges > DPS Series > DPS-011> no attributes
Digital Force Gauges > DPS Series > DPS-044> no attributes
Digital Force Gauges > DPS Series > DPS-110> no attributes
Digital Force Gauges > DPS Series > DPS-220> no attributes

The capacity for each is within the description.
All you need to do is enter one, and then copy it six times, change the model# and the capacity in the description.
Dont forget to change the price on DPS-220

BTW, if you keep it as is atleast make the attribute values as I have them above for uniformity. It'll look alot better.

[MachaNeko]

i was afraid of that. there is no easier way than copy and modify?

my new concern is how to limit how many show up when adding new attributes to new products. like if i add a new product with attributes called jrp force gauge, when i go to add the attributes id like to be able to see only the new attributes for jrp instead of my whole 600 list.

[Zinfandel]

Approach every such problem by analyzing it at its most fundamental level.

Attributes for your products are not standardized across all products.
The set of capacity ranges differs for every model scale.

Either
1) you create a product for every set of attributes and do not define attributes.
2) you create an elaborate and large set of attributes and fewer products.

Sit with a pencil and paper, choose a product and write down the variables. Then try to organize them using different approaches and see what makes the best sense for you.

In the example we used above the model number differs within the same product so it becomes a function of the attributes that are chosen. I believe every product model# should be a product unto itself. This is the only way to avoid losing your mind.

[Website Rob]

MachaNeko, you have a Bear of a site and it will either make you or break you. And I say that with good intentions.

Due to the nature of the Industry and Products you are providing for that Industry, there is no way around it; you will have to have loads of attributes and be highly organized in your database structure.

Using the example page you provided, you can have One page listing 6 Models or 6 pages listing One Model each.

The latter method would mean having 6 pages that are pretty much exactly like each other except for one piece of information; the Model number.

The former method which you are using now is the better; saves on duplication of Content but does require 6 attributes.


In fact, it looks like you are skimping on attributes with some Products. Your page for CW500 Roller Deck Scale for example, lists 2 Models with many Options -- 32 to be exact. What is the baseline for Options already provided with each Model? Although one can choose either of the Models, how does one choose their Options? What is the pricing for each option?


The above is just some of the reasons why Database Programmers are in high demand. A lot of thought must go into organizing the database structure to be efficient and quick. This does not mean it will be easy or simple. On the bright side, although there is a lot of work/cost to setup there should not be a lot for maintenance. There will be no shortcuts when adding new Products and they must be added properly.


On a side note, why is it that your Header has Category links on top of your Logo?

Template layout is always a main concern and you might want to consider widening yours. The page for the CW500 Roller Deck Scale for example, breaks the Template when viewed in IE6 but not FF. There could be other pages breaking as well but I only looked at a few pages.


I know this is more than you bargained for when you asked your original question, so I hope you don't mind the additional information.

[MachaNeko]

Approach every such problem by analyzing it at its most fundamental level.

Attributes for your products are not standardized across all products.
The set of capacity ranges differs for every model scale.

Either
1) you create a product for every set of attributes and do not define attributes.
2) you create an elaborate and large set of attributes and fewer products.

Sit with a pencil and paper, choose a product and write down the variables. Then try to organize them using different approaches and see what makes the best sense for you.

In the example we used above the model number differs within the same product so it becomes a function of the attributes that are chosen. I believe every product model# should be a product unto itself. This is the only way to avoid losing your mind.

no. not only is that too much work but it will not help with my problem. i found a much better solution anyways.