[ic] One SKU in multiple Branches of TREE

[Ed LaFrance]

At 01:06 PM 01/11/2002 -0700, you wrote:
>Ed,
>
>Thanks for the reply. So are you suggesting this implementation for TREE 
>as well, or just in reference to Multiple Categories. It seems like a 
>delimited field with multiple tree-branch paths could get quite ugly very 
>quickly. However, I may not be seeing the light at the end of the tunnel 
>on this either. I would think just for a normalization factor that it 
>would be best in a separate table, but again I am not a DBA or Perl 
>programer by trade. Just a newbie trying expand my skill set and understanding.
>
>Thanks in advance,
>Gary
>

I was making a general observation. In all the things I have done with MV 
and IC, I have never knowingly used the TREE tag, so I have to stay mute on 
how my comments would fit into that context.

- Ed L.




> >>> edl@newmediaems.com 01/11/02 10:58AM >>>
>At 07:57 PM 01/10/2002 -0700, you wrote:
> >In searching the archives of the list I didn't see this addressed
> >specifically, but I did find mention of one SKU in multiple categories.
> >Basically the thread mentioned creating a separate table that listed only
> >sku and category (that is an abbreviated explanation of course).
> >
> >I am not sure if it is possible (usually it is if you are smart enough,
> >unfortunatly on this subject I am not) to do the same thing to support a
> >single SKU in multiple branches of a tree.
> >
> >Example: Auto-parts store sells items that are usually selected by auto
> >make and year:
> >
> >Shocks=>Ford=>Bronco=>77-79=>SKU
> >
> >However many SKU's can be used across multiple branches using the previous
> >logic (ie 81-83 etc.)
> >
> >If this is possible, what do you think the best implementation is. I had
> >thought about a 3rd table implementation as listed for the single sku in
> >multiple categories thread, but wasn't sure what would need to be tweaked
> >to support the TREE structure.
> >
> >I had a few ideas, but basically my brain-train got derailed when I tried
> >to figure out how I was going to support SEARCHING and other features etc...
> >
> >FYI, I am testing this implementation on a generic install of
> >"Construct"  with the integration of the HOW TO for TREES.
> >
> >Thanks in advance,
> >Gary
>
>Fields like category, which are used to classify and group items, need not
>contain just one value - you could theoretically make one sku a member of
>as many categories as you want, by filling the category field with a list
>of delimited values.  This will require changes in the UI as well as in
>front-end code, but it is quite doable - I have done so many times.  It's
>just not implemented in the foundation demo, AFAIK.
>
>- Ed L.
>
>
>
>
>
>
>===============================================================
>New Media E.M.S.               Software Solutions for Business
>463 Main St., Suite D          eCommerce | Consulting | Hosting
>Placerville, CA  95667         edl@newmediaems.com
>(530) 
>622-9421 
><http://www.newmediaems.com/>http://www.newmediaems.com
>(866) 519-4680 Toll-Free       (530) 622-9426 Fax
>===============================================================
>
>_______________________________________________
>interchange-users mailing list
>interchange-users@interchange.redhat.com
><http://interchange.redhat.com/mailman/listinfo/interchange-users>http://interchange.redhat.com/mailman/listinfo/interchange-users

===============================================================
New Media E.M.S.               Software Solutions for Business
463 Main St., Suite D          eCommerce | Consulting | Hosting
Placerville, CA  95667         edl@newmediaems.com
(530) 622-9421                 http://www.newmediaems.com
(866) 519-4680 Toll-Free       (530) 622-9426 Fax
===============================================================