Project

General

Profile

GRSF ยป

20 September 2019 Towards GRSF pilot release

Meeting Notes

Participants:

FishSource (Susana Segurado, Marina Mendes, Merul Patel)
FAO (Anton Ellenbroek, Aureliano Gentile, Bracken van Niekerk)
FORTH (Yannis Marketakis)

Main topics

  • New data harvest
  • Upgrade FishSource APIs
  • stocks approval logic

Notes

Ms Susana raised the following questions which were discussed by the group. See follow-up section for wrap-up or final decisions.

1- When is the next harvest? Could we agree a time towards the end of October

2- We have 6 stock trees to fix which were identified by incorrect GRSF matches. These are documented in our internal redmine (#15428) and the expected time to complete is 2 weeks.

3- We also have two IT tickets that we can close next week (#15557, #15554). These will allow us to export two additional fields for each Organisation related to a Management Unit:

A.
Geographical coverage: a string indicating whether the Organisation is an International, National or Subnational entity.

B.
ISO2, eg: US-MS for Mississippi

These would require modification of the harvesting logic, but would then allow more accurate semantic identification for the Management Unit portion.

4- The API changes will also lead to removal of the state_of_marine_resource and scientific_advice sections from the main Stocks endpoint now, since that increases the execution time.

We propose to add a separate endpoint for these, which we can also implement before the end of September

5- With regards to ongoing approval of GRSF records, is there funding available for a contractor to be appointed to carry out this work for data from all providers?

6- We were not approving Marine Resources, pending a decision on their structuring. It seems you are approving those from FIRMS though.

Follow-up actions

1- New API code changes (v5) expected in the next 2 weeks, the 4 October 2019 as a deadline, which will provide enough time for the new data harvest before the International Symposium on Fisheries Sustainability on the 18 November 2019.

2- This to be resolved by FishSource by the 4 October 2019, which can then be approved and connected with the Assessment Units.

3- This is not only a technical problem, however there are no foreseeable issues. It is also a question of standards and how the logic for the semantic identifier will be changed. The group concurred with the following draft standard:

in case of Sub-national authorities the semantic identifier will be populated with "authority:Sub-Nat:XXX" where XXX is the ISO2 of the country plus the iso2 of the state or other subdivision. Example: authority:Sub-Nat:US-MS (USA - Mississipi)
The choice of Alpha-2 code - Alpha-2 code is recommended by ISO2 https://www.iso.org/obp/ui/#iso:code:3166:GB
GRSF standards will be updated accordingly

4- Agreed. This will imply 2 iterations for FORTH.

5- Not currently, beyond the current support offered by the FIRMS Secretariat, the FishSource and the RAM colleagues, Mr Takayuki Hagiwara (previously worked for RAM at the University of Washington) can be approached with specific tasks on subsets of FishSource records.

A point was raised on dominant records when performing merges: The record with a standard code is to "dominate" over the record with the non-standard code when merging. The unknown codes are retained in the GRSF page, but are not a part of the semantic identifier. Currently, records are being merged when there is a clear match, with partial potential matches being reviewed further in more detail.
Suggestion is to create an Excel file for these potential matches, with priority given to the fishery records.

The issue of a conflicting number of merged FishSource records to be addressed and further investigated with FORTH.

6- Marine Resources Type - the group concurred to focus on the Assessment Units. Current approved Marine Resource records may need to be investigated and will most likely change type. We leave Marine Resource records as Pending for the meantime, to be addressed during the next phase of development and content updates.

Resources

Add picture from clipboard (Maximum size: 8.91 MB)