Difference between revisions of "MD Metadata"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
− | Comprehensive explorer of ISO | + | [[Image:MD_Metadata.png|thumb|right|MD_Metadata.png]] |
− | + | Comprehensive explorer of ISO 19115-1 metadata standard. These pages show the correct order of the elements, links to child element/object, obligation, repeatability and references to more information and examples. <br> | |
+ | |||
Revision as of 10:41, January 4, 2017
Comprehensive explorer of ISO 19115-1 metadata standard. 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. |