Yes, we should handle multiple search terms, though I think AND is probably
more useful if we have to choose only one. Although we're getting pretty
complicated adding a "find all terms" checkbox to engage AND instead of OR.
Implementing multiple search terms will get a little complicated with our
static saved query mechanism, since we can't just append "OR
TAG_VALUE='{tag[n]}'" for each item. Right now the consistent approach is
to create queries of 1, 2, .. n search terms and key off the number of
search terms to find the right query. There is an upper limit to this
approach though, as we have to prepopulate the registry with queries up to
the maximum we allow (10 should be more than sufficient).
Besides splitting we need to consider normalizing tags both when searching
and adding tags. My first thought would be something like:
- case preserved when tagging, though not significant when searching.
- punctuation other than ":", ".", "_" stripped (major_loser! ->
major_loser)
- Quoted strings whitespace normalized into a single tag ("San Francisco" ->
SanFrancisco)
Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Chathura C. Ekanayake
> Sent: Monday, December 03, 2007 4:17 AM
> To: [email protected]
> Subject: Re: [mashup-dev] Tag searches
>
>
> Hi Jonathan,
>
> We used exactly the same method you have described for searching fields
> with large text content (descriptions, comments) and tags. We used SQL
> LIKE to compare descriptions, comments, etc and exact match to compare
> tags.
>
> Another concern I am having is that user can type multiple words in the
> tag search box. In that case, I consider each word as a separate tag
> and
> use OR operation to combine them. But I am not exactly sure whether we
> should use OR or AND here.
>
> Thanks,
> Chathura
>
> Jonathan Marsh wrote:
> >
> > I keep going back and forth on how tag searches should work.
> >
> > If one is searching for mashups tagged with a particular tag, an
> exact
> > match seems best. For instance if I have created a query or a feed
> > showing mashups tagged "ok", then I probably don't want mashups
> tagged
> > "broken" to appear. Right now we use exact tag matching to link tags
> > to mashups, and if I click on a tag link "ok" I really don't want
> > anything to appear that isn't tagged with the "ok" tag.
> >
> > On the other hand, when I'm searching through descriptions and
> titles,
> > I don't generally need an exact match, but just that the search
> string
> > appears somewhere in the title or description.
> >
> > Currently a custom query always match tags exactly, but descriptions
> > and titles loosely. When used in isolation these behaviors seem fine
> > but when they are combined into a single query you might occasionally
> > get some slightly strange results. For instance, searching for the
> > letter "s" in titles or descriptions returns lots of stuff, but if
> you
> > try that in tags you probably won't get anything at all even though
> > many tags contain the letter "s". Is that what you'd expect?
> >
> > On the other hand, providing two ways to search tags (exact,
> contains)
> > seems more complex than it's worth.
> >
> > I guess I'm convincing myself the current behavior is fine, and the
> > subtle difference between searching tags and searching titles and
> > descriptions probably won't be visible to an average user, but if you
> > have any thoughts to the contrary I'd love to hear them.
> >
> > *Jonathan Marsh* - http://www.wso2.com -
> > http://auburnmarshes.spaces.live.com
> >
> > ---------------------------------------------------------------------
> ---
> >
> > _______________________________________________
> > Mashup-dev mailing list
> > [email protected]
> > http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
> >
>
>
> _______________________________________________
> Mashup-dev mailing list
> [email protected]
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
