Difference between revisions of "ISO Aggregation"

From Earth Science Information Partners (ESIP)
(New page: ==How ISO Does It== The ISO AggregateInformation object provides a powerful mechanism for grouping multiple metadata records into sets based on a number of relationships described by the A...)
 
(replaced 'DS_InitiativeTypeCode' with 'MD_initiativeTypeCode', assuming it was just a typo)
 
(4 intermediate revisions by one other user not shown)
Line 6: Line 6:
 
+ aggregateDataSetIdentifier [0..1] : MD_Identifier<br>
 
+ aggregateDataSetIdentifier [0..1] : MD_Identifier<br>
 
+ associationType : DS_AssociationTypeCode<br>
 
+ associationType : DS_AssociationTypeCode<br>
+ initiativeType [0..1] : DS_InitiativeTypeCode<br>
+
+ initiativeType [0..1] : MD_InitiativeTypeCode<br>
  
 
'''MD_InitiativeTypeCode'''<br>
 
'''MD_InitiativeTypeCode'''<br>
Line 31: Line 31:
 
+ source<br>
 
+ source<br>
 
+ stereoMate<br>
 
+ stereoMate<br>
 +
 +
==ESIP Response==
 +
*[[user:KarlBenedict|Karl Benedict]] - GIS Bounding Environmental Observations, etc., Imagery Collections
 +
*[[user:Tstevens| Tyler Stevens]] - GCMD DIF has "Parent"/"Child" relationships in metadata
 +
*[[user:Jeff.arnfield| Jeff Arnfield]] - station metadata is often hierarchical, nested, or draws on other components. Our data products or datasets often involve aggregation
 +
*James Gallagher - OPeNDAP servers (really DAP Servers in general) need to support aggregation in several ways. We have use cases, part. tiles, and time series
 +
*Xing
 +
*Ed Armstrong - Instruments > Missions > Campaigns
 +
*Henry - aggregation from daily to monthly
 +
*[[user:Rhusar|Rudy Husar]]
  
  
 
[[Category: ISO Metadata]]
 
[[Category: ISO Metadata]]

Latest revision as of 23:36, October 29, 2009

How ISO Does It

The ISO AggregateInformation object provides a powerful mechanism for grouping multiple metadata records into sets based on a number of relationships described by the AssociationType and InitiativeTypeCodes. Note that the sets are identified by MD_Identifiers which suggests that they could have metadata records of their own.

MD_AggregateInformation
+ aggregateDataSetName [0..1] : CI_Citation
+ aggregateDataSetIdentifier [0..1] : MD_Identifier
+ associationType : DS_AssociationTypeCode
+ initiativeType [0..1] : MD_InitiativeTypeCode

MD_InitiativeTypeCode
+ campaign
+ collection
+ exercise
+ experiment
+ investigation
+ mission
+ sensor
+ operation
+ platform
+ process
+ program
+ project
+ study
+ task
+ trial

DS_AssociationTypeCode
+ crossReference
+ largerWorkCitation
+ partOfSeamlessDatabase
+ source
+ stereoMate

ESIP Response

  • Karl Benedict - GIS Bounding Environmental Observations, etc., Imagery Collections
  • Tyler Stevens - GCMD DIF has "Parent"/"Child" relationships in metadata
  • Jeff Arnfield - station metadata is often hierarchical, nested, or draws on other components. Our data products or datasets often involve aggregation
  • James Gallagher - OPeNDAP servers (really DAP Servers in general) need to support aggregation in several ways. We have use cases, part. tiles, and time series
  • Xing
  • Ed Armstrong - Instruments > Missions > Campaigns
  • Henry - aggregation from daily to monthly
  • Rudy Husar