| At line 5 added 1 line. |
| + * [http://kuecogrid.ittc.ku.edu:8080/ogsa/queryForm.jsp] |
| At line 6 added 1 line. |
| + * [http://129.237.201.166:8080/ogsa/queryForm.jsp] |
| Line 41 was replaced by line 43 |
| - UI will be web browser based. Search criteria will be collected across multiple screens (wizard) with the option to execute search or move to next screen on each screen. |
| + UI will be web browser based. |
| Lines 43-71 were replaced by lines 45-51 |
| - ! UI Input Screen 1 : Sources and Keywords |
| - * __Sources__: select one or more options of registered ecogrid hosts. |
| - * __keywords__: full text search (how?) |
| - * __title__: |
| - * __name__: (one input field and parse or use two seperate fields?) |
| - * __key|value pairs__ |
| - ** input some additional key|value pairs, key possible chose from list box of common fields |
| - ** possible move this to a advanced keyword page where users can also specify more complex AND/OR combinations |
| - * __<Search Now> or <Next: More Criteria (2 Spatial, 3 Temporal)__ |
| - |
| - ! UI Input Screen 2 : Spatial |
| - * __Area__: list - "select area", "custom", and list of predefined areas |
| - ** custom will use a graphical picker or manul input |
| - * (inputs for custom) N,S,E,W (min|max lat|long) |
| - * __<Search Now> or <Next: More Criteria (3 Temporal)__ |
| - |
| - ! UI Input Screen 3 : Temporal |
| - * __date type__ : assuming there is more than date field such as collection date, publication date, etc |
| - * __startDate__ |
| - * __endDate__ |
| - * __<Search Now>__ |
| - |
| - ! UI Results Screen |
| - ... |
| - |
| - |
| - !! Application Components |
| - ! UI |
| - Web tier using Struts handles collecting user input, dispatches query to GenericQueryHub and displays results. This only knows about generic queries which use simple field names instead of xpaths which could vary according to data format (EML, Darwin, etc.). |
| + ! LTER Metadata Query mockup |
| + (early in the process, not a final design) |
| + [LTER_query_interface_mockup.png] |
| + |
| + ! Screen Capture of Work In Progress |
| + (early in the process, not a final design) |
| + [ecogrid_query_screen.png] |
| Removed lines 73-75 |
| - ! GenericQueryHub |
| - Receives a generic query from the webapp. Then for each data source selected to search, it converts the query into an ecogrid query for the appropriate data format using some xref to obtain xpaths for the simple field names. It submits and recieves results for each data source and merges them together returning a single dataset. |
| - |
| Lines 78-88 were replaced by lines 55-60 |
| - !! Related Questions |
| - ! GWSDL |
| - * I was hoping to use familiar WSDL tools with GWSDL, but this isn't possible. So what does one use for working with GWSDL? Specifically, client generation? E.g., with WSDL you can point your IDE to a URL for the WSDL on the server hosting the web service and it will generate the client code as well as let you run simple generic tests with generating a client. |
| - |
| - ! Data Formats - EML, Darwin |
| - * What all data formats are there? |
| - ** I have only see EML, Darwin, is there others? |
| - ** [EML | http://knb.ecoinformatics.org/software/eml/] |
| - ** Darwin described where? |
| - ** What fields can be assumed to be common among all data formats? |
| - *** (need to create xref of the different paths for these) |
| + !! Data Formats - EML, Darwin |
| + * [Doc for Field Mappings between search fields and EML, Darwin in CVS|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/seek/web/EcoGridWebApp/docs/FieldMappings.html] |
| + * [EML | http://knb.ecoinformatics.org/software/eml/] |
| + * [Darwin | http://digir.sourceforge.net/] |
| + |
| + ---- |
| At line 89 added 1 line. |
| + !! Misc Questions |
| Removed lines 91-92 |
| - * is there I build target that I haven't found for building just the client code? |
| - * if not, what's the minimal set of things I need from the Ecogrid project for clients? |
| Line 95 was replaced by line 66 |
| - * What about queries for counts, group by, etc |
| + * What about queries for counts, group by, etc, that might be used to generate a drill down instead of a search |
