Difference between revisions of "MD Metadata"

Revision as of 13:07, 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.

ISO Objects.png

MD IdentificationInformation.png



Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed
Example is needed

ISO Legend

Possible Parent Elements

Please contribute!

@@ Line 44: / Line 44: @@
           <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><pre>Example is needed</pre></td>
+          <td></td>
        </tr>
        <tr>
@@ Line 55: / Line 55: @@
        <tr>
           <td bgcolor="CCFFFF">3</td>
-          <td bgcolor="CCFFFF">[[Citation|parentMetadata]]</td>
+          <td bgcolor="CCFFFF">[[CI_Citation|parentMetadata]]</td>
           <td bgcolor="CCFFFF">0..*</td>
           <td><i>Citation to a parent level metadata record</i></td>

Elements			Definition and Recommended Practice	Examples
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	Example is needed
3	parentMetadata	0..*	Citation to a parent level metadata record	Example is needed
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.	Example is needed
5	contact	1..*	Individual and/or organization responsible for metadata creation and maintenance. Use roleCode="pointOfContact". Provide contact details, such address, phone and email.	Example is needed
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.	Example is needed
7	metadataStandard	0..*	Citation of the metadata standard used.	Example is needed
8	metadataProfile	0..*	Citation of the profile(s) of the metadata standard used.	Example is needed
9	alternativeMetadataReference	0..*	Citation to alternative metadata for the resource.	Example is needed
10	otherLocale	0..*	Alternative language, country of origin and characterSet used in metadata.	Example is needed
11	metadataLinkage	0..*	Online location information for the metadata.	Example is needed
12	spatialRepresentationInfo	0..*	Spatial representation properties for Gridded datasets.	Example is needed
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.	Example is needed
14	metadataExtensionInfo	0..*	Description of extended metadata fields and structure.	Example is needed
15	identificationInfo MD_DataIdentification SV_ServiceIdentification	1..*	Choose one and repeat identificationInfo if needed.	Example is needed
16	contentInfo	0..*	information about the feature catalogue, or descriptions of the coverage and the image data characteristics.	Example is needed
17	distributionInfo	0..*	nformation about acquiring the resource.	Example is needed
18	dataQualityInfo	0..*	Data quality quality reporting for the resource.	Example is needed
19	resourceLineage	0..*	Data processing history (provenance) for the resource.	Example is needed
20	portrayalCatalogueInfo	0..*	A portrayal catalogue is a collection of defined symbols used to depict humans, features on a map.	Example is needed
21	metadataConstraints	0..*	The limitations or constraints regarding the use and access of the metadata.	Example is needed
22	applicationSchemaInfo	0..*	Information about the conceptual schema of the dataset.	Example is needed
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.	Example is needed
24	acquisitionInformation	0..*	Information about the platforms and instruments collecting the data.	Example is needed