StocksAndFisheriesKB

Yannis Marketakis wrote in #note-4:

Is this related to the discussion we have about providing some hidden areas while publishing/updating, that will be used for generated tags?

Yes

If so, just to clarify that they will not be just FAO areas, but areas of any type.

I created the ticket togheter with @aureliano.gentile@fao.org.
I have indeed modified the title. Thanks for the clarification.

A new functionality that includes all the parent areas for a record has been implemented.
As agreed, the extended collection of areas, is added in a different field in the submitted json file. This field is called hidden_assessment_area.

The difference between assessment_area and hidden_assessment_area is that the first one contains the explicit areas, while the second one contains both the explicit and the parent areas.
The following part of the submitted json shows the contents of the two field for the stock https://data.d4science.org/ctlg/GRSF_Pre/f0eb0e4d-f2a6-39a2-bfd2-0b541af416dc.

{
    "assessment_area": [
        "Code: 47, System: lme, Name: Antarctica"
    ],
    "hidden_assessment_area": [
        "Code: 88, System: fao, Name: Pacific, Antarctic",
        "Code: 47, System: lme, Name: Antarctica",
        "Code: 48, System: fao, Name: Atlantic, Antarctic"
    ]
}

The detailed json of this stock record is attached.

The same functionality is also applicable for GRSF fishery records. The new field for fisheries is called hidden_fishing_area.

{
    "fishing_area": [
        "Code: KNA, System: eez, Name: fao:31"
    ],
    "hidden_fishing_area": [
        "Code: 31, System: fao, Name: Atlantic, Western Central",
        "Code: KNA, System: eez, Name: fao:31"
    ]
}