[seek-dev] kepler quicksearch

[Bertram Ludaescher]

One other concern regarding this solution: I fear that this will be
hardwired in the code, right? 

I think a better solution would be to declare, e.g., via a set of views,
which fields are being queried.

That one the code wouldn't have to be changed when one decides to turn
on/off certain fields for search. In fact, the user could specify which
parts are to be searched..

We could have a user-definable search option (where to search) and a
full-text index...

Bertram

On Fri, 16 Sep 2005, Jing Tao wrote:

> Hi, matt:
> 
> I will do it.
> 
> Thanks,
> 
> Jing
> 
> Jing Tao
> National Center for Ecological
> Analysis and Synthesis (NCEAS)
> 735 State St. Suite 204
> Santa Barbara, CA 93101
> 
> On Fri, 16 Sep 2005, Matt Jones wrote:
> 
> > Date: Fri, 16 Sep 2005 15:47:52 -0800
> > From: Matt Jones <jones at nceas.ucsb.edu>
> > To: Jing Tao <tao at nceas.ucsb.edu>
> > Cc: seek-dev <seek-dev at ecoinformatics.org>
> > Subject: kepler quicksearch
> > 
> > Jing,
> >
> > Could you modify the current QuickSearch in Kepler against EML and make sure 
> > that it is searching the taxonomic fields, mainly "taxonRankValue", along 
> > with the other title/abstract/keywords/creator fields?  That way, when 
> > someone searches for a scientific name in Kepler they should get results back 
> > from both EML and DarwinCore.  Thanks.
> >
> > Matt
> >
> >
> >
> _______________________________________________
> Seek-dev mailing list
> Seek-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/seek-dev
>