Difference between revisions of "MD MetadataScope"
From Earth Science Information Partners (ESIP)
m |
|||
Line 20: | Line 20: | ||
<td bgcolor="ffffff"><pre>An example is needed!</pre></td> | <td bgcolor="ffffff"><pre>An example is needed!</pre></td> | ||
</tr> | </tr> | ||
− | <tr bgcolor=" | + | <tr bgcolor="ccffff"> |
<td>2</td> | <td>2</td> | ||
<td>[[CharacterString|name]]</td> | <td>[[CharacterString|name]]</td> | ||
− | <td>1</td> | + | <td>0..1</td> |
<td bgcolor="ffffff">The name of the hierarchy level.</td> | <td bgcolor="ffffff">The name of the hierarchy level.</td> | ||
<td bgcolor="ffffff"><pre>An example is needed!</pre></td> | <td bgcolor="ffffff"><pre>An example is needed!</pre></td> |
Revision as of 06:41, June 22, 2017
In ISO 19115 a metadata record could include any number of hierarchyLevels and hoerarchyLevelNames but there was no mechanism for connection appropriate pairs. MD_MetadataScope was introduced in ISO 19115-1 in order to allow unambiguous association of scope codes and level names. Repeat if more than one scope is applicable to this metadata description.
Elements | Definition and Recommended Practice | Examples |
||
---|---|---|---|---|
1 | resourceScope | 1 | Scope of resource to which the metadata applies. Most common values to use are the following: 'dataset' for granule level, 'series' for collection level, 'nonGeographicDataset' for space weather, 'fieldSession' for cruises or surveys, 'service' for map services and 'model'. | An example is needed! |
2 | name | 0..1 | The name of the hierarchy level. | An example is needed! |