[kepler-dev] Q: What's proper functionality in Digir Quick Search aggregation.
jones at nceas.ucsb.edu
Tue Nov 22 08:49:42 PST 2005
That's wrong. It should only return those that equal Mephitis macroura.
Also, it would be much better if the second query were only a local
subsetting of the results that have already been returned, rather than
requerying the DiGIR providers.
As Rob Gales and Aimee Stewart finish up work on the Taxonomic Object
Server and the associated Kepler actors to access it, we can expect the
way in which these DiGIR queries are conducted to change significantly.
You might want to talk this over with Rob -- I'd like to get his
actors incorporated as soon as is feasible so that we can deal with the
name/concept mismatch more effectively.
Kevin Ruland wrote:
> When I do a Quick Search from the Ecogrid Digir service for the term
> 'mephitis', the quick search where clause is "Scientific name LIKE
> mephitis". The results are aggregated by Scientific Name and there are
> different little folders for each Scientific Name. The first few on my
> screen are:
> mephitis macroura
> mephitis macroura macroura
> mephitis macroura milleri
> Now, if I drag, say "mephitis macroura" onto the canvas, a dataset is
> created. The way it works now is it requeries using the where clause
> "Scientific Name LIKE mephitis macroura". This means that the resulting
> dataset includes all the results which match the following: "mephitis
> macroura", "mephitis macroura macroura", and "mephitis macroura milleri".
> Is this what is expceted? Or does the user expect the folder to contain
> only those records which EQUAL "mephitis macroura"?
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
jones at nceas.ucsb.edu Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara http://www.nceas.ucsb.edu/ecoinformatics
More information about the Kepler-dev