MD DataIdentification

From NOAA Environmental Data Management Wiki
Elements Definition and Recommended Practice
1 citation 1 Citation for the resource, includes name, publication date, identifiers, originators and publishers.
2 abstract 1 Brief narrative summary of the resource. This is different than a scientific abstract. Limit information in the abstract to the specific resource that is being described. Provide descriptive information in a clear, concise and human readable manner. Describe the contents of the resource and the key aspects and/or attributes that are represented. Briefly explain what is unique about this resource and, if appropriate how it differs from similar resources. Ensure contextual information important to the use of the resource are explained, e.g. formats, recommended tools, related resources, or limitations. Avoid citing external sources to this resource.
See abstract Other Recommendations
3 purpose 0..1 Summary of intentions for which the resource was developed.
See purpose_examples
4 credit 0..* Recognition of those who contributed to the dataset. Do not include URLs here.
Provide full citations in MD_AggregateInformation section.
5 status 0..* Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field.
See Status Examples
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.
7 resourceMaintenance 0..* Information about the frequency, scope, and responsible party for the updating of the resource.
See MD_MaintenanceInformation Examples
8 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.
See MD_BrowseGraphic Examples
9 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'.
10 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.
11 resourceSpecificUsage 0..* Basic information about specific application(s) for which the resource(s) has been or is being used by different users.
12 resourceConstraints 0..* The limitations or constraints on the use of or access to the resource.
13 aggregationInfo 0..* The citations and identifiers of associated resources, such as projects and documents.
14 spatialRepresentationType 0..* Object(s) used to represent the geographic information.
15 spatialResolution 0..* The level of detail of the dataset expressed as equivalent scale or ground distance.
16 language 1..* Languages of the dataset using standard ISO three-letter codes.
Best Practice: eng; USA
17 characterSet 0..* Character coding standard in the dataset.
18 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.
19 environmentDescription 0..1 Describes the dataset’s processing environment. Includes information, such as software, computer operating system, filename, and dataset size. Provide full citations in the LI_Lineage section.
20 extent 0..* Information about the spatial, horizontal and/or vertical, and the temporal coverage of the resource.
21 supplementalInformation 0..1 Other descriptive information about the resource.

Community Requirements

M = Mandatory; C = Conditional; R = Recommended; blank cell = user discretion

Community Element M C R Notes

NOAA Completeness Rubric V2

citation M
abstract M
purpose M
credit Same requirements as the ISO standard
status M
pointOfContact M
resourceMaintenance R Extra credit for recommended fields.
graphicOverview R
resourceFormat Same requirements as the ISO standard
descriptiveKeywords M
resourceSpecificUsage Same requirements as the ISO standard
resourceConstraints M
aggregationInfo R Extra credit for recommended fields
spatialRepresentationType M
spatialResolution Same requirements as the ISO standard
language
characterSet
topicCategory M
environmentDescription Same requirements as the ISO standard
extent M Only geographicExtent is conditional.
supplementalInformation Same requirements as the ISO standard

OneStop Project

citation M
abstract M
purpose M
credit Same requirements as the ISO standard
status M
pointOfContact M
resourceMaintenance Same requirements as the ISO standard
graphicOverview M
resourceFormat Same requirements as the ISO standard
descriptiveKeywords M Mandatory for OneStop Collection records. Not mandatory for Granule level records.
resourceSpecificUsage Same requirements as the ISO standard
resourceConstraints M
aggregationInfo R Extra credit for recommended fields
spatialRepresentationType M
spatialResolution Same requirements as the ISO standard
language
characterSet
topicCategory M
environmentDescription Same requirements as the ISO standard
extent M Only geographicExtent is conditional.
supplementalInformation Same requirements as the ISO standard

More Information

UML
Description.MD DataIdentification.png
Links




Legend