Represents a uniquely identified presentation of a defined collection of information. The presentation consists of a particular subset of the collection. A DataProduct may have a real-time stream and may have persisted historic data.
Refer to the CIAD APP Resource Model page for metadata definitions.
|Responsible Service||Data Product Management Service|
|Architecture References||CIAD SA OV Data Product Generation
CIAD OV Resource and Object Model (needs update)
CIAD OV Data Flows (needs update)
|Other References||Object Spec for DatumCharacterization
Object Spec for DataRecordFormat
|Comments||The attributes necessary to produce the many formats of Data Product. Persistence is NOT implied.|
|Open Issues/Changes||Exact relationship of Data Product to Data Set. Many issues have been addressed on Discussion page.|
To be a data product in OOI, the entity must (a) have a unique identifier by which it is referenced, (b) be a subset of a well-defined collection of information. (It may be either an improper subset — that is, the entire well-defined collection – or a proper subset.)
The data product contains sufficient metadata or references to metadata to unambiguously describe its content and provenance. An extensible set of formats will be available to the user to request the information in the particular byte order and organization that suits them; the format specification does not change the identity of the data product.
An Invariant Data Product is a temporally invariant data product. Requesting the data corresponding to the Invariant Data Product URL will produce the same exact data for the life of the system. (Any data or annotations that become known to the system after the Invariant Data Product URL's time mark will not be included in a representation of the data.)
A Core Data Product is a data product that comes from an OOI owned instrument, including L0 and the derivative L1 and L2 data products that OOI has defined and described and which will be produced and managed with OOI expertise. (The OOI team often refers to this simply as a 'Data Product', and the listener must infer the appropriate meaning.)
Note that the attributes that are stored for the Data Product must be converted into different formats according to different standards. For example, ISO 19115 metadata call for particular attribute names and forms; netCDF CF conventions call for specific attributes within the netCDF form; and ACDD conventions call for additional specific attributes to be provided. The attributes specified here were derived as a common set of information that could be extracted into these different forms, even as they are also useful at a more detailed level internally. (Generating core ISO 19115 metadata for data products is required in Release 2, with more comprehensive ISO 19115 compatibility required for Release 3. netCDF CF is required in Release 2 and beyond; netCDF ACDD conventions are desirable.)
References in this section point to the material that describes attributes of the resource, if any.
- NetCDF ACDD