16-07-06 GRSF requirements¶
Meeting Notes
Topics: Requirements and specifications for UUIDs.
Participants: FishSource (Susana Segurado); RAM (Mike Melnychuk, Daniel Hively); FAO (Giulia Gorelli, Aureliano Gentile)
Notes
UUIDs (universally unique identifier) for the GRSF records¶
UUID examples prepared by FAO were introduced and discussed. They are stored at GRSF_UUIDs.xlsx (Worksheet "Examples") http://goo.gl/0RLZ8f
Following the examples review, several questions regarding the overall UUID logic were tackled. Details on questions and answers are stored at GRSF_UUIDs.xlsx (Worksheet "UUID_principles", all comments/answers are stored in blue)
- UUID components: Species Name, Area, Management Entity, Production System Type, Flag State, Fishing Gear
- UUID code: concatenation of available information in the UUID proposed fields (from the GRSF database) according to selected standards and agreed mapping rules.
- UUID labels: Two type of labels: 1) for the full title as the concatenation of the descriptive values of the UUID components and 2) for the short title inherited from the source of information (with FIRMS>FishSource>RAM order of priority) complemented with the type value. This mechanism implies that GRSF names are different from the original ones.
- The fields Species, Area and Management Entity can accept multiple entries, as in some cases it makes no sense to dissect these fields to identify single marine resources and/or single fisheries (there might be more than one management entity for the very same fishery and or for the very same stock). Other fields (Production System Type, Flag State and Fishing Gear) will be dissected to the minimal elements
- An amendment to Type values for stocks was proposed and accepted by participants. The new values are: "assessment unit" and "resource". The opportunity to add a new field containing information on whether the assessment unit/resource considered is also a biological stock (yes/no/not applicable) was discussed.
- Fishery types have not been deeply discussed but it is becoming evident that the main distinction is between fishery overall descriptions (FIRMS type=jurisdictional/fishery management unit/fishery resource) and fishing operations (FIRMS type=fishing activity).
- GRSF record labels: The group expressed preference for the proposal one which includes two fields: 1) for the full title as the concatenation of the descriptive values of the UUID components and 2) for the short title inherited from the source of information (with FIRMS>FishSource>RAM order of priority) complemented with the type value.
- The concept of proximity among records (fisheries and/or stocks that are somehow related) was introduced, and clear rules to identify and assign automatically a proximity should be identified as this will help the process of expert validation. The following values were suggested: "subset/superset/sibling". RAM has a flat list of records, without any indication of proximity.
- Competence questions were discussed. Further formulations will be made in the next call.
- Governance: FishSource stressed that we will need precise rules for validating (approve/merge/reject) the GRSF records. This topic will be discussed at a later stage of the project.
Follow-up actions
- RAM and FishSource to produce more examples of UUIDs.
- Two more calls are envisaged by the end of July to collect requirements on competency queries and CMS.
Working files
- Details and further comments are stored in: GRSF_UUIDs.xlsx (Worksheet "Examples"; Worksheet "UUID_Principles", all comments/answers are stored in blue) http://goo.gl/0RLZ8f GRSF_MinimumDataRequirements.xlsx (Worksheet: MinimumDataRequirement_May2016) http://goo.gl/DizvHa