Skip to content

Add support for gmd:status #84

@streino

Description

@streino

I'd like to suggest adding support for gmd:status.

ISO-19115:2003 definitions

gmd:status: status of the resource(s)
gmd:MD_ProgressCode: status of the dataset or progress of a review

Example

<gmd:identificationInfo>
  <gmd:MD_DataIdentification>
    <gmd:status>
      <gmd:MD_ProgressCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_ProgressCode" codeListValue="onGoing">
      </gmd:MD_ProgressCode>
    </gmd:status>
  </gmd:MD_DataIdentification>
</gmd:identificationInfo>

Rationale

It is not clear if and how this metadata should be supported because it is not mentioned at all in the INSPIRE Technical Guidelines and is defined as optional in the ISO-19115:2003 spec (I don't have access to the ISO-19139 spec but assume it's the same based on the schemas).

However, I believe it would be worth supporting because:

  • It is useful metadata, found in the wild in a number of INSPIRE catalogs (from the French administration at least).
  • It is mentioned in the GeoNetwork documentation in a page dedicated to INSPIRE, and therefore likely to be used in that context.
  • The adms:status metadata in GeoDCAT-AP seems like a good fit1 and doesn't yet have a mapping in the spec.

I wanted to go ahead and propose a PR for this, but I believe the spec needs work first:

Footnotes

  1. As suggested by https://www.w3.org/TR/vocab-dcat-3/#life-cycle. 2

  2. Mentions of adms:status in GeoDCAT-AP are inconsistent: It is specified only at the level of CatalogRecord as "change type" in section 7.3, but is then only mentioned as part of Distribution in section 10.3. No mention at the CatalogedResource level, despite DCAT mentioning it in its life-cycle1. The spec also doesn't provide any example for this metadata.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions