StocksAndFisheriesKB

@marketak@ics.forth.gr I just remember that @aureliano.gentile@fao.org asked me the following requirements during the meeting in Pisa see #24604

To satisfy both requirements, we could have the following JSON

"database_sources" : [ "Fisheries and Resources Monitoring System (FIRMS)", "FAO SDG 14.4.1 Questionnaire" ]

Moreover, I generate the multiple times the metadata Database Source (one time for each element of the array).

@marketak@ics.forth.gr I just realised that you are right. Thanks for highlighting this.
Also the database_sources should create a resource but in the case of the record

https://data.d4science.org/ctlg/GRSF_Admin/cb468fb0-fed5-370f-9bc6-08fa99c54f3c

they were not created.

Maybe, they were overwritten by the resources generated from refers_to due to the name clash.

"refers_to":
    [
        {
            "id": "2109694f-17d1-3206-815d-179bc52e5ec7",
            "url": "https://data.d4science.org/ctlg/GRSF_Admin/2109694f-17d1-3206-815d-179bc52e5ec7"
        },
        {
            "id": "c0d7d44f-71cb-3b28-9b65-ddf72c57d44f",
            "url": "https://data.d4science.org/ctlg/GRSF_Admin/c0d7d44f-71cb-3b28-9b65-ddf72c57d44f"
        },
        {
            "id": "1b3ce0de-1ed1-3ba8-8a80-f866b287617e",
            "url": "https://data.d4science.org/ctlg/GRSF_Admin/1b3ce0de-1ed1-3ba8-8a80-f866b287617e"
        }
    ],

In fact, as explained in ticket #24816 the name of refers_to resources are derived from the lookup of the pointed resources and we discussed about having a more significant name.

Can we talk about this in a call?

In any case, I've just realised that this field database_sources is fine as it is.
Instead, I have to change the behaviour for the name in refers_to to avoid name clashes.
I can use the id you already provide or a more significant name, but we will discuss bout this in ticket #24816.

To comply with the new request of @aureliano.gentile@fao.org in #24604, what about if we add another property in each database_sources element e.g. long_name

E.g.

"database_sources" : [ {
    "name" : "FishSource",
    "long_name" : "FishSource",
    "description" : "FishSource is an online information resource about the status of stocks and fisheries, that compiles and summarizes all the information that is needed from analysts to evaluate the sustainability.",
    "url" : "http://www.fishsource.com"
  }, {
    "name" : "FIRMS",
    "long_name" : "Fisheries and Resources Monitoring System (FIRMS)",
    "description" : "Fisheries and Resources Monitoring System aims to provide access to a wide range of high-quality information on the global monitoring and management of fishery marine resources",
    "url" : "http://firms.fao.org/firms/en"
  }, {
    "name" : "RAM",
    "long_name" : "RAM Legacy Stock Assessment Database",
    "description" : "RAM Legacy Stock Assessment Database is a compilation of stock assessment results for commercially exploited marine populations from around the world.",
    "url" : "http://ramlegacy.org"
  } ]

@aureliano.gentile@fao.org does the creation of the resource point to the database source which are well know an added value?

Hi @luca.frosini@isti.cnr.it,

I replied to #24816 (please check).
Of course we can discuss this (and any other issue) in a dedicated call

I just had a call with @aureliano.gentile@fao.org and we agreed that:

• the generated Resources not only are useless but they create confusion;
• we need to create a metadata for each database source instead of concatenating them in a single metadata.
• each metadata must contain the longest version of the source.

So we can keep the same structure and add the long_name as follows:

"database_sources" : [ {
    "name" : "FishSource",
    "long_name" : "FishSource",
    "description" : "FishSource is an online information resource about the status of stocks and fisheries, that compiles and summarizes all the information that is needed from analysts to evaluate the sustainability.",
    "url" : "http://www.fishsource.com"
  }, {
    "name" : "FIRMS",
    "long_name" : "Fisheries and Resources Monitoring System (FIRMS)",
    "description" : "Fisheries and Resources Monitoring System aims to provide access to a wide range of high-quality information on the global monitoring and management of fishery marine resources",
    "url" : "http://firms.fao.org/firms/en"
  }, {
    "name" : "RAM",
    "long_name" : "RAM Legacy Stock Assessment Database",
    "description" : "RAM Legacy Stock Assessment Database is a compilation of stock assessment results for commercially exploited marine populations from around the world.",
    "url" : "http://ramlegacy.org"
  } ]

or having a simples array like this

"database_sources": [
  "FishSource",
  "Fisheries and Resources Monitoring System (FIRMS)",
  "RAM Legacy Stock Assessment Database"
]

I prefer the latter if possible

OK let's keep the second approach that is much simpler and less verbose

"database_sources": [
  "FishSource",
  "Fisheries and Resources Monitoring System (FIRMS)",
  "RAM Legacy Stock Assessment Database"
]

Thank you, all fine with me. The above examples do not cover the 4th source of information (FAO SDG 14.4.1 Questionnaire) but I trust this will be part of the implementation.
Aureliano

The complete list is:

"database_sources": [
  "FishSource",
  "Fisheries and Resources Monitoring System (FIRMS)",
  "RAM Legacy Stock Assessment Database",
  "FAO SDG 14.4.1 Questionnaire"
]