Difference between revisions of "MD Metadata"

From Earth Science Information Partners (ESIP)
Line 27: Line 27:
  
  
<div id="elementsAndDefinitionsManual"> <!--elements, definitions, and examples for class: AbstractMD_Identification--> <table cellpadding="3" width="100%"> <tr> <th colspan="3">Elements</th> <th width="60%"> <i>Definition and Recommended Practice</i> </th> <th width="20%"> <pre>Examples</pre> </th> </tr> <tr> <td bgcolor="FFFF99">1</td> <td bgcolor="FFFF99">[[CI_Citation|citation]]</td> <td bgcolor="FFFF99">1</td> <td> <i>Citation for the resource, includes name, publication date, identifiers, originators and publishers.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/citation Type: Abstract_Citation-->See [[CI_Citation]]</td> </tr> <tr> <td bgcolor="FFFF99">2</td> <td bgcolor="FFFF99">[[CharacterString|abstract]]</td> <td bgcolor="FFFF99">1</td> <td> <i>Brief narrative summary of the resource contents. Include summary information on general content and features; resource applications: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/abstract Type: CharacterString-->See [[CharacterString]]</td> </tr> <tr> <td bgcolor="CCFFFF">3</td> <td bgcolor="CCFFFF">[[CharacterString|purpose]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Summary of intentions for which the resource was developed.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/purpose Type: CharacterString-->See [[CharacterString]]</td> </tr> <tr> <td bgcolor="CCFFFF">4</td> <td bgcolor="CCFFFF">[[CharacterString|credit]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/credit Type: CharacterString-->See [[CharacterString]]</td> </tr> <tr> <td bgcolor="CCFFFF">5</td> <td bgcolor="CCFFFF">[[MD_ProgressCode|status]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/status Type: MD_ProgressCode-->See [[MD_ProgressCode]]</td> </tr> <tr> <td bgcolor="CCFFFF">6</td> <td bgcolor="CCFFFF">[[CI_Responsibility|pointOfContact]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Individuals and/or organizations available for questions about the resource. Use roleCode="pointOfContact". This should be a person at an archive or the originator of the resource. Provide contact details, such address, phone and email.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/pointOfContact Type: Abstract_Responsibility-->See [[CI_Responsibility]]</td> </tr> <tr> <td bgcolor="CCFFFF">7</td> <td bgcolor="CCFFFF">[[MD_SpatialRepresentationTypeCode|spatialRepresentationType]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Object(s) used to represent the geographic information.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/spatialRepresentationType Type: MD_SpatialRepresentationTypeCode-->See [[MD_SpatialRepresentationTypeCode]]</td> </tr> <tr> <td bgcolor="CCFFFF">8</td> <td bgcolor="CCFFFF">[[MD_Resolution|spatialResolution]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The spatial resolution (level of spatial detail) of the dataset.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/spatialResolution Type: MD_Resolution-->See [[MD_Resolution]]</td> </tr> <tr> <td bgcolor="CCFFFF">9</td> <td bgcolor="CCFFFF">[[TM_PeriodDuration|temporalResolution]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The temporal resolution (level of temporal detail) of the dataset.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/temporalResolution Type: TM_PeriodDuration-->See [[TM_PeriodDuration]]</td> </tr> <tr> <td bgcolor="CCFFFF">10</td> <td bgcolor="CCFFFF">[[MD_TopicCategoryCode|topicCategory]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>main theme(s) of the resource</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/topicCategory Type: MD_TopicCategoryCode-->See [[MD_TopicCategoryCode]]</td> </tr> <tr> <td bgcolor="CCFFFF">11</td> <td bgcolor="CCFFFF">[[EX_Extent|extent]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>High-level thematic classifications to assist in the grouping and searching of data. Required when the hierarchyLevelName scopeCode is 'dataset'. Recommended when hierarchyLevelName scopeCode is 'series', 'fieldSession', or 'nonGeographicDataset'. The most applicable topics in NOAA are usually geoscientificInformation, climatologyMeteorologyAtmosphere, oceans or elevation. Repeat if more than one category is applicable. Keep the capitalization and spacing of the terms.</i> </td> <td align="center">See [[EX_Extent]]</td> </tr> <tr> <td bgcolor="CCFFFF">12</td> <td bgcolor="CCFFFF">[[CI_Citation|additionalDocumentation]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Additional documentation related to the resource such as publications and users guides.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/additionalDocumentation Type: Abstract_Citation-->See [[CI_Citation]]</td> </tr> <tr> <td bgcolor="CCFFFF">13</td> <td bgcolor="CCFFFF">[[MD_Identifier|processingLevel]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>An identifier code that identifies the level of processing in the producers coding system.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/processingLevel Type: MD_Identifier-->See [[MD_Identifier]]</td> </tr> <tr> <td bgcolor="CCFFFF">14</td> <td bgcolor="CCFFFF">[[MD_MaintenanceInformation|resourceMaintenance]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Information about the frequency, scope, and responsible party for the updating of the resource.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/resourceMaintenance Type: Abstract_MaintenanceInformation-->See [[MD_MaintenanceInformation]]</td> </tr> <tr> <td bgcolor="CCFFFF">15</td> <td bgcolor="CCFFFF">[[MD_BrowseGraphic|graphicOverview]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>A small image that exemplifies the collective resource. The graphic file should be less than 500KB and 1000x1000 pixels. Provide URL to an image that can be rendered in browsers.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/graphicOverview Type: MD_BrowseGraphic-->See [[MD_BrowseGraphic]]</td> </tr> <tr> <td bgcolor="CCFFFF">16</td> <td bgcolor="CCFFFF">[[MD_Format|resourceFormat]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Information about the formats of the resource. This is independant of the distribution details and is useful to provide when the resource has a status of 'planned' or 'underDevelopment'.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/resourceFormat Type: Abstract_Format-->See [[MD_Format]]</td> </tr> <tr> <td bgcolor="CCFFFF">17</td> <td bgcolor="CCFFFF">[[MD_Keywords|descriptiveKeywords]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Commonly used words or phrases which describe the dataset. Optionally, the keyword type and a citation for the authoritative or registered resource of the keywords are also provided.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/descriptiveKeywords Type: MD_Keywords-->See [[MD_Keywords]]</td> </tr> <tr> <td bgcolor="CCFFFF">18</td> <td bgcolor="CCFFFF">[[MD_Usage|resourceSpecificUsage]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Basic information about specific application(s) for which the resource(s) has been or is being used by different users.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/resourceSpecificUsage Type: MD_Usage-->See [[MD_Usage]]</td> </tr> <tr> <td bgcolor="CCFFFF">19</td> <td bgcolor="CCFFFF">[[MD_Constraints|resourceConstraints]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The limitations or constraints on the use of or access to the resource.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/resourceConstraints Type: Abstract_Constraints-->See [[MD_Constraints]]</td> </tr> <tr> <td bgcolor="CCFFFF">20</td> <td bgcolor="CCFFFF">[[MD_AssociatedResource|associatedResource]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>The citations and identifiers of associated resources, such as projects and documents.</i> </td> <td align="center"><!--No example found: AbstractMD_Identification/associatedResource Type: MD_AssociatedResource-->See [[MD_AssociatedResource]]</td> </tr> </table> </div>
+
<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> <th width="20%"> <pre>Examples</pre> </th> </tr> <tr> <td bgcolor="CCFFFF">1</td> <td bgcolor="CCFFFF">[[MD_Identifier|metadataIdentifier]]</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> </tr> <tr> <td bgcolor="CCFFFF">2</td> <td bgcolor="CCFFFF">[[PT_Locale|defaultLocale]]</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> </tr> <tr> <td bgcolor="CCFFFF">3</td> <td bgcolor="CCFFFF">[[CI_Citation|parentMetadata]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Citation to a parent level metadata record</i> </td> </tr> <tr> <td bgcolor="CCFFFF">4</td> <td bgcolor="CCFFFF">[[MD_MetadataScope|metadataScope]]</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> </tr> <tr> <td bgcolor="FFFF99">5</td> <td bgcolor="FFFF99">[[CI_Responsibility|contact]]</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> </tr> <tr> <td bgcolor="FFFF99">6</td> <td bgcolor="FFFF99">[[CI_Date|dateInfo]]</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> </tr> <tr> <td bgcolor="CCFFFF">7</td> <td bgcolor="CCFFFF">[[CI_Citation|metadataStandard]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Citation of the metadata standard used.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">8</td> <td bgcolor="CCFFFF">[[CI_Citation|metadataProfile]]</td> <td bgcolor="CCFFFF">0..*</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|alternativeMetadataReference]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Citation to alternative metadata for the resource.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">10</td> <td bgcolor="CCFFFF">[[PT_Locale|otherLocale]]</td> <td bgcolor="CCFFFF">0..*</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|metadataLinkage]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Online location information for the metadata.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">12</td> <td bgcolor="CCFFFF">[[MD_GridSpatialRepresentation|spatialRepresentationInfo]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Spatial representation properties for Gridded datasets.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">13</td> <td bgcolor="CCFFFF">[[MD_ReferenceSystem|referenceSystemInfo]]</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> </tr> <tr> <td bgcolor="CCFFFF">14</td> <td bgcolor="CCFFFF">[[MD_MetadataExtension|metadataExtensionInfo]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Description of extended metadata fields and structure.</i> </td> </tr> <tr> <td bgcolor="FFFF99">15</td> <td bgcolor="FFFF99">identificationInfo<br/>&nbsp;&nbsp;&nbsp;[[MD_DataIdentification|MD_DataIdentification]]<br/>&nbsp;&nbsp;&nbsp;[[SV_ServiceIdentification|SV_ServiceIdentification]]<br/></td> <td bgcolor="FFFF99">1..*</td> <td> <i>Choose one and repeat identificationInfo if needed.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">16</td> <td bgcolor="CCFFFF">[[MD_ContentInformation|contentInfo]]</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> </tr> <tr> <td bgcolor="CCFFFF">17</td> <td bgcolor="CCFFFF">[[MD_Distribution|distributionInfo]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>nformation about acquiring the resource.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">18</td> <td bgcolor="CCFFFF">[[DQ_DataQuality|dataQualityInfo]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Data quality quality reporting for the resource.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">19</td> <td bgcolor="CCFFFF">[[LI_Lineage|resourceLineage]]</td> <td bgcolor="CCFFFF">0..*</td> <td> <i>Data processing history (provenance) for the resource.</i> </td> </tr> <tr> <td bgcolor="CCFFFF">20</td> <td bgcolor="CCFFFF">[[MD_PortrayalCatalogue|portrayalCatalogueInfo]]</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> </tr> <tr> <td bgcolor="CCFFFF">21</td> <td bgcolor="CCFFFF">[[MD_Constraints|metadataConstraints]]</td> <td bgcolor="CCFFFF">0..*</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|applicationSchemaInfo]]</td> <td bgcolor="CCFFFF">0..*</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|metadataMaintenance]]</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> </tr> <tr> <td bgcolor="CCFFFF">24</td> <td bgcolor="CCFFFF">[[MI_AcquisitionInformation|acquisitionInformation]]</td> <td bgcolor="CCFFFF">0..*</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 15:05, December 23, 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_Metadata.png














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
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.


ISO Legend

Possible Parent Elements

ESIP-logo-tag sm-H.jpg

Please contribute!