Difference between revisions of "MD Metadata"

From Federation of Earth Science Information Partners
Line 1: Line 1:
 +
[[Image:MD_Metadata.png|thumb|right|MD_Metadata.png]]
 
== mdb:MD_Metadata ==
 
== mdb:MD_Metadata ==
[[Image:MD_Metadata.png|thumb|right|MD_Metadata.png]]
 
 
The root element of the ISO Metadata Standards contains information about the metadata and sections that contain other information.
 
The root element of the ISO Metadata Standards contains information about the metadata and sections that contain other information.
  
Line 8: Line 8:
 
<tr>
 
<tr>
 
<th colspan="3">Elements</th>
 
<th colspan="3">Elements</th>
<th colspan="1">Domain</th>
+
<th width="10%">Domain</th>
<th width="60%"><i>Definition and Recommended Practice</i></th>
+
<th width="50%"><i>Definition and Recommended Practice</i></th>
 +
<th width="30%"><i>Examples</i></th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 16: Line 17:
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">[[MD_Identifier|mcc:MD_Identifier]]</td>
 
<td bgcolor="CCFFFF">[[MD_Identifier|mcc:MD_Identifier]]</td>
<td><i>Code that uniquely identifies this metadata record, assigned and maintained by the custodian of the metadata record. Recommended Practice: value of identifier is usually the same as the name of the metadata file - for example C00500.xml. There are two general approaches to ensuring uniqueness for these identifiers: 1. use a universal unique identifier (UUID), to distinguish it from other resources. 2. Include a namespace and a code guarenteed to be unique in that namespace in the identifier. For example: gov.noaa.class:AERO100. In this case gov.noaa.class is a namespace and AERO100 is a code guaranteed to be unique in that namespace</i></td>
+
<td>Code that uniquely identifies this metadata record, assigned and maintained by the custodian of the metadata record. Recommended Practice: value of identifier is usually the same as the name of the metadata file - for example C00500.xml. There are two general approaches to ensuring uniqueness for these identifiers: 1. use a universal unique identifier (UUID), to distinguish it from other resources. 2. Include a namespace and a code guarenteed to be unique in that namespace in the identifier. For example: gov.noaa.class:AERO100. In this case gov.noaa.class is a namespace and AERO100 is a code guaranteed to be unique in that namespace</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 23: Line 25:
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">[[PT_Locale|lan:PT_Locale]]</td>
 
<td bgcolor="CCFFFF">[[PT_Locale|lan:PT_Locale]]</td>
<td><i>Default language, country of origin and characterSet used in metadata. Locale is mandatory when more than one language is used in free text descriptions</i></td>
+
<td>Default language, country of origin and characterSet used in metadata. Locale is mandatory when more than one language is used in free text descriptions</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 30: Line 33:
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
<td><i>Citation to a parent level metadata record</i></td>
+
<td>Citation to a parent level metadata record</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 37: Line 41:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_MetadataScope|mdb:MD_MetadataScope]]</td>
 
<td bgcolor="CCFFFF">[[MD_MetadataScope|mdb:MD_MetadataScope]]</td>
<td><i>Scope of resource to which the metadata applies. Now includes an MD_ScopeCode and a name for a hierarchy level. Repeat if more than one scope is applicable to this metadata description.</i></td>
+
<td>Scope of resource to which the metadata applies. Now includes an MD_ScopeCode and a name for a hierarchy level. Repeat if more than one scope is applicable to this metadata description.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 44: Line 49:
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">[[CI_Responsibility|cit:CI_Responsibility]]</td>
 
<td bgcolor="FFFF99">[[CI_Responsibility|cit:CI_Responsibility]]</td>
<td><i>Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email.</i></td>
+
<td>Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 51: Line 57:
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">[[CI_Date|cit:CI_Date]]</td>
 
<td bgcolor="FFFF99">[[CI_Date|cit:CI_Date]]</td>
<td><i>Date of last metadata update. Highly recommend revisiting the metadata content annually to ensure that all the information is still relevant. Use ISO 8601 extended format: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.</i></td>
+
<td>Date of last metadata update. Highly recommend revisiting the metadata content annually to ensure that all the information is still relevant. Use ISO 8601 extended format: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 58: Line 65:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
<td><i>Citation of the metadata standard used.</i></td>
+
<td>Citation of the metadata standard used.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 65: Line 73:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
<td><i>Citation of the profile(s) of the metadata standard used.</i></td>
+
<td>Citation of the profile(s) of the metadata standard used.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 72: Line 81:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
 
<td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td>
<td><i>Citation to alternative metadata for the resource.</i></td>
+
<td>Citation to alternative metadata for the resource.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 79: Line 89:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[PT_Locale|lan:PT_Locale]]</td>
 
<td bgcolor="CCFFFF">[[PT_Locale|lan:PT_Locale]]</td>
<td><i>Alternative language, country of origin and characterSet used in metadata.</i></td>
+
<td>Alternative language, country of origin and characterSet used in metadata.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 86: Line 97:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[CI_OnlineResource|cit:CI_OnlineResource]]</td>
 
