Skip to content

Inclusion of metadata field "GOOS Applications" #4

Description

@PatricaCabrera

Background

EC-OBPSS includes a metadata field for GOOS Applications. This field does not currently exist in IOC-OBPS.

As part of the metadata alignment exercise, we reviewed whether this field would add value to the OBPS metadata model.

Current situation

IOC-OBPS: No dedicated metadata field for GOOS Applications.

EC-OBPSS uses the following controlled vocabulary:

  • Biodiversity analysis and assessment
  • Climate analysis and assessment
  • Climate prediction and projection
  • Environmental assessment and outlook
  • Hazard response / early warning system
  • Operational ocean data and forecasting
  • Sustainable management and food security
  • Coastal management

Assessment

To evaluate the usefulness of this field, we reviewed its application in the GOOS BioEco Panel specification sheets.

The assessment found that almost all specification sheets assign the three broad GOOS application categories:

  • Climate Change
  • Ocean Health
  • Operational Services

These high-level categories do not provide sufficient discrimination between Best Practices and are already reflected, directly or indirectly, through other metadata fields.

It is unclear where the detailed list adopted by EC-OBPSS comes from or is used.

Questions for the community

  • Does GOOS Applications provide information that is not already captured by other metadata?
  • Is there an authoritative source for the EC-OBPSS vocabulary?
  • Are there use cases where this field would significantly improve discovery or filtering?

Proposed outcome

Current recommendation: Do not introduce GOOS Applications as a separate metadata field in OBPS unless a clear, non-redundant use case and an authoritative controlled vocabulary can be demonstrated.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions