Embedded Files
The primary database objects, describing the major elements of the data within the repository, are represented as catalog items within the data base. The primary objects of the database are:
- Catalog Hierarchy: The (directory) structure of the repository
- · Contact Data
- o Person: These are researchers connected or contributing to the repository
- o Organization: Organization associated with data in the repository
- · Device and Component Data
- o Instrument: The instrument producing the data
- o Subsystem: Instruments and devices are viewed as collections of subsystems
- o Components: sensors, valves, baths, pistons, rotors, nozzles, etc.
- · Specification/Interpretation Knowledge base
- o Protocol: Set of observations associated with a methodology protocol
- o Observation Correspondences: Correspondence between an observation and the source data parameters.
- o Observation Specification: A specification of an observation consisting of several parameters include the type of parameter and its units
- o Block Definition: Isolation specification of a block of data within a source.
- · Observations
- o Single Database Observation: The result of interpretation of a source into a set of data parameters connected to the knowledge base.
- o Isolated Matrix Object: A matrix of data (associated with a data specification)
- o Full Matrix Object: A matrix of data (typically from the original source)
All the catalog items, specifications and source data is organized with a hierarchy, much like a file structure, represented by the Catalog Hierarchy. This hierarchy organizes blocks of data that are considered to be the same, for example a set of devices or a set of experimental measurements. In addition, within a block, data types are collected together for reference. For example, within a given block it is often useful only to access those type of items, for example specifications, that are needed.
In preparation for reading in a typical set of data, a Protocol is selected (catalog data types are bold face). A protocol mainly specifies which data (observations) should be in the data source(s). For example, the standard reporting for ignition delay times from a rapid compression machine, RCMPublishedResults (knowledge base entities are italics), lists a set of expected observations, the fuel composition (MoleFractionComposition) and a set of parameters about the pressure and temperature (experimental and compression) of the run and the ignition delay time with uncertainty (RCMPublishedResults).
Within the Protocol, these are links to Observation Correspondences, giving the correspondence between the parameters in the source data, for example the link between the column of a matrix and a particular parameter. Each Observation Correspondence links the set of parameters in the source to an Observation Specification.
Each Observation Correspondence links the set of parameters in the source to an Observation Specification. The Observation Specification has the type and unit information about each parameter. For example, in the expected observations from a rapid compression machine (RCMPublishedResults) the ignition delay time parameter type (IgnitionDelayTime) is specified. This ignition delay time specification from the knowledge base specifies that the units are of the class time (TimeParameter).
The Observation Correspondence also links to a specific Block Definition which specifies how the block of data is to be isolated from the source data from a Full Matrix Object. The result of the isolation is a Isolated Matrix Object.
Google Sites
Report abuse