No problem with that. I totally agree case sensitivity during searches is a usability issue, and I have an open JIRA on that. Dealing with the "applyTag" behavior will definitely help. Only drawback is that it doesn't address all the case-sensitivity issues we have - e.g. searching for usernames, titles, and descriptions also needs to be done case-insensitively. That work I imagine still needs to happen in the UI.
Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Glen Daniels > Sent: Thursday, September 18, 2008 12:12 PM > To: [EMAIL PROTECTED]; mashup-dev > Subject: [Mashup-dev] Tags and case-sensitivity > > Hey Registry folk and Mashup folk: > > I am about to make a significant change (a fix, I think) to the way > tags > work and wanted to run it past people. Right now tags are case > sensitive. If I applyTag(r, "foo") and then applyTag(r, "Foo"), there > will be *two* separate tags on the resource. We also are case- > sensitive > when searching, so looking for "foo" will NOT currently find "FOO" or > "Foo". > > I believe this is a serious usability problem, and am in the midst of > fixing this to work as follows - the *first* time a tag is applied, it > will maintain case, but searches will still find it even if they > specify > a different case. Future taggings which differ only in case will > simply > up the counter on the existing tag. > > applyTag(r, "Foo") // now there's one tag "Foo" > // Any time after here a search for "foo" with any case will succeed > applyTag(r, "FOO") // still only one tag "Foo", but two taggings. > > Any issues with this? > > Thanks, > --Glen > > _______________________________________________ > Mashup-dev mailing list > [email protected] > http://mailman.wso2.org/cgi-bin/mailman/listinfo/mashup-dev _______________________________________________ Mashup-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
