ices-eg / wg_WGTAFGOV

Working group on TAF Governance
https://community.ices.dk/ExpertGroups/WGTAFGOV/SitePages/HomePage.aspx
0 stars 1 forks source link

Standard outputs from TAF repos (ARTEFACTS) #89

Open colinpmillar opened 1 year ago

colinpmillar commented 1 year ago

Summary

Please see the following proposal for defining standard outputs from a TAF analysis.

In order to identify standard outputs from stock assessments, we need to define a set of 'output types' and these should belong to a vocabulary

Proposal for new code type: CodeType: TAFOutputTypes - standard outputs from TAF analyses

Codes:

Other potential codes (draft)

An example of usage in a TAF analysis - the user creates a file called ARTIFACTS.json, this file contains an array of outputs, and the creation of the file will be supported by R functions in icesTAF package. The file contains an array of entries with three elements

{
  "file": string,
  "type": vocab - TAFOutputTypes ,
  "metdata": [
    {
      "code_type": string - vocab code type,
      "code": string - vocab code within code_type
    }
  ]
}

for example:

[
{
  "file": "output/sag_upload.xml",
  "type": "SAG",
  "metdata": [
    {
      "code_type": "ICES_StockCode",
      "code": "san.sa.6"
    },
    {
      "code_type": "Year",
      "code": "2023"
    }
  ]
},
{
  "file": "output/asd_upload.xml",
  "type": "ASD",
  "metdata": [
    {
      "code_type": "ICES_StockCode",
      "code": "san.sa.6"
    },
    {
      "code_type": "Year",
      "code": "2023"
    }
  ]
},
{
  "file": "output/stock.RData",
  "type": "FLStock",
  "metdata": [
    {
      "code_type": "ICES_StockCode",
      "code": "san.sa.6"
    },
    {
      "code_type": "Year",
      "code": "2023"
    }
  ]
}
]

Each output type will be decorated with metadata, depending on the output type different metadata will be required. We need to manage the definition of output types somewhere. The definition at its simplest can be: output type definition:

We may also want to add to the definition: