Catalog view for visualization and management if resources.
This class will be rather heavy on documentation, because it central (literally) to the uDig applicaiton, and because it is one of the first views we are creating.
Of Note:
- The catalog is strange in that there is only *one*, represent a global registry of all the data sources in use by any uDig plugins.
-
From the requirements document (where CatalogView is known as LocalCatalog):
The Local Catalog serves as a central repository of data and server information. Non-Functional Requirements:
- Ease of Data Location , intent is for the user to be separated from the data source; so they need as little technical knowledge as possible.
- Security , name/password should be left out of the export/share.
Functional Requirements:
- Servers , store server connection information for sharing between projects.
- Data Directories , store data directories for sharing between projects.
- Metadata , provide access to metadata on Servers/Data Directories.
- Data Discovery , provide enough information for a user to define a new layer in their context.
- Persist Settings , permit exporting and sharing DataStore connection information.
- DataStores Management , lookup actualized DataStores that are in use.
- Missing Data , entries referred to by imported projects should be maintained, allowing the user one location to correct data connection information.
Catalog View has a strong interaction with the preferences maintained by the local installation of uDig for the current user.