Refactor Metadata Fetching/Caching

danames[CodePlex]
Instead of entering a direct WSDL for a single server and downloading metadata and then searching the metadata to download data let's reduce the steps significantly.

Let's try it this way:

1) add a new button to the Data Source group on the search tab called quotAdd Sites Layerquot

2) When user pushes this button, show a dialog box that requests the WSDL server connection URL string

3) Entering the string and clicking quotNextquot prsents a list of all variables on that server

4) User checks boxes next to variables and clicks Get Sites

5) A new sites (search results) layer is created for each variable on that server

--- all of the meta data is loaded into the regular HydroDesktop search results database.

--- we can now get rid of the idea of a quotlocal metadata cachequot and it's associated database.

--- user can simply click on the points on the map to download data just like with any other search results layer.

Review the existing WSDL metadata fetching flow, the local metadata cache and its database, and the regular search-results database. Trace how metadata becomes map layers and how users download data from search results. Done means the Add Sites Layer workflow creates a sites layer for each selected variable and no longer depends on the local metadata cache.

Written by the indexing model from the issue text.