<td bgcolor="CCFFFF">[[CI_OnlineResource|cit:CI_OnlineResource]]</td>
<td><i>Online location information for the metadata.</i></td>
+
<td>Online location information for the metadata.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 93: Line 105:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_SpatialRepresentation|msr:MD_SpatialRepresentation]]</td>
 
<td bgcolor="CCFFFF">[[MD_SpatialRepresentation|msr:MD_SpatialRepresentation]]</td>
<td><i>Spatial representation properties for Gridded datasets.</i></td>
+
<td>Spatial representation properties for Gridded datasets.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 100: Line 113:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_ReferenceSystem|mrs:MD_ReferenceSystem]]</td>
 
<td bgcolor="CCFFFF">[[MD_ReferenceSystem|mrs:MD_ReferenceSystem]]</td>
<td><i>Identification of the horizontal projections, vertical datums and temporal reference systems used. Mandatory if spatialRepresentationType in dataIdentification is vector, grid, or tin.</i></td>
+
<td>Identification of the horizontal projections, vertical datums and temporal reference systems used. Mandatory if spatialRepresentationType in dataIdentification is vector, grid, or tin.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 107: Line 121:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_MetadataExtension|mex:MD_MetadataExtensionInformation]]</td>
 
<td bgcolor="CCFFFF">[[MD_MetadataExtension|mex:MD_MetadataExtensionInformation]]</td>
<td><i>Description of extended metadata fields and structure.</i></td>
+
<td>Description of extended metadata fields and structure.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 114: Line 129:
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">1..*</td>
 
<td bgcolor="FFFF99">[[MD_DataIdentification|mri:MD_DataIdentification]]<br/>&nbsp;&nbsp;&nbsp;- or-<br>[[SV_ServiceIdentification|srv:SV_ServiceIdentification]]<br/>
 
<td bgcolor="FFFF99">[[MD_DataIdentification|mri:MD_DataIdentification]]<br/>&nbsp;&nbsp;&nbsp;- or-<br>[[SV_ServiceIdentification|srv:SV_ServiceIdentification]]<br/>
<td><i>Choose one and repeat identificationInfo if needed.</i></td>
+
<td>Choose one and repeat identificationInfo if needed.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 121: Line 137:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_ContentInformation|mrc:MD_ContentInformation]]</td>
 
<td bgcolor="CCFFFF">[[MD_ContentInformation|mrc:MD_ContentInformation]]</td>
<td><i>information about the feature catalogue, or descriptions of the coverage and the image data characteristics.</i></td>
+
<td>information about the feature catalogue, or descriptions of the coverage and the image data characteristics.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 128: Line 145:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_Distribution|mrd:MD_Distribution]]</td>
 
<td bgcolor="CCFFFF">[[MD_Distribution|mrd:MD_Distribution]]</td>
<td><i>nformation about acquiring the resource.</i></td>
+
<td>nformation about acquiring the resource.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 135: Line 153:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[DQ_DataQuality|mdq:DQ_DataQuality (ISO 19157-2)]]</td>
 
<td bgcolor="CCFFFF">[[DQ_DataQuality|mdq:DQ_DataQuality (ISO 19157-2)]]</td>
<td><i>Data quality quality reporting for the resource.</i></td>
+
<td>Data quality quality reporting for the resource.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 142: Line 161:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[LI_Lineage|mrl:LI_Lineage]]</td>
 
<td bgcolor="CCFFFF">[[LI_Lineage|mrl:LI_Lineage]]</td>
<td><i>Data processing history (provenance) for the resource.</i></td>
+
<td>Data processing history (provenance) for the resource.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 149: Line 169:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_PortrayalCatalogue|mpc:MD_PortrayalCatalogue]]</td>
 
<td bgcolor="CCFFFF">[[MD_PortrayalCatalogue|mpc:MD_PortrayalCatalogue]]</td>
<td><i>A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.</i></td>
+
<td>A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 156: Line 177:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_Constraints|mco:MD_Constraints]]</td>
 
<td bgcolor="CCFFFF">[[MD_Constraints|mco:MD_Constraints]]</td>
<td><i>The limitations or constraints regarding the use and access of the metadata.</i></td>
+
<td>The limitations or constraints regarding the use and access of the metadata.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 163: Line 185:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MD_ApplicationSchemaInformation|mas:MD_ApplicationSchemaInformation]]</td>
 
<td bgcolor="CCFFFF">[[MD_ApplicationSchemaInformation|mas:MD_ApplicationSchemaInformation]]</td>
<td><i> Information about the conceptual schema of the dataset.</i></td>
+
<td> Information about the conceptual schema of the dataset.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 170: Line 193:
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">0..1</td>
 
<td bgcolor="CCFFFF">[[MD_MaintenanceInformation|mmi:MD_MaintenanceInformation]]</td>
 
