On Tue, Sep 23, 2003 at 05:32:57PM +0100, Kate L Pugh wrote:
OpenGuides 0.25 (just released).
<ivorw> Or, how about: locale=west end&category=pubs
00:30 <hex> King's Head locale:"West End" category:Pubs
I'm not always clear, reading this conversation, on whether the thing
being discussed at any one time is the thing that the user types into
the search box, or the query string that will appear in the URL, or
the API of OpenGuides::SuperSearch, or what.
We were talking about what the user would be typing into the search box at
<ivorw> e.g. king's head&post_code=~W3
Would anyone actually use this, practically speaking? Perhaps a fuzzy
match would be more useful.
I would think it might, yes. Regexen are very specific; I don't think I'd
have much use for them.
In general, I really don't want to have to
remember yet another syntax
for writing search queries. How about we have an "advanced search" page
I've been wanting this for quite a while. However, your point about yet
another syntax is why I mentioned Google style in the conversation - Google
lets you do advanced queries from the generic box, but gives you an advanced
search page as well. I'd like this format for search terms (where metadata1
and metadata2 are two arbitrary metadata types like locale and category):
term1 [metadata1]:term2 [metadata2]:"term3 term4"
This would search for a node with the word term1, and the word term2 in its
metadata1 and the phrase "term3 term4" in its metadata2. A less generic
fish category:Restaurants locale:"West London"
So that would search for a restaurant in West London that mentions the word
"fish". Very straightforward, I think. However, since the new OG release
"searches for your terms not only in the titles and bodies of the nodes, but
also in the locales and categories", I guess that makes this redundant.
# Earle Martin http://c2.com/cgi/wiki?EarleMartin