Eric J Altman wrote:
> Jonas Maurus wrote:
> >
> [snip]
> >
> > You're welcome. Wait until we have done the other modifications (feedback and
> > searching) :-).
> >
>
> Hello Jonas,
>
> Thanks for contributing this localization code to the project. I see
> you have some other stuff in the pipeline as well which is great!
>
> Would you be interested in sharing your ideas for searching in
> jyve/turbine? Unlike localization, I would like to contribute something
> here if I can be of help to you, whether a feature spec, a few lines of
> code,
> or just user-land feedback.
>
> Don't know how far along your team is, but I just had some questions:
>
We've not started to develop any code for the search-functionality, yet.
>
> 1.Did you take Jon *'s suggestion from a while back and think about
> using OPaL for this functionality and/or making a more generic search
> service as part of Turbine?
>
I would take Jon's side and prefer a TurbineService.
>
> 2.If it's a jyve specific implementation, are you replacing the
> SearchGlobal / SearchResults screens with
> something else entirely, or just tweaking what's there?
>
Nope, see above :-).
>
> 3.If the latter: conceptually, is parsing a search query string an
> action, or part of a screen? Ie, should you put search string parsing
> routines into an action module, pass the query string in as a parameter
> from SearchGlobal, then access the parsed string from SearchResults with
> a data.user.getTemp("search") kinda thing?
>
> 4. How do you localize a search? Is it reasonable to force non-english
> speakers to use and/or/not within a query?
>
Probably not. I don't know of any Searchengine which is localized. Most use a quite
sophisticated and easy boolean grammer (and/or/not) and/or the equivalent signs (is it
being called "signs"
?) +/-/! ans so on. Localization is not an issue there.
For us, providing a search-possibility has always included creating an "advanced
search"-screen, where the user can select the boolean configuration of his search with
his mouse.
>
> In the interest of shut-up-already-and-post-code, I spent my lunch hour
> today and worked up a little something to help me find out what's
> already in there and where it could go. I attached my draft below -
> it's a mess and not ready for prime time, so I didn't bother doing a
> premature diff (let me know if that would help, though). The objective
> was:
>
> 1. Do something minimalist to elicit commentary.
> 2. Work with the existing code before suggesting we throw it out and
> start over.
> 3. Use my admittedly "script kiddie" level abilties to implement a
> simple boolean search.
>
> So I tacked on some code to SearchResults.java to support AND and OR
> with multiple search terms.
> I'd like to get back the ability to search on a long multi word string
> without having it be "or"'d, however, so I guess parsing for ""'s to
> signify a quoted string is next. Then maybe parse for ![NOT]. Perhaps
> same time tommorrow. ;)
>
> Criticism/discussion welcome, or just tell me to go away... ;)
>
>
I never even thought of the possibility that someone would come up with suggestions
and you can bet I don't dared to dream of somebody who would actually code something
:-).
I currently have no time to take a look at it, but I promise that I do asap.
For now, our next step will be to implement the feedback/voting feature. This will
probably happen next week.
Searching is currently not one of our top-priorities as there is preliminary code
already in place.
If you continue to work on this (ideas/code), please keep me up to date.
Yours sincerly,
-Jonas Maurus
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
