StocksAndFisheriesKB

@amorim.patricia@gmail.com @susana.segurado@sustainablefish.org @merul.patel@sustainablefish.org @mmel@uw.edu

Dear FishSource and RAMLDB colleagues, please find in the attached file "GRSF_RecordsReviewSFP-2021-07-30_RevFAO_17Dec2021.xlsx" 32 records for your kind review and action (please see columns K, L). Mostly, it is matter to provide a feedback to our suggested actions or to amend area codes into your systems.
We stand ready to assist should you require any clarifications.
Thanks
Aureliano

Dear @aureliano.gentile@fao.org

Thanks for this. We will proceed with (most of) the corresponding actions immediately.
More specifically, we will move on with the records that require Approve, Merge and approve, Archive, Delete

As regards, the ones with proposed actions New Harvest and Re-Harvest , I suggest relying on GRSF Refresh workflow. So we could refresh the entire GRSF KB (and the corresponding VREs of course).
Refresh can be executed right away, or we could do it in the first days of January, when we will have the updated APIs from FishSource.
Let me know what you think.

Thanks Yannis,
I agree that the New Harvest and Re-Harvest records can be performed as soon as @merul.patel@sustainablefish.org confirms his work is completed according to what we discussed on area codes. (See minutes at https://support.d4science.org/projects/stocksandfisherieskb/wiki/21-12-02-GRSF_area_standards)
So, please, @merul.patel@sustainablefish.org indicate your expected schedule.

Yannis, what about deletions, do you want to wait as well? (fine with me in either cases). In this regard I here mention a recent email received by @susana.segurado@sustainablefish.org indicating:

... due to the change in the API we made earlier this year. Where we have biological stocks with multiple nested assessment units, as is the case for the NW Atlantic queen crab, we stopped exposing the biological stock, but instead started to expose each of the individual assessment units, which is aligned with the GRSF "stocks". There must have been several harvests done since then though.

What a nice Christmas gift! Thanks!

Regarding deletions, yes I think we remove the legacy records, and the new refresh in January will import any new ones.
I mean, this is the policy we designed by relying on the source databases, if they remove their records, then these are lost in the GRSF as well.
As per UUIDs logic, this may change in the future when the UUIDs are in use by third parties, but for now I think we can keep it "clean". And in any case it should be an archived records not a deletion.

Thanks again and best wishes!