SOTS data issues

[leonardolaiolo]

From Claire:
@sedgar

bgc_phyto_raw : Please can you change the conditions on this so the constraint incudes method. i.e. Trip_code, taxon_name, method should be unique. This will allow these records to go through, this is real and wanted. This is from the SOTS data which is analysed in 2 ways and the same taxa may occur in either sample. I had not envisaged this as it would not happen for other projects.
Please can you add a condition that sampleDepth_m cannot be null in any table in which it occurs. Not the depths in the BGC_trip, these can be zero.
Is it possible that when these fail that I get notified?

@sedgar to make the changes and update AODN.

@leonardolaiolo

You may also have to change the constraint conditions, add method, on harvesting the bgc_phyto_raw to allow these records to go through, they are correct.

Possibly methods needs to be added to all the SQL code, to make sure rows will be unique in the views created. It needs to be tested in stack as it could cause issues with the pivoting.

---

Workflow to solve this should be:

1. @sedgar to make required changes
2. @clairedavies to add back some of the SOTS data
3. @leonardolaiolo to update SQL, test and promote to production