[Pugged] Related Resources
Chris Hettinger
ciapug@ciapug.org
Fri, 28 Mar 2003 13:47:58 -0600
Does a bit, but I am concerned about the interface for linking the =
articles... How would you go about selecting the links for each of the =
entries? I don't want to have to select individually what articles this =
new one is then related to... From the user stand point, how would this =
work on the front end.
-----Original Message-----
From: David Champion [mailto:dave@visionary.com]
Sent: Friday, March 28, 2003 1:42 PM
To: ciapug@ciapug.org
Subject: Re: [Pugged] Related Resources
I'd put the resource links into a sub table (like I think Chris has seen =
me do for categories). So you have a lookup table, a "link" table with=20
the article id and a link id, and the article table.
That way you can have as many links per article as you want, and don't=20
have to mess with parsing the comma separated list or anything.
Does that make sense?
-dc
Chris Hettinger wrote:
> Hello PHPers...
> =20
> I would like some input on a project that I am just starting. I would=20
> like feedback telling me if I am on the best path for this scenario, =
and=20
> if not recommendations are welcomed.
> =20
> The project in summary... I have a database table containing articles=20
> (title, article, keywords...). On the viewing end, when an article is=20
> viewed on the web site I have a area designated for "Related =
Resources."
> =20
> The path that occurred to me to create this list of related resources=20
> was to include a field for each article that contained a comma =
separated=20
> list of keywords. When the page is requested a process would select =
the=20
> article they are viewing, then when I create the related resources=20
> listing I would take the value of the keywords list from the selected=20
> article, and have to do a comparison to the keywords listing for all =
of=20
> the other articles. Where a keyword matched, I would then include that =
> article as a related resource.
> =20
> So am I considering the best method for doing this? This seems like it =
> could become a very inefficient query as my db table grows.
> =20
> Thanks for any input.
> =20
> -Chris Hettinger
_______________________________________________
Ciapug mailing list
Ciapug@ciapug.org
http://cialug.org/mailman/listinfo/ciapug
=20
The information in this e-mail is the property of Employee and Family =
Resources. It is considered confidential, may be legally privileged, =
and is intended only for the addressee. If you are not an addressee, =
you are not authorized to read, copy or use the e-mail or any =
attachment. If you have received this e-mail in error, please notify =
the sender by return e-mail and then destroy the e-mail.
=20
=20