Workflow simple DAG should have explicit links

[nf-s]

Currently the simple DAG just has simple text - but it should link to existing item IDs so we can allow users to click to go to geometries/datasets/other dependencies

[willjnz]

This needs careful planning to be done well. It could be quite fragile to link these.

Technical lineage chart is created dynamically and builds over the workflow.

Simple lineage chart is hardcoded at the provenance step. It could be possible to add these links but it could be quite fragile.

The first input should link to a specific Dataset run e.g. https://csdr.dev.oceandevelopmentdata.org/console/dataset/run/33e9acd0-2d65-47f4-9959-22a0e1628480
The second input should link to a specific Geometry run e.g.

For this I would just need to add the dataset, geometry, and product run ids. We already have these here. I would just need to add a tag to each item in the simple provenance json so the frontend can apply these run ids to make a link for each.

Products need tags for

1. dataset input
2. geom input
3. product output (self linking needed?)
4. one or more indicators
   https://csdr.dev.oceandevelopmentdata.org/console/indicator/measured/sum-seagrass-area

Datasets need tags for:

1. dataset output (self linking needed?)

Geoms need tags for:

1. geom output (self linking needed?)

Do datasets and geometries need links added to their simple lineage? The only link for each would be to the item itself.

product simple lineage JSON example:

{
  "description": "Intersect Digital Earth Pacific''s Mangroves with EEZ boundaries to calculate mangrove area per EEZ (2017-2024) at 10m resolution.",
  "inputs": [
    "DEP Mangroves raster dataset (open and closed canopy)",
    "Global EEZ boundaries"
  ],
  "methods": [
    "Intersect and calculate area (per EEZ, per year)"
  ],
  "outputs": [
    "DEP Mangroves per EEZ Product"
  ],
  "indicators": [
    "Mangrove Area (m\u00b2)"
  ]
}

Could be updated to:

{
  "description": "Intersect Digital Earth Pacific''s Mangroves with EEZ boundaries to calculate mangrove area per EEZ (2017-2024) at 10m resolution.",
  "inputs": [
    {"description": "DEP Mangroves raster dataset (open and closed canopy)", "dataset_run_id": "33e9acd0-2d65-47f4-9959-22a0e1628480"},
    {"description": "Global EEZ boundaries", "geometries_run_id": "3e55c4fd-c4cd-5a66-b32b-7bfafc31bc75"},
  ],
  "methods": [
    "Intersect and calculate area (per EEZ, per year)"
  ],
  "outputs": [
    "DEP Mangroves per EEZ Product" -- Don't think we need to self link. Actually it could be helpful.
  ],
  "indicators": [
    {"description": "Mangrove Area (m\u00b2)", "indicator_id": "sum-mangrove-area"},
  ]
}

The indicator items could link to https://csdr.dev.oceandevelopmentdata.org/console/product/run/test-a05c1776-93ed-5616-bd09-fe3f21cf5819?from=library&section=explore&sub=table&indicatorId=sum-mangrove-area using the product run id and the indicator id.

Then the frontend SimpleWorkflowDagChart component will build the links from the ids.

[willjnz]

To do:

• Update app - Add links to product simple lineage items. Update schema for workflowDagSimple #118
• Update flux repo to pass IDs (untested) https://github.com/SustainableDevelopmentReform/csdr-cloud-spatial-flux/pull/55
• Update python repo to pass IDs (untested) Add extended workflow-dag-simple attrs to product provenance csdr-cloud-spatial#156
• Merge, migrate prod
• manually update product_run.workflow_dag_simple entries.

[willjnz]

@nf-s all products now have improved links in their simple lineage https://data.dev.sd17.org/console/product/5e7cd722-9534-4378-aedb-d5471d8af95a?section=lineage&sub=simple