HIS Desktop Conceptual Design
(With contributions from Tim Whiteaker, Dan Ames, Jon Goodall, and Jeff Horsburgh)
This page documents the current conceptual design and design principles for HIS Desktop.
The following is an conceptual image of how HIS Desktop will fit in with the larger CUAHSI HIS.
The following design principles guide the development of the HIS Desktop application.
- HIS Desktop will emphasize user functionality to enable users to take advantage of HIS data and service oriented architecture capability.
- HIS Desktop will be a well documented and structured example for how a similar project could be built for other platforms. Additionally, to the extent possible, the code will be Mono compatible and cross database compatible.
- HIS Desktop will have a local data repository where data retrieved from WaterOneFlow web services via GetValues calls will be cached. Only data associated with time series values in the database will be stored. In other words, regardless of how many sites were returned during a data search, only sites for which time series were actually retrieved will be stored in the database.
- HIS Desktop will have a GIS enabled Graphical User Interface that supports development of plugins that will contain specific sets of HIS Desktop functionality.
- HIS Desktop will support multiple different Relational Database Management Systems (RDBMS) - SQL Server, MySQL.
- HIS Desktop will perform data discovery by accessing metadata and ontology web services housed at HIS Central (SDSC).
- HIS Desktop will have the capability to do data discovery on a published web service that is not registered with HIS Central.
- HIS Desktop will have the ability to organize data into a "project." A project will be all of the GIS data, its symbology, a database of observational data, and all loaded plug-ins and configuration settings.
- HIS Desktop will provide an interface for selecting and downloading specific online spatial datasets (NED, NLCD, NHD, etc.).
- HIS Desktop will discover data and retrieve ontology concepts using HIS Central web services, but it will retrieve data by formulating web service calls to the data source (i.e., the existence of the data comes from HIS Central, but the data and metadata populating the HIS Desktop database comes from the data source).
- HIS Desktop will store a local version of the ontology that can be updated from the HIS Central web services.
- HIS Desktop will have the capability to "package" a project so that it can be transferred from one machine to another. The packaging could just include the instructions on how to rebuild the package from HIS Central and data servers.