MD Metadata
From Earth Science Information Partners (ESIP)
Revision as of 09:05, November 14, 2016 by Ted.Habermann (talk | contribs)
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 | Examples | ||
|---|---|---|---|---|
| 1 | metadataIdentifier | 0..1 | 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. | identifier: (MD_Identifier) code: C00500 codeSpace: gov.noaa.ncdc |
| 2 | defaultLocale | 0..* | Default language and characterSet used in metadata. Locale is mandatory when more than one language is used in free text descriptions.
|
|
| 3 | parentMetadata | 0..1 | Document a higher level metadata record if it exists. Provide full citation to parent. | |
| 4 | hierarchyLevel | 0..* | Scope of resource to which the metadata applies. Most common values to use are the following: 'dataset' for granule level, 'series' for collection level, 'nonGeographicDataset' for space weather, 'fieldSession' for cruises or surveys, 'service' for map services and 'model'. Repeat if more than one scope is applicable to this metadata description. | |
| 6 | hierarchyLevelName | 0..* | ||
| 7 | contact | 1..* | Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email. | |
| 8 | dateStamp (choose one) | 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. | 2015-12-08 |
| 9 | metadataStandard | 0..* | Name of the metadata standard used. Use text in the example. | ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data |
| 10 | metadataProfile | 0..* | Profile(s) of the metadata standard used. | ISO 19115-2:2009(E) |
| 13 | spatialRepresentationInfo | 0..* | Digital representation of spatial information in the dataset.
|
|
| 14 | referenceSystemInfo | 0..* | Identification of the horizontal projections, vertical datums and temporal reference systems used. Mandatory if spatialRepresentationType in dataIdentification is vector, grid, or tin
|
|
| 15 | metadataExtensionInfo | 0..* | Information describing metadata extensions. |
|
| 16 | identificationInfo |
1..* | Choose one and repeat identificationInfo if needed. |
|
| 17 | contentInfo | 0..* | Information about the feature catalogue, or descriptions of the coverage and the image data characteristics. |
|
| 18 | distributionInfo | 0..1 | Information about acquiring the resource |
|
| 19 | dataQualityInfo | 0..* | history and quality of 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 on the use of or access of the metadata. |
|
| 22 | applicationSchemaInfo | 0..* | Information about the conceptual schema of the dataset. |
|
| 23 | metadataMaintenance | 0..1 | 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. |
metadataMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annually dateOfNextUpdate: 2016-11-06 maintenanceNote: This record was automatically modified on 2015-11-05 to include references to NCEI where applicable. |
| 24 | acquisitionInformation | 0..* | Information about the platforms and instruments collecting the data. |
|
