Evaluate: Simple Query (rewrite views for query)
ML need to revise template
#4 Updated by Michael Lee over 19 years ago
simple query has been designed and needs to be 1) evaluated and probably reduced
in complexity a bit (stems are currently commented out)
The proposed form (in its built state after ant) :
The form pre-build http://tekka.nceas.ucsb.edu/~lee/forms/plot-query-prebuild.html
Gabe needs to implement the new form.
A rough guide to the fields as they are in the form and where they need to be
queried in vegbank is on
#5 Updated by Robert Peet over 19 years ago
1. Remove the soil depth criteria from the query
2. Move the NULL and NOT NULL up to the tops of the picklists immediately
3. The variables “Cover Method Name”, “Stratum method name”, “Name of
plot submitter”, “name of observation compiler”, & “project name” need either
pull down lists or better a click to find with a separate window that allows
these to be searched and the name selected or cut and pasted across. Perhaps
want to include wildcard symbol as option in the directions.
4. The same issue pertains to the community classification as in 3.
Very soon, but not for release 1.0, we need to have the query result cashed so
that a second query can be run on the results to further narrow down the set
of plots selected.
We also need to have the option to click on the selected plots and place in a
shopping cart – John was working on this and I am not sure how much of it
currently is functional.
#7 Updated by P. Anderson about 19 years ago
What is the official status of this bug today?
How does it relate to bug 712?
I have made some enhancements to the simple query. Users are now given hints
where min/max values can be entered (elev,slope,dates,area).
Along those lines, what do you think about having an option that automatically
limits some or all of the picklist values so that they are constrained to
existing data only? e.g. if there are currently no plots in the state of
Quintana Roo, don't even include Quintana Roo in the picklist.
#8 Updated by Robert Peet about 19 years ago
As Mark suggests, when viewing the picklists for construction of a query it
makes much sense to display only those values for which there are plots.
However, what is the performance cost? Do we have to redetermine which fields
to display each time, or can this be cached someplace and updated as new
fields become represented? I don't want to invest alot in this yet -- it is
down there at approximately a version 2.5 bug.
#9 Updated by Michael Lee about 19 years ago
I agree with Bob in that the simpler query (with all states) is easier to
maintain. It would be helpful, after we work on some "canned" queries, to
provide a link next to the list: click here for a list of all states with plots
and the number of plots in each. This would show the user a live list of our
current plots and where they occur.
The advantage to listing fewer states is that users are less likely to be
frustrated in that they can't find any plots.
The advantage to listing all states is that 1) easier to maintain query page and
2) we better show the schope of VegBank - where we are moving. We'd like to
have plots from Mexican and Canadian provinces, in other words, at least at some