GRSF-merging workflow¶
- Table of contents
- GRSF-merging workflow
This wiki page describes the workflow that is being followed for the merging of two or more records into a new one. We describe the workflow for merging stocks and fisheries. For each type of record, we identify which are the prerequisites that need to be met in order to move on with the merging, what are the consequences for all the fields of the record, and the concrete (technical) steps that are followed.
Terminology¶
- RUM: The Records Under Merging. They are the records that are selected to be merged into a new one.
- MR: The Merged Record. The new record that will be created from the information existing in RUM.
- DR: The Dominant Record. The record from RUM, that was used as the primary record when selecting others to be merged with it. In terms of the catalogue, it is the record that was used for triggering the merging (the one that was managed from the management panel).
Merging GRSF Stock records¶
Prerequisites¶
- The species in RUM should be the same (their classification system and code). If they are not the same, the merging can proceed if some of the species have an unknown classification system. If all the records under merging have an unknown system or they have different codes then the merging should be forbidden.
Fields¶
| Field | Description |
|---|---|
| Name | The name of the DR |
| Description | The concatenation of the descriptions of RUM, using ';' as a separator |
| Short Name | The short name of the DR |
| Status | The status will be set to pending |
| UUID | A new UUID will be generated for MR |
| Record URL | A new catalog URL will be created for MR |
| Type | if MR contains time-dependent information it is Assessment Unit, otherwise a Marine Resource (this can be changed afterwards) |
| Traceability flag | Use the traceability flag of DR (this can be changed afterwards) |
| SDG flag | Use the SDG flag of DR (this can be changed afterwards) |
| Referring Legacy Records | Use all the referring legacy records of RUM |
| Species | Use the species from RUM (using a standard classification system) |
| Semantic ID | Use the semantic ID of the DR |
| Assessment Area | Use all the assessment areas from RUM |
| Data Owner | Use all the data owners from RUM |
| Scientific Advice | Use all scientific advice from RUM |
| State of Trend | Use all state and trend information from RUM |
| Assessment Methods | Use all assessment methods from RUM |
| Assessor | Use assessor from RUM |
| Exploiting Fisheries | Use all exploiting fisheries from RUM |
| Similar Records | Use all similar records from RUM |
| Spatial Information | Calculate the new polygon based on the spatial information from RUM documented here |
| Citation | Generate a new proper citation based on the contents of MR |
| Time-Dependent Data | Use all the time-dependent data from RUM |
Workflow¶
- Fetch details about RUM from GRSF KB
- Check if RUM meet the prerequisites to be merged.
- Create MR 3.1 Fill information of MR based on the contents of RUM 3.2 Generate new UUID for MR 3.3 Calculate spatial information for MR based on the spatial information of RUM
- Ingest MR in GRSF KB
- Delete RUM from catalog
- Publish MR in the catalog
- Remove RUM from GRSF KB
- Update stock records having any of RUM in their similar records list to use MR
- Update fishery records having any of RUM in their exploiting stocks list to use MR
Merging GRSF Fishery records¶
Prerequisites¶
- The species in RUM should be the same (their classification system and code). If they are not the same, the merging can proceed if some of the species have an unknown classification system. If all the records under merging have an unknown system or they have different codes then the merging should be forbidden.
- The flag state in RUM should be the same (their classification system and code). If they are not the same, the merging can proceed if some of the flag sates have an unknown classification system. If all the records under merging have an unknown system or they have different codes then the merging should be forbidden.
- The fishing gear in RUM should be the same (their classification system and code). If they are not the same, the merging can proceed if some of the fishing gears have an unknown classification system. If all the records under merging have an unknown system or they have different codes then the merging should be forbidden.
Fields¶
| Field | Description |
|---|---|
| Name | The name of the DR |
| Description | The concatenation of the descriptions of RUM, using ';' as a separator |
| Short Name | The short name of the DR |
| Status | The status will be set to pending |
| UUID | A new UUID will be generated for MR |
| Record URL | A new catalog URL will be created for MR |
| Type | if MR contains time-dependent information it is Assessment Unit, otherwise a Marine Resource (this can be changed afterwards) |
| Traceability flag | Use the traceability flag of DR (this can be changed afterwards) |
| SDG flag | Use the SDG flag of DR (this can be changed afterwards) |
| Referring Legacy Records | Use all the referring legacy records of RUM |
| Species | Use the species from RUM (using a standard classification system) |
| Flag State | Use the flag state from RUM (using a standard classification system) |
| Fishing Gear | Use the fishing gear from RUM (using a standard classification system) |
| Semantic ID | Use the semantic ID of the DR |
| Fishing Area | Use all the assessment areas from RUM |
| Data Owner | Use all the data owners from RUM |
| Management Body | Use all management body information from RUM |
| Exploiting Stocks | Use all exploiting fisheries from RUM |
| Spatial Information | Calculate the new polygon based on the spatial information from RUM documented here |
| Citation | Generate a new proper citation based on the contents of MR |
| Time-Dependent Data | Use all the time-dependent data from RUM |
Workflow¶
- Fetch details about RUM from GRSF KB
- Check if RUM meet the prerequisites to be merged.
- Create MR 3.1 Fill information of MR based on the contents of RUM 3.2 Generate new UUID for MR 3.3 Calculate spatial information for MR based on the spatial information of RUM
- Ingest MR in GRSF KB
- Delete RUM from catalog
- Publish MR in the catalog
- Remove RUM from GRSF KB
- Update stock records having any of RUM in their exploiting fisheries list to use MR
