Difference between revisions of "MD Metadata"
From Earth Science Information Partners (ESIP)
| Line 1: | Line 1: | ||
| − | [[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. | + | == 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. | ||
| − | + | <div id="elementsAndDefinitionsManual"> | |
| − | + | <!--elements, definitions, and examples for class: MD_Metadata--> | |
| − | + | <table cellpadding="3" width="100%"> | |
| − | + | <tr> | |
| − | + | <th colspan="3">Elements</th> | |
| − | + | <th colspan="1">Domain</th> | |
| − | + | <th width="60%"><i>Definition and Recommended Practice</i></th> | |
| − | + | </tr> | |
| − | + | <tr> | |
| − | + | <td bgcolor="CCFFFF">1</td> | |
| − | <div id="elementsAndDefinitionsManual"> <!--elements, definitions, and examples for class: MD_Metadata--> <table cellpadding="3" width="100%"> <tr> <th colspan="3">Elements</th> <th width="60%"> <i>Definition and Recommended Practice</i> </th> </tr> <tr> <td bgcolor="CCFFFF">1</td> <td bgcolor="CCFFFF">[[MD_Identifier|metadataIdentifier]]</td> <td bgcolor="CCFFFF">0..1</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> <td bgcolor="CCFFFF">2</td> <td bgcolor="CCFFFF">[[PT_Locale|defaultLocale]]</td> <td bgcolor="CCFFFF">0..1</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> <td bgcolor="CCFFFF">3</td> <td bgcolor="CCFFFF">[[CI_Citation|parentMetadata]]</td> <td bgcolor="CCFFFF">0..1</td> <td> | + | <td bgcolor="CCFFFF">[[MD_Identifier|mdb:metadataIdentifier]]</td> |
| + | <td bgcolor="CCFFFF">0..1</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_Identifier|mcc:MI_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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">2</td> | ||
| + | <td bgcolor="CCFFFF">[[PT_Locale|mdb:defaultLocale]]</td> | ||
| + | <td bgcolor="CCFFFF">0..1</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">3</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|mdb:parentMetadata]]</td> | ||
| + | <td bgcolor="CCFFFF">0..1</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td> | ||
| + | <td><i>Citation to a parent level metadata record</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">4</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_MetadataScope|mdb:metadataScope]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="FFFF99">5</td> | ||
| + | <td bgcolor="FFFF99">[[CI_Responsibility|mdb:contact]]</td> | ||
| + | <td bgcolor="FFFF99">1..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="FFFF99">6</td> | ||
| + | <td bgcolor="FFFF99">[[CI_Date|mdb:dateInfo]]</td> | ||
| + | <td bgcolor="FFFF99">1..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">7</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|mdb:metadataStandard]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td> | ||
| + | <td><i>Citation of the metadata standard used.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">8</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|mdb:metadataProfile]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td> | ||
| + | <td><i>Citation of the profile(s) of the metadata standard used.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">9</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|mdb:alternativeMetadataReference]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_Citation|cit:CI_Citation]]</td> | ||
| + | <td><i>Citation to alternative metadata for the resource.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">10</td> | ||
| + | <td bgcolor="CCFFFF">[[PT_Locale|mdb:otherLocale]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[PT_Locale|lan:PT_Locale]]</td> | ||
| + | <td><i>Alternative language, country of origin and characterSet used in metadata.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">11</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_OnlineResource|mdb:metadataLinkage]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[CI_OnlineResource|cit:CI_OnlineResource]]</td> | ||
| + | <td><i>Online location information for the metadata.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">12</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_SpatialRepresentation|mdb:spatialRepresentationInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_SpatialRepresentation|msr:MD_SpatialRepresentation]]</td> | ||
| + | <td><i>Spatial representation properties for Gridded datasets.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">13</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_ReferenceSystem|mdb:referenceSystemInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">14</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_MetadataExtension|mdb:metadataExtensionInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_MetadataExtension|mex:MD_MetadataExtension]]</td> | ||
| + | <td><i>Description of extended metadata fields and structure.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="FFFF99">15</td> | ||
| + | <td bgcolor="FFFF99">[[MD_Identification|mdb:identificationInfo]]<br/><br/></td> | ||
| + | <td bgcolor="FFFF99">1..*</td> | ||
| + | <td bgcolor="FFFF99">[[MD_DataIdentification|mri:MD_DataIdentification]]<br/> - or-<br>[[SV_ServiceIdentification|srv:SV_ServiceIdentification]]<br/> | ||
| + | <td><i>Choose one and repeat identificationInfo if needed.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">16</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_ContentInformation|mdb:contentInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">17</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_Distribution|mdb:distributionInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_Distribution|mrd:MD_Distribution]]</td> | ||
| + | <td><i>nformation about acquiring the resource.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">18</td> | ||
| + | <td bgcolor="CCFFFF">[[DQ_DataQuality|mdb:dataQualityInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[DQ_DataQuality|mdq:DQ_DataQuality (ISO 19157-2)]]</td> | ||
| + | <td><i>Data quality quality reporting for the resource.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">19</td> | ||
| + | <td bgcolor="CCFFFF">[[LI_Lineage|mdb:resourceLineage]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[LI_Lineage|mrl:LI_Lineage]]</td> | ||
| + | <td><i>Data processing history (provenance) for the resource.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">20</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_PortrayalCatalogue|mdb:portrayalCatalogueInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">21</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_Constraints|mdb:metadataConstraints]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">22</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_ApplicationSchemaInformation|mdb:applicationSchemaInfo]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_ApplicationSchemaInformation|mas:MD_ApplicationSchemaInformation]]</td> | ||
| + | <td><i> Information about the conceptual schema of the dataset.</i></td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">23</td> | ||
| + | <td bgcolor="CCFFFF">[[MD_MaintenanceInformation|mdb:metadataMaintenance]]</td> | ||
| + | <td bgcolor="CCFFFF">0..1</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> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td bgcolor="CCFFFF">24</td> | ||
| + | <td bgcolor="CCFFFF">[[MI_AcquisitionInformation|mdb:acquisitionInformation]]</td> | ||
| + | <td bgcolor="CCFFFF">0..*</td> | ||
| + | <td bgcolor="CCFFFF">[[MI_AcquisitionInformation|mac:MI_AcquisitionInformation]]</td> | ||
| + | <td><i>Information about the platforms and instruments collecting the data.</i></td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | </div> | ||
{{isoOrderingFooter}} | {{isoOrderingFooter}} | ||
[[Category:ISO Explorer]] | [[Category:ISO Explorer]] | ||
Revision as of 06:29, August 14, 2017
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 | ||
|---|---|---|---|---|
| 1 | mdb:metadataIdentifier | 0..1 | mcc:MI_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_MetadataExtension | 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. |
