Basic Notes
ODM Site Catalog is feature based. Sites, and datasets are now features. Data is associated with a feature.
Logic for populating the catalog
Preflight checks
- Responsible Party Information
- Public or private data
- Information Type (Site, Raster, etc)
- Information about the observed variables
Database Population Summary
Base Information
- If new DataService, populate ODCore_ResponsibleParty
- Add record to ODCore_UpdateLogs
Location Information
Sites, and datasets are now features. You should load a single FeatureType at a time.
- Populate ODCore_Feature
- Get Site Information
- From web service GetSites
- Or from shapefile/database if dataset is large
- Fillet site information into core information, and featureProperties
- Add core site information, and feature properties
- Add record to ODCore_UpdateLogs
Observation Series Information
Catalog is Series based. You add data to a series. Before a series is created, variables and sites must be added.
Present thought rather then rely on a list of variables, harvest the catalog, and add the variables, and series at the same time. This way only used variables exist in the database.
- Add ODCollections_SeriesSet
- Is this public or private data
- Get Series from source
- extract site, variable, and method
- if site does not exist, reject
- If variable does not exist, then populate ODCore_ObservedVariable
- Fillet into
- variableCode, variableName,Observed medium, speciation
- If method does not exist, then populate ODCore_Method
- Fillet into
- variableCode, variableName,Observed medium, speciation
- Determine Series Characteristics
- What is the ObservationType
- Manage SeriesSet
- for each added series, add to ODCollections_ObservationGroup
Meaty Data Goodness
This is the site catalog. No meaty goodness needed. As noted above, catalog is Series based. You add data to a series. A Series must exist before you add data.
Steps
ODCore_UpdateLogs
populate ODCore_ResponsibleParty
===