28 September 2016 FishSource, further clarification with FORTH.¶
Meeting Notes
Topics: acquire further information on FishSource data for completing the harvesting process.
Participants: FishSource (Susana Segurado, Merul Patel), FORTH (Yannis Marketakis, Nikos Minadakis), FAO (Anton Ellenbroek, Aymen Charif, Emmanuel Blondel, Aureliano Gentile)
Notes
- FORTH presented the progress that has been achieved so far, as regards FishSource modeling activities. The link for the slides can be found at the bottom of this page.
- The stock name as exposed from the API is different than the name as exposed in the FishSource front-end. In the API the name refers only to the water area, therefore FORTH should concatenate it with the species name.
- The elements code_3a and fao_name (exposed through the FishSource API) have always the value null. FishSource team will add in their databases and expose it through the API.
- The element text (under the element state_of_marine_resource) contains a narrative text with various encoded html tags. FishSource responded that the text they expose is always html-based. FORTH will try to remove such tags.
- The information for management units are pour. It would be good if we could export more information about them. FishSource team will investigate creating a new API for exposing more information about management units.
- The datafile element contains an ID that refers to the actual data. These data are exposed through the Datafile API that FishSource has provided. We can use it for public use, however the resource contains the results in JSON format. Since JSON format might be restricting, FishSource team will investigate removing the restricting issues (on their portal) so that we can include a publicly available URL pointing the actual XLS sheets with the data, through GRSF.
- Scientific_advice is missing. FishSource team will include it their APIs
- The Data owner is missing. As the data owner we can use the organization that actually provided the data. FishSource will include this kind of information in their APIs
- Reporting year is empty. FishSource does not record that kind of information, but reporting dates are reported through the DataFile API. FORTH will use the last_update_date which is reported by FishSource team and refer to the date where a stock or fishery has been publicly added in the FishSource database.
- Reporting entity is empty. FAO mentioned that since this information is covered by RAM, it would be better to leave this information empty for FIRMS and FishSource.
- Assessment method is empty. FishSource does not store this information.
Follow-up actions
- FishSource to expose more information through the APIs (based on the above descriptions)
- FORTH to export new data after FishSource team updates the APIs
- FORTH to continue working on the modelling activities, the mappings and the construction of the 1st version of GRSF KB, based on the comments received
Materials
