/
Catch Reports

Catch Reports

Owned by Vilhjálmur Hallgrímsson
Jan 12, 2023

The CRFM member states using TFM should be able to share catch reports with each other.

 

We intend to use FLUX format in the future. TFM format is sufficient for now.

The source tenant

  1. For each member state (source tenant), the data manager selects the landing records he wants to include and saves them as a named catch report.

  2. A data manager selects a TFM account whom he wants to share the catch report with and selects share.

  3. The system copies / create the records in the destination tenant.

Do we need to add a column for report id?

We need to analyse with the customer how granular the data in the report should be.

The destination tenant

  1. A data manager reviews the catch report that is in the state of submitted.

We should implement the approval process to support sending and receiving reports.

  1. The data manager accepts, rejects, or requires more info (according to the workflow states).

 

The level of granularity for the record depends on what the customer wants to achieve and the statistics he expects. The destination tenant will have to have all the:

  • species,

  • landing sites,

  • fishing zones,

  • gear,

  • Vessels

I doubt it will be needed to share a record on pr. vessel level but I think CRFM will probably want to know the catches pr. vessel class of gear class.

What happens when there is a new vessel or other new records from the source country and the record is not available in the destination tenant? Then we will need to Create that record in the destination tenant.

Technical

The sequences will not persist from the destination tenant to the source. One way of implementing this is to add one new column “Source_Tenant_ID“ which will store the source ID’s. This is how we can retain the record association from one table to another.