This may turn out to be a complex questions so please bear with me!
I have uploaded Price Tapestry to a server and uploaded a sample of 20 feeds. Feeds are for companies A, B, C, D, E, .....
At the moment, a user comes on and searches for product XYZ. XYZ is a make of fridge but is also the title of a DVD.
The user has to fight his/her way through all the DVD's before they get to the fridge.
Naturally, if it isn't in the first 1 to 5 results, the user will go somewhere else.
What I would like to do is create sub-sections. For instance, http://www.myname.com/dvd-search.php or http://www.myname.com/fridge-search.php. The user then has the option on the main screen of searching the entire list of feeds or just for DVD's or fridges.
Taking fridge-search.php, there would need to be a way of selecting feeds ONLY from seller A and D. dvd-search.php would be sellers B, C and E.
I think it is only a case of copying the search php pages, renaming them to whatever, and editing the mysql code to select records from sellers listed in the code of the search php page. I just need confirmation that this is it plus a snippet of edited mysql code to enable this, if I am correct!
The ultimate aim of this is to create dedicated search sections for my users so that if you are looking for a book, you won't need to trawl through CDs and DVDs.
As a second question, is it possible to extend this and only search for items in a grouped category (e.g. anything paired to the category book in Price tapestry)?
Hi,
Something a number of Price Tapestry users do is to create several "sub-sites" installed into sub-directories; where each sub-directory contains a separate installation of Price Tapestry containing merchants in a particular "master" category, such as Electronics or Music and Video. The following thread shows you how to create a "master" search box for each of the categories:
http://www.pricetapestry.com/node/205
Does that sound like it might be a possible option? What you've described in your post shouldn't be too difficult however; there is just the usual caveat of restricting search against a non-indexed field - there are performance issues to consider...
Cheers,
David.