The need for identifiers in metadata records was first recognized in the DIF Standard and FGDC Remote Sensing Extensions. These standards introduced identifiers for the metadata records themselves. In ISO 19115 this role is addressed by the metadataIdentifier, an MD_Identifier included in the MD_Metadata object.
Including metadataIdentifiers in the ISO metadata records gives metadata creators a mechanism for uniquely identifying them. This is becoming more important as metadata records evolve from single files into collections of related objects that can be harvested into repositories like geo.data.gov along multiple paths. There is no reliable way to identify duplicate records without a unique identifier in the actual record.
ISO 19115 also includes a MD_Identifier object for associating identifiers with various objects in the metadata record. This object was improved significantly in the revision of 19115. It now includes a Codespace that gives the namespace for the identifier, a version for the identifier, and a description along with the identifier itself. The identifier is guaranteed to be unique in that namespace.
Digital Object Identifiers (DOIs) and Other Dataset Identifiers[edit | edit source]
Digital Object Identifiers are most commonly used to identify and cite published datasets. In the ISO standard these identifiers should be included as an MD_Identifier in the CI_Citation for the dataset. This citation describes how the dataset that the metadata describes is to be cited. If the metadata record itself also had a DOI, that would be in the fileIdentifier.
As DOIs become more ubiquitous, the prefix doi: is becoming a standard internet protocol. This means that browsers and other tools will know that the string doi:10.5067/MEASURES/DMSP-F8/SSMI/DATA302 means the same thing as the URL: http://dx.doi.org/10.5067/MEASURES/DMSP-F8/SSMI/DATA302. As this becomes more common, it addresses the problem of identifiers with no straightforward mechanism for resolution.
Structure[edit | edit source]
Identifiers include several elements:
- authority - the individual or organization responsible for maintenance of the namespace
- code - code is an alphanumeric value identifying an object in a namespace that is maintained by the authority
- codeSpace - which unambiguously defines the namespace for the identifier
- version - which is a version for the identifier
- description - a brief description of the meaning of the code
Usage[edit | edit source]
Identifiers occur in many places in the ISO standard. The identifiers in Citations are particularly important because Citations also occur in many locations throughout the standard.
Managing ISO Metadata in a Database[edit | edit source]
Including identifiers in ISO metadata records gives metadata creators a mechanism for uniquely identifying metadata records and pieces of those records for the first time. The importance of unique identifiers is well known to people that use relational database management systems, they are the primary keys that identify items and make relationships possible. This is also becoming more important as metadata records are harvested into repositories like Geospatial One-Stop along multiple paths. There is no reliable way to identify duplicate records without an identifier in the actual record.
Serving Metadata With a REST web service[edit | edit source]
The REST approach to web services is becoming more and more commonplace. The first principle of REST is “Give Everything an ID”. Given this principle, one measure of how “RESTful” a metadata standard might be is the number of id’s that are included in the standard. This compares the number of IDs included in four metadata standards. The original FGDC standard has none, the Directory Interchange Format (DIF) and the FGDC Remote Sensing Extensions (RSE) have one and the ISO 19115(-2) has 36.
These ids make it possible to reference many individual elements in an ISO metadata record directly, so the ISO standard is very compatible with a RESTful approach.