General - Product item Grouping (see comment)
Opened this issue · 6 comments
The ability to group items by item type and generate dashboard reports grouping like items. I think this can be done using the "serial code" field and all we would need to do is use this for a dashboard categorization. Specific items here would be to change the name of the serial code field to something like “Type” or “Group”, but serial code may be used for something else, so this needs to be discussed. Then we need to create dashboard that generated reports that total up these grouping
Requested by MMCH
Oh and let's add the grouping on the right.
SKU is is the current "itemid"
Short Name is the current "serial string"
Box ID is the current "leadingchar"
Adding a new field for Group, how about "group"?
Need to go through and mod the database to break up the current itemid string into the new itemid (SKU) and the new short name (serial string).
Need to add group names to the items. (Maybe customer can do this)
Need to do dashboards so we can show groups in the executive summary
HOLD ON .... I am remembering why it is not so simple to just break up the SKU and the Short Name. There are lots of drop down selectors all over the place where you select a product. If just the SKU is the itemid then only the SKU will be listed and unless people know the SKU they will not know what the product is. This is the original reason that I encouraged people to adopt the naming convention standard. So, I guess a question is can we easily change the contents of the drop down selectors? If not, we need to think about this some more. (edited)
OK, here are a few options. 1. Seperate the SKU and Short Name as described and then modify the product drop down selectors so that we create a list where we concatenate the itemid and the serialstring. 2. Keep with the current itemid format convention of "SKU - Short Name" but build it from the form as modified. That is use the form illustrated above, but when we save the product concatentate the two form fields with a dash inbetween. Of course this means you need to parse the itemid when you populate the form, but you don't need to do so for the dropdowns. 3. Just leave it the way it is. If 3 then we can use serialstring for the group, and we don't need to make a new database field.
Just noticed that there is another free field in the items that is not used imageurl_extra. if we wanted to just grab this instead of making a new group field.
I think this is done.... needs testing