MD DataIdentification

From Earth Science Information Partners (ESIP)
Revision as of 18:24, December 20, 2016 by Jkozimor (talk | contribs)







Elements Definition and Recommended Practice
Examples
1 citation 1 Citation for the resource, includes name, publication date, identifiers, originators and publishers.
Example is needed
2 abstract 1 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.
Example is needed
3 purpose 0..* Summary of intentions for which the resource was developed.
Example is needed
4 credit 0..* Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section.
Example is needed
5 status 0..* Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.
Example is needed
6 pointOfContact 0..* 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.
Example is needed
7 spatialRepresentationType 0..* Object(s) used to represent the geographic information.
Example is needed
8 spatialResolution 0..* The spatial resolution (level of spatial detail) of the dataset.
Example is needed
9 temporalResolution 0..* The temporal resolution (level of temporal detail) of the dataset.
Example is needed
10 topicCategory 0..* 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.
Example is needed
11 extent 0..* Information about the spatial, horizontal and/or vertical, and the temporal coverage of the resource.
12 additionalDocumentation 0..* Additional documentation related to the resource such as publications and users guides.
Example is needed
13 processingLevel 0..* An identifier code that identifies the level of processing in the producers coding system.
Example is needed
14 resourceMaintenance 0..* Information about the frequency, scope, and responsible party for the updating of the resource.
Example is needed
15 graphicOverview 0..* 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.
Example is needed
16 resourceFormat 0..* 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'.
Example is needed
17 descriptiveKeywords 0..* 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.
Example is needed
18 resourceSpecificUsage 0..* Basic information about specific application(s) for which the resource(s) has been or is being used by different users.
Example is needed
19 resourceConstraints 0..* The limitations or constraints on the use of or access to the resource.
Example is needed
20 associatedResource 0..* The citations and identifiers of associated resources, such as projects and documents.
Example is needed


ISO Legend

Possible Parent Elements

ESIP-logo-tag sm-H.jpg

Please contribute!

Documentation Spirals#Identification