<td bgcolor="CCFFFF">[[MD_MaintenanceInformation|mmi:MD_MaintenanceInformation]]</td>
<td><i>Document recent metadata record edits. When the metadata is generated automatically, use this section to document the source and transform tool in the maintenanceNote field. </i></td>
+
<td>Document recent metadata record edits. When the metadata is generated automatically, use this section to document the source and transform tool in the maintenanceNote field. </td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 177: Line 201:
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">0..*</td>
 
<td bgcolor="CCFFFF">[[MI_AcquisitionInformation|mac:MI_AcquisitionInformation]]</td>
 
<td bgcolor="CCFFFF">[[MI_AcquisitionInformation|mac:MI_AcquisitionInformation]]</td>
<td><i>Information about the platforms and instruments collecting the data.</i></td>
+
<td>Information about the platforms and instruments collecting the data.</td>
 +
<td><i></i></td>
 
</tr>
 
</tr>
 
</table>
 
</table>

Revision as of 06:49, August 24, 2017

MD_Metadata.png

mdb:MD_Metadata

The root element of the ISO Metadata Standards contains information about the metadata and sections that contain other information.

Elements Domain Definition and Recommended Practice Examples
1 mdb:metadataIdentifier 0..1 mcc:MD_Identifier Code that uniquely identifies this metadata record, assigned and maintained by the custodian of the metadata record. Recommended Practice: value of identifier is usually the same as the name of the metadata file - for example C00500.xml. There are two general approaches to ensuring uniqueness for these identifiers: 1. use a universal unique identifier (UUID), to distinguish it from other resources. 2. Include a namespace and a code guarenteed to be unique in that namespace in the identifier. For example: gov.noaa.class:AERO100. In this case gov.noaa.class is a namespace and AERO100 is a code guaranteed to be unique in that namespace
2 mdb:defaultLocale 0..1 lan:PT_Locale Default language, country of origin and characterSet used in metadata. Locale is mandatory when more than one language is used in free text descriptions
3 mdb:parentMetadata 0..1 cit:CI_Citation Citation to a parent level metadata record
4 mdb:metadataScope 0..* mdb:MD_MetadataScope Scope of resource to which the metadata applies. Now includes an MD_ScopeCode and a name for a hierarchy level. Repeat if more than one scope is applicable to this metadata description.
5 mdb:contact 1..* cit:CI_Responsibility Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email.
6 mdb:dateInfo 1..* cit:CI_Date Date of last metadata update. Highly recommend revisiting the metadata content annually to ensure that all the information is still relevant. Use ISO 8601 extended format: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.
7 mdb:metadataStandard 0..* cit:CI_Citation Citation of the metadata standard used.
8 mdb:metadataProfile 0..* cit:CI_Citation Citation of the profile(s) of the metadata standard used.
9 mdb:alternativeMetadataReference 0..* cit:CI_Citation Citation to alternative metadata for the resource.
10 mdb:otherLocale 0..* lan:PT_Locale Alternative language, country of origin and characterSet used in metadata.
11 mdb:metadataLinkage 0..* cit:CI_OnlineResource Online location information for the metadata.
12 mdb:spatialRepresentationInfo 0..* msr:MD_SpatialRepresentation Spatial representation properties for Gridded datasets.
13 mdb:referenceSystemInfo 0..* mrs:MD_ReferenceSystem Identification of the horizontal projections, vertical datums and temporal reference systems used. Mandatory if spatialRepresentationType in dataIdentification is vector, grid, or tin.
14 mdb:metadataExtensionInfo 0..* mex:MD_MetadataExtensionInformation Description of extended metadata fields and structure.
15 mdb:identificationInfo

1..* mri:MD_DataIdentification
   - or-
srv:SV_ServiceIdentification
Choose one and repeat identificationInfo if needed.
16 mdb:contentInfo 0..* mrc:MD_ContentInformation information about the feature catalogue, or descriptions of the coverage and the image data characteristics.
17 mdb:distributionInfo 0..* mrd:MD_Distribution nformation about acquiring the resource.
18 mdb:dataQualityInfo 0..* mdq:DQ_DataQuality (ISO 19157-2) Data quality quality reporting for the resource.
19 mdb:resourceLineage 0..* mrl:LI_Lineage Data processing history (provenance) for the resource.
20 mdb:portrayalCatalogueInfo 0..* mpc:MD_PortrayalCatalogue A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.
21 mdb:metadataConstraints 0..* mco:MD_Constraints The limitations or constraints regarding the use and access of the metadata.
22 mdb:applicationSchemaInfo 0..* mas:MD_ApplicationSchemaInformation Information about the conceptual schema of the dataset.
23 mdb:metadataMaintenance 0..1 mmi:MD_MaintenanceInformation Document recent metadata record edits. When the metadata is generated automatically, use this section to document the source and transform tool in the maintenanceNote field.
24 mdb:acquisitionInformation 0..* mac:MI_AcquisitionInformation Information about the platforms and instruments collecting the data.




ISO Legend

Possible Parent Elements

ESIP-logo-tag sm-H.jpg

Please contribute!