26 march 2019 GRSF pilot release, towards FIRMS Steering Committee meeting (Rome, FAO headquarters 13-14 May 2019)¶
Meeting Notes
Participants:
CNR (Pasquale Pagano, Luca Frosini, Francesco Mangiacrapa)
FAO (Marc Taconet, Anton Ellenbroek, Aureliano Gentile)
FORTH (Yannis Marketakis, Nikos Minadakis)
Main topics
- Refresh the GRSF KB with the latest fixes and content updates - how should we proceed, do we have enough time before the FIRMS meeting? (Also to address the duplication of records/missing data, FishSource and FIRMS updates, etc.)
- Bulk approval of new records
- Publish GRSF records in the CKan catalogue - short and medium term actions to improve this part of the workflow
- Manual merge of records
- Citation mechanism
- Table of contents
- 26 march 2019 GRSF pilot release, towards FIRMS Steering Committee meeting (Rome, FAO headquarters 13-14 May 2019)
Notes¶
Refresh the GRSF KB¶
- FORTH is suggesting that for the pilot release is safer to update records rather than republish. Any new data harvest and republish thus inheriting all the bug fixes made recently will take place after May. Approved records UUIDS will be retained in any new data harvest.
- Updating records are for the following tickets:
#16281 SFP fishing gears (426 records to be update)
#12421 accented words, the ticket will be updated by FAO with the most common accented words or characters in FIRMS stocks and fisheries so to facilitate the understanding of how many records need to be updated
#16275, #13250, #13160 Management authority is missing or the semantic identifier does not contain the ISO3 country code (to which the authority belongs to)
#13289 FishSource marine resource vs assessment unit, FishSOurce exposes this info in the subservice and it should be taken into account to assign the GRSF record type
#13301, #16223 Missing data or redundant, FAo to check and to identify what is still missing
- FAO and FORTH will have a call to discuss priorities to all tickets assigned to FORTH
Bulk approval of new records¶
RAM and FishSource are providing criteria or list for approving new records in bulk mode. How should we proceed?
FORTH confirmed that upon specific criteria the bulk approvals can be performed. But not with list based only on GRSF name without UUIDs.
The criteria to further approve RAM record is the following:
RAM records, with type assessment unit, without similar records. (350 records, see https://support.d4science.org/projects/stocksandfisherieskb/wiki/GRSF_validation_plan#Validating-and-approving-RAM-records
attachment:ApprovalProcessGroup1.xlsx) Ticket will follow.
During the discussion it also turned out that a download/export facility for CKan search results would facilitate the reviewer and users to "consume" GRSF records. A ticket has been cretated to that goal: #16372
Publishing in Ckan catalogue¶
CNR reported the development of new services GCat and GFeed which can serve the GRSF. GCat is a new publishing service while GFeed is an harvester with a plugin. These new services will perform queries in the KB and update the catalogue thus leading to a new architecture with an impact on FORTH development.
GCat is in a test phase in another project and could be in production within two months or so. GFeed will be completed after the summer and likely could be used by the GRSF in six months or so.
FORTH expressed interest and appreciation for new tools which better tackle performance and scalability issues. FORTH is available to join the upgrade.
There is a concern on the current publishing workflow from the GRSF KB to the CKan Catalogue. A solution is needed to avoid uncertainties/incorrect data in the results as well to drastically reduce the effort needed.
If the GRSF will be positively received at the FIRMS meeting, then specific effort can be allocated in 2019 to such development beyond the project opportunities Blue Cloud - Food cloud.
It was clarified the distinction of SLAs for operations vs. projects or specific arrangements for developments of new features.
Synchronization of efforts has been recalled to make CNR and FORTH interventions as efficient as possible.
Development of the manual merge of GRSF records¶
- #12277 FORTH clarified that it is an action on their side to complete. The service to check periodically the merge requirements is already in place, what is missing is the merge action in the KB which need to be developed. CNR will be involved at later stage if needed.
Complete the citation mechanism¶
FORTH is available to complete the development but asking FAO to give details on what is missing or not working.
FAO to make a new ticket and report the GRSF citation template and what is currently missing/not working.
#12278 that ticket is mostly focused on missing creation date which is an issue of FIRMS source records.
documentation for the citation is available at
GRSF Wiki: GRSF_database_overview
Google Doc: https://docs.google.com/document/d/1W7-GSTLFL28bZ8ejJC3O8Bi47kWIvvPCNCq5HCVv0SE/edit?usp=sharing
Follow-up actions¶
Further to tickets, in particular these are the actions identified during the call:
FORTH and FAO to have a call to assign priorities to tickets assigned to FORTH, so as to identify what can be done by the end of April
CNR to interrogate the CKan with selected accented words or characters
FAO to test the real-time publication in the GRSF VRE once a record is published in the GRSF Admin VRE
FAO to make a ticket for RAM bulk approval #16375
FAO to make a ticket on citation template and highlight what is missing #16377
FAO to provide examples of accented words and characters for encoding issue. See ticket #12421
Resources¶
