[ic] One SKU in multiple Branches of TREE
Sat Jan 12 16:57:00 2002
Content-Type: text/plain; charset=US-ASCII
<cut and paste relevant part to comment on>
could just as well be
Hmm. Interesting point on the latter item leading with SKU as a Trunk item =
rather than a Leaf. I hadn't even considered that. I need to think about =
it a bit more, it sounds promising, but then I am stuck with a way to =
build Reverse Expand/Collapse tree as the user would not want their =
initial interface to start with the SKU, but rather the most generic =
Ugh. My head hurts.
Perhaps I am addressing the problem all wrong. Rather than assuming that =
TREE is what I need, does anyone else have suggestions in implementing a =
hierarchal product structure that a user can browse through?
>>> email@example.com 01/11/02 02:32PM >>>
On Fri, Jan 11, 2002 at 12:22:31PM -0800, Ed LaFrance wrote:
> At 01:06 PM 01/11/2002 -0700, you wrote:
> >Thanks for the reply. So are you suggesting this implementation for =
> >as well, or just in reference to Multiple Categories. It seems like =
> >delimited field with multiple tree-branch paths could get quite ugly =
> >quickly. However, I may not be seeing the light at the end of the =
> >on this either. I would think just for a normalization factor that =
> >would be best in a separate table, but again I am not a DBA or Perl=20
> >programer by trade. Just a newbie trying expand my skill set and=20
> >Thanks in advance,
> I was making a general observation. In all the things I have done with =
> and IC, I have never knowingly used the TREE tag, so I have to stay mute =
> how my comments would fit into that context.
> - Ed L.
I fall into the "single field gets ugly very fast" camp. If you suspect
that is likely to be an issue, then it probably will be a big issue. :-)
could just as well be
> >>>> firstname.lastname@example.org 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 =
> >>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 =
> >>unfortunatly on this subject I am not) to do the same thing to support =
> >>single SKU in multiple branches of a tree.
> >>Example: Auto-parts store sells items that are usually selected by =
> >>make and year:
> >>However many SKU's can be used across multiple branches using the =
> >>logic (ie 81-83 etc.)
> >>If this is possible, what do you think the best implementation is. I =
> >>thought about a 3rd table implementation as listed for the single sku =
> >>multiple categories thread, but wasn't sure what would need to be =
> >>to support the TREE structure.
> >>I had a few ideas, but basically my brain-train got derailed when I =
> >>to figure out how I was going to support SEARCHING and other =
> >>FYI, I am testing this implementation on a generic install of
> >>"Construct" with the integration of the HOW TO for TREES.
> >>Thanks in advance,
> >Fields like category, which are used to classify and group items, need =
> >contain just one value - you could theoretically make one sku a member =
> >as many categories as you want, by filling the category field with a =
> >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. =
> >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 email@example.com=20
> >(866) 519-4680 Toll-Free (530) 622-9426 Fax
> >interchange-users mailing list
> New Media E.M.S. Software Solutions for Business
> 463 Main St., Suite D eCommerce | Consulting | Hosting
> Placerville, CA 95667 firstname.lastname@example.org=20
> (530) 622-9421 http://www.newmediaems.com=20
> (866) 519-4680 Toll-Free (530) 622-9426 Fax
> interchange-users mailing list
Christopher F. Miller, Publisher email@example.com=
MaineStreet Communications, Inc 208 Portland Road, Gray, ME =
Content/site management, online commerce, internet integration, Debian =
interchange-users mailing list
Content-Disposition: attachment; filename="Gary Norton.vcf"