You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 reg_vessels) 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).
The text was updated successfully, but these errors were encountered:
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 reg_vessels) 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).
The text was updated successfully, but these errors were encountered: