Difference between revisions of "MD Metadata"
From Earth Science Information Partners (ESIP)
| Line 1: | Line 1: | ||
Comprehensive explorer of ISO 19115 and 19115-2 metadata standards. These pages show the correct order of the elements, links to child element/object, obligation, repeatability and references to more information and examples. <br> | Comprehensive explorer of ISO 19115 and 19115-2 metadata standards. These pages show the correct order of the elements, links to child element/object, obligation, repeatability and references to more information and examples. <br> | ||
[[Image:ISO Objects.png|thumb|right|ISO Objects.png]] [[Image:MD IdentificationInformation.png|thumb|right|MD IdentificationInformation.png]] | [[Image:ISO Objects.png|thumb|right|ISO Objects.png]] [[Image:MD IdentificationInformation.png|thumb|right|MD IdentificationInformation.png]] | ||
| − | |||
| − | |||
| − | |||
| Line 37: | Line 34: | ||
<th colspan="3">Elements</th> | <th colspan="3">Elements</th> | ||
<th><i>Definition and Recommended Practice</i></th> | <th><i>Definition and Recommended Practice</i></th> | ||
| − | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 44: | Line 40: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 51: | Line 47: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td bgcolor="CCFFFF">3</td> | <td bgcolor="CCFFFF">3</td> | ||
| − | <td bgcolor="CCFFFF">[[ | + | <td bgcolor="CCFFFF">[[Citation|parentMetadata]]</td> |
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Citation to a parent level metadata record</i></td> | <td><i>Citation to a parent level metadata record</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 65: | Line 61: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 72: | Line 68: | ||
<td bgcolor="FFFF99">1..*</td> | <td bgcolor="FFFF99">1..*</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><i>Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 79: | Line 75: | ||
<td bgcolor="FFFF99">1..*</td> | <td bgcolor="FFFF99">1..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 86: | Line 82: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Citation of the metadata standard used.</i></td> | <td><i>Citation of the metadata standard used.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 93: | Line 89: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Citation of the profile(s) of the metadata standard used.</i></td> | <td><i>Citation of the profile(s) of the metadata standard used.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 100: | Line 96: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Citation to alternative metadata for the resource.</i></td> | <td><i>Citation to alternative metadata for the resource.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 107: | Line 103: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Alternative language, country of origin and characterSet used in metadata.</i></td> | <td><i>Alternative language, country of origin and characterSet used in metadata.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 114: | Line 110: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Online location information for the metadata.</i></td> | <td><i>Online location information for the metadata.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 121: | Line 117: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Spatial representation properties for Gridded datasets.</i></td> | <td><i>Spatial representation properties for Gridded datasets.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 128: | Line 124: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 135: | Line 131: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Description of extended metadata fields and structure.</i></td> | <td><i>Description of extended metadata fields and structure.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 142: | Line 138: | ||
<td bgcolor="FFFF99">1..*</td> | <td bgcolor="FFFF99">1..*</td> | ||
<td><i>Choose one and repeat identificationInfo if needed.</i></td> | <td><i>Choose one and repeat identificationInfo if needed.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 149: | Line 145: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>information about the feature catalogue, or descriptions of the coverage and the image data characteristics.</i></td> | <td><i>information about the feature catalogue, or descriptions of the coverage and the image data characteristics.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 156: | Line 152: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>nformation about acquiring the resource.</i></td> | <td><i>nformation about acquiring the resource.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 163: | Line 159: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Data quality quality reporting for the resource.</i></td> | <td><i>Data quality quality reporting for the resource.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 170: | Line 166: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Data processing history (provenance) for the resource.</i></td> | <td><i>Data processing history (provenance) for the resource.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 177: | Line 173: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.</i></td> | <td><i>A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 184: | Line 180: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>The limitations or constraints regarding the use and access of the metadata.</i></td> | <td><i>The limitations or constraints regarding the use and access of the metadata.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 191: | Line 187: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i> Information about the conceptual schema of the dataset.</i></td> | <td><i> Information about the conceptual schema of the dataset.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 198: | Line 194: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</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><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> | ||
| − | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 205: | Line 201: | ||
<td bgcolor="CCFFFF">0..*</td> | <td bgcolor="CCFFFF">0..*</td> | ||
<td><i>Information about the platforms and instruments collecting the data.</i></td> | <td><i>Information about the platforms and instruments collecting the data.</i></td> | ||
| − | + | ||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 13:12, December 19, 2016
Comprehensive explorer of ISO 19115 and 19115-2 metadata standards. These pages show the correct order of the elements, links to child element/object, obligation, repeatability and references to more information and examples.
| Elements | Definition and Recommended Practice | ||
|---|---|---|---|
| 1 | metadataIdentifier | 0..* | 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 | defaultLocale | 0..* | 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 | parentMetadata | 0..* | Citation to a parent level metadata record |
| 4 | metadataScope | 0..* | 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 | contact | 1..* | Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email. |
| 6 | dateInfo | 1..* | 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 | metadataStandard | 0..* | Citation of the metadata standard used. |
| 8 | metadataProfile | 0..* | Citation of the profile(s) of the metadata standard used. |
| 9 | alternativeMetadataReference | 0..* | Citation to alternative metadata for the resource. |
| 10 | otherLocale | 0..* | Alternative language, country of origin and characterSet used in metadata. |
| 11 | metadataLinkage | 0..* | Online location information for the metadata. |
| 12 | spatialRepresentationInfo | 0..* | Spatial representation properties for Gridded datasets. |
| 13 | referenceSystemInfo | 0..* | Identification of the horizontal projections, vertical datums and temporal reference systems used. Mandatory if spatialRepresentationType in dataIdentification is vector, grid, or tin. |
| 14 | metadataExtensionInfo | 0..* | Description of extended metadata fields and structure. |
| 15 | identificationInfo MD_DataIdentification SV_ServiceIdentification |
1..* | Choose one and repeat identificationInfo if needed. |
| 16 | contentInfo | 0..* | information about the feature catalogue, or descriptions of the coverage and the image data characteristics. |
| 17 | distributionInfo | 0..* | nformation about acquiring the resource. |
| 18 | dataQualityInfo | 0..* | Data quality quality reporting for the resource. |
| 19 | resourceLineage | 0..* | Data processing history (provenance) for the resource. |
| 20 | portrayalCatalogueInfo | 0..* | A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map. |
| 21 | metadataConstraints | 0..* | The limitations or constraints regarding the use and access of the metadata. |
| 22 | applicationSchemaInfo | 0..* | Information about the conceptual schema of the dataset. |
| 23 | metadataMaintenance | 0..* | 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 | acquisitionInformation | 0..* | Information about the platforms and instruments collecting the data. |
