Calipseo is FAO web- based platform for national Fisheries Authorities to streamline management of fisheries data and the production, analysis and reporting of fishery statistics.
1
stars
0
forks
source link
[CALR-73] Vessel QA - Add tab on vessel characteristics #73
Issue migrated from JIRA: https://sdlc.review.fao.org/jira/browse/CALR-73
Creator/Reporter: Emmanuel Blondel @eblondel
Assignee: Brian Ojok @brianandy
Priority: Medium
Status: Done
Date of creation: 2022-04-05T06:52:20.000+0000
For many vessels we miss one or more vessel characteristics. In the same spirit of CALR-71, the objective is to add a vertical tab 'Vessel characteristics', in which we can have a comrehensive table that counts vessels with missing vs. available characteristic.
Instead of having 1 table by characteristic, let's try to have a single table.
First column is the 'Action' -> To complete (with exclamation mark icon, in orange), vs Completed (with check icon, in green)
Then, one column per characteristic (see corresponding columns in _regvessels) with the counting:
LOA
DRA
GT
SPEED
POWER
Column names to be i18n-enabled. For the english vocab terms, you can re-use the above names.
The output should then look like this:
||Action||LOA||DRA||GT||SPEED||POWER||
|! To complete|xxx|xxx|xxx|xxx|xxx|
|✔ Completed|xxx|xxx|xxx|xxx|xxx|
For simplicity, you can stick with handling separate SQL queries per characteristic (to ease the counting SQL side).
For many vessels we miss one or more vessel characteristics. In the same spirit of CALR-71, the objective is to add a vertical tab 'Vessel characteristics', in which we can have a comrehensive table that counts vessels with missing vs. available characteristic.
Instead of having 1 table by characteristic, let's try to have a single table.
First column is the 'Action' -> To complete (with exclamation mark icon, in orange), vs Completed (with check icon, in green)
Then, one column per characteristic (see corresponding columns in _regvessels) with the counting:
Column names to be i18n-enabled. For the english vocab terms, you can re-use the above names.
The output should then look like this:
||Action||LOA||DRA||GT||SPEED||POWER|| |! To complete|xxx|xxx|xxx|xxx|xxx| |✔ Completed|xxx|xxx|xxx|xxx|xxx|
For simplicity, you can stick with handling separate SQL queries per characteristic (to ease the counting SQL side).