| Previous · Next | |
| User | Message |
|
martink
|
Date: 11/13/2007 2:06 pm · Subject: Adding forced keywords to the search asset · Rating: 8
Hi all,I've been extending the Search asset with a field (in the edit screen) called required keywords. The idea is that when someone enters a search query those required keywords are added to it before it is passed to the WG::Search engine. It's a bit of a pity that the actual search isn't put in a seperate method, but that's no biggie. Anyway, after I made this I thought it might be something to add to the search asset in the core. So what is this good for? It makes it possible to search through specific posts only, for one. You could for instance use a userDefined field to 'tag' posts with an identifier, and use the required keywords field to limit the search to only those posts. Not only within one cs but also trough all such assets within an entire branch. Maybe there are more uses, I dunno. Any thoughts? Martin |
| Back to Top |
Rate [ | ]
|
|
knowmad
|
Date: 11/13/2007 4:26 pm · Subject: Re: Adding forced keywords to the search asset · Rating: 11
Martin,Interesting idea. It seems like it's doing about the same as a form post to a SQL Report asset. What benefits are you getting by using a Search asset? William -- Knowmad Technologies W: http://www.knowmad.com P: 704.343.9330 |
| Back to Top |
Rate [ | ]
|
|
martink
|
Date: 11/14/2007 11:45 am · Subject: Re: Adding forced keywords to the search asset · Rating: 1
The search asset uses the the webgui search engine, SQL reports do not. BTW, stating this is the same as an SQL Report with a form post is about the same as saying that the current Search wobject has no reason to exist... Martin william@knowmad.com wrote: > knowmad wrote: > > Martin, > > Interesting idea. It seems like it's doing about the same as a form post > to a SQL Report asset. What benefits are you getting by using a Search > asset? > > > William > > -- > Knowmad Technologies > W: http://www.knowmad.com > P: 704.343.9330 > > > http://www.plainblack.com/webgui/dev/discuss/adding-forced-keywords-to-the-search-asset/1 > > ------------------------------------------------------------------------ > > > > |
| Back to Top |
Rate [ | ]
|
|
knowmad
|
Date: 11/14/2007 1:30 pm · Subject: Re: Adding forced keywords to the search asset · Rating: 13
On Wed, Nov 14, 2007 at 11:45:19AM -0600, martin@oqapi.nl wrote:> The search asset uses the the webgui search engine, SQL reports do > not. BTW, stating this is the same as an SQL Report with a form > post is about the same as saying that the current Search wobject > has no reason to exist... Now that you mention it.... Seriously, the WebGUI search engine is nothing more than a pretty front for MySQL search. Putting up a form that returns a custom SQL Report would appear to offer the same thing though not be as well indexed. Sure, it would take a long time to run on a large website. However, your example was searching for certain "tagged" entries in a CS. An SQL Form with posted formdata could do the same thing. This is Perl after all--long live TIMTOWTDI! Cheers, William -- Knowmad Technologies W: http://www.knowmad.com P: 704.343.9330 |
| Back to Top |
Rate [ | ]
|
|
martink
|
Date: 11/15/2007 10:15 am · Subject: Re: Adding forced keywords to the search asset · Rating: 1
william@knowmad.com wrote:> knowmad wrote: > > Now that you mention it.... Seriously, the WebGUI search engine is > nothing more than a pretty front for MySQL search. Putting up a form > that returns a custom SQL Report would appear to offer the same thing > though not be as well indexed. Except that using an SQL Report will bypass the api and does not protect you from db schema changes. Something the Search asset does. Besides, I want something flexible and easy to use =) > Sure, it would take a long time to run on a large website. However, your > example was searching for certain "tagged" entries in a CS. An SQL Form > with posted formdata could do the same thing. This is Perl after > all--long live TIMTOWTDI! I propose the acronym TAEMWYDWTDI (try to pronounce _that_), which obviuosly stands for 'There Are Even More Ways You Don't Want To Do It'. Using a SQL Form combined with an SQL Report to subsitute something that already works, is not my idea of fun =) Martin |
| Back to Top |
Rate [ | ]
|
|
JT
|
Date: 11/15/2007 10:00 am · Subject: Re: Adding forced keywords to the search asset · Rating: -21
I can't see this being highly useful. It's one thing for you to shove stuff into the search index, it's another to modify the search interface to support your hack. I'd need to see further evidence that this is both useful and not detrimental before allowing such a thing into the core. |
| Back to Top |
Rate [ | ]
|
