Skip to content

EOEPCA Utilisation Domain User Stories - Metadata Profile #154

@GarinSmith

Description

@GarinSmith

Summary
These user stories aim to give EOEPCA a clearer strategic vision to help support EarthCODE.
They define what we as an EarthCODE utilisation domain want from EOEPCA.
They focus on defining a better EarthCODE schema for experiments based upon real EarthCODE experiments.
They focus on collaborating to evolve the EarthCODE FAIR score tool to help give a better score for real EarthCODE experiments.
We hope this will help enable EOEPCA to better develop building blocks that support EarthCODE experiments.

User Story One)
As an EarthCODE Utilisation Domain, I want a schema that validates EarthCODE experiments, so that I know that their metadata complies with FAIR principles.
a. Acceptance criteria – must be based on real world EarthCODE experiments. See
https://opensciencedata.esa.int/experiments/catalog
https://github.com/ESA-EarthCODE/open-science-catalog-metadata/tree/main/experiments
b. Acceptance criteria – deliver a code list of additional validation checks.
This means that the schema is likely to remain fairly stable.
This means that the code list is more likely to change when new validation checks are added.
c. Acceptance criteria – validation checks must be executable on the command line using Python, so that platforms can use them before making a publishing request.
d. Consider the use of schemas identified in OSPD Project. See below for examples
https://github.com/ogcincubator/bblocks-openscience/blob/master/_sources/geodcat-stac-earthcode/experiments/examples/water-bodies-prov.json
https://github.com/ogcincubator/bblocks-openscience/blob/master/_sources/geodcat-stac-earthcode/workflows/examples/water-bodies-with-provenance.json
https://github.com/ogcincubator/bblocks-openscience/blob/master/_sources/geodcat-stac-earthcode/products/examples/water-bodies-with-provenance.json
e. For further information please also refer to the following (sent separately)
• D001_Section_3_Open Science Demonstrators of OSPD 2025-TPZ Updates and Feedback.docx
• water-bodies-records.tgz

Please also consider feedback from CGI (for all relevant use cases) https://esait.sharepoint.com/:b:/r/sites/EarthCODE/Shared%20Documents/General/Deliverables/04%20BP2%20Deliverables/MS2/CGI/QDR/OSC_metadata_schema_CGI_for_EarthCODE.pdf?csf=1&web=1&e=EVj3kP

User Story Two)
As an EarthCODE Domain, I want a schema that validates EarthCODE workflows, so that I know that their metadata complies with FAIR principles.
a. Must be based on real world EarthCODE workflows. See
https://opensciencedata.esa.int/workflows/catalog
https://github.com/ESA-EarthCODE/open-science-catalog-metadata/tree/main/workflows

User Story Three)
As an EarthCODE User, I want an enhanced FAIR score for my experiment, so that I know how FAIR it is.
a. Add to the existing solution that currently focuses primarily on Find and Access scores.
b. Focus on Interoperability and Re-use
c. Must be based on real world EarthCODE experiments and workflows. See above.
d. It is expected that experiments with good FAIR scores will work well with relevant EOEPCA building blocks.
FAIR Score Tool
i) Please see https://github.com/ESA-EarthCODE/earthcode-library/blob/main/earthcode/fairtool.py
ii) Please see https://github.com/ESA-EarthCODE/earthcode-library/blob/main/tests/test_fairtool.py
Please note this is currently aimed at Product FAIR Score. See actions above

User Story Four)
iv) As an EarthCODE User, I want to reproduce an experiment on a new platform, so that I know it can be reproduced.
a. Must use real world EarthCODE experiments and workflows. See above.
b. May want to break down by experiment type (E.g. OGC API Processes, OpenEO, JNP etc)
c. Consider use of FAIR score to ensure an experiment can be reproduced and it ready to be reproduced.

User Story Five)
As an EarthCODE User, I want to reproduce an experiment using two platforms, so that it runs more efficiently than on only one platform.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions