feat: support filtering for warnings only on the review page

backend/docs/db/schema.sql

@@ -468,12 +468,17 @@ CREATE VIEW public.sequence_entries_view AS
     sepd.warnings,
         CASE
             WHEN (se.released_at IS NOT NULL) THEN 'APPROVED_FOR_RELEASE'::text
-            WHEN se.is_revocation THEN 'AWAITING_APPROVAL'::text
+            WHEN se.is_revocation THEN 'PROCESSED'::text
             WHEN (sepd.processing_status = 'IN_PROCESSING'::text) THEN 'IN_PROCESSING'::text
-            WHEN (sepd.processing_status = 'HAS_ERRORS'::text) THEN 'HAS_ERRORS'::text
-            WHEN (sepd.processing_status = 'FINISHED'::text) THEN 'AWAITING_APPROVAL'::text
+            WHEN (sepd.processing_status = 'PROCESSED'::text) THEN 'PROCESSED'::text
             ELSE 'RECEIVED'::text
-        END AS status
+        END AS status,
+        CASE
+            WHEN (sepd.processing_status = 'IN_PROCESSING'::text) THEN NULL::text
+            WHEN ((sepd.errors IS NOT NULL) AND (jsonb_array_length(sepd.errors) > 0)) THEN 'HAS_ERRORS'::text
+            WHEN ((sepd.warnings IS NOT NULL) AND (jsonb_array_length(sepd.warnings) > 0)) THEN 'HAS_WARNINGS'::text
+            ELSE 'NO_ISSUES'::text
+        END AS processing_result
    FROM ((public.sequence_entries se
      LEFT JOIN public.sequence_entries_preprocessed_data sepd ON (((se.accession = sepd.accession) AND (se.version = sepd.version) AND (sepd.pipeline_version = ( SELECT current_processing_pipeline.version
            FROM public.current_processing_pipeline)))))

backend/docs/plantuml/sequenceInitialSubmission.puml

@@ -21,7 +21,7 @@
 
         processing -> backend: Query initial/edited sequence data
         backend -> DB: Query initial/edited sequence data
-        backend -> DB: Set status from 'RECEIVED'/'HAS_ERRORS' to 'IN_PROCESSING'
+        backend -> DB: Set status from 'RECEIVED' to 'IN_PROCESSING'
         DB --> backend: initial/edited sequence data
         backend --> processing: initial/edited sequence data
 
@@ -34,14 +34,10 @@
                end note
         end loop
 
-        alt processed sequence data contain processing errors
-            backend -> DB: Store processed sequence data with errors
-            backend -> DB: set status to 'HAS_ERRORS'
-        else
-            backend -> DB: Store processed sequence data without errors
-            backend -> DB: set status to 'AWAITING_APPROVAL'
-        end
-         frontend -> backend: query processed sequence data with errors
+        backend -> DB: Store processed sequence data
+        backend -> DB: set status to 'PROCESSED'
+
+        frontend -> backend: query processed sequence data with errors
         frontend -> frontend: address errors and edit sequence data
 
         frontend -> backend: submit edited sequence data
@@ -56,7 +52,7 @@
     backend -> frontend: processed sequence data
 
     frontend -> backend: approve processed sequence data
-    backend -> DB: set status from 'AWAITING_APPROVAL' to 'APPROVED_FOR_RELEASE'
+    backend -> DB: set status from 'PROCESSED' to 'APPROVED_FOR_RELEASE'
 
 @enduml
 

backend/docs/plantuml/sequenceRevocation.puml

@@ -6,7 +6,7 @@
     frontend -> backend: wants to revoke already processed sequence
 
      alt accession exists and highest version is 'APPROVED_FOR_RELEASE'
-        backend -> DB: insert new version\nwith status 'AWAITING_APPROVAL' \nand ' is_revocation = true'
+        backend -> DB: insert new version\nwith status 'PROCESSED' \nand ' is_revocation = true'
     backend -> frontend: response with accession + new version number
     else
         backend -> frontend: response with error message
@@ -17,6 +17,6 @@
         backend -> DB: set status to 'APPROVED_FOR_RELEASE'
     else
         frontend -> backend: cancels revocation
-        backend -> DB: delete latest version \nof the sequence and Status \n'AWAITING_APPROVAL'
+        backend -> DB: delete latest version \nof the sequence and Status \n'PROCESSED'
     end
 @enduml

backend/docs/plantuml/statusChange.puml

@@ -18,17 +18,15 @@
     ' status states
     state RECEIVED
     state IN_PROCESSING
-    state HAS_ERRORS
+    state PROCESSED
     state RECEIVED
     state APPROVED_FOR_RELEASE
-    state AWAITING_APPROVAL
 
     ' actions
     state CREATING_SUBMIT as "entry with new accession\n will be created" #lightgreen;line:green;line.dotted
     state CREATING_REVISE as "entry with existing accession\n and incremented version number\n will be created" #lightgreen;line:green;line.dotted
     state CREATING_REVOKE as "entry with existing accession,\n incremented version number, \n and is_revocation=true will be created" #lightgreen;line:green;line.dotted
     state DELETION as "entry will be deleted" #IndianRed;line:red;line.dotted
-    state is_error <<choice>>
     state is_approved <<choice>>
 
     ' transitions
@@ -38,15 +36,12 @@
     CREATING_REVISE --> RECEIVED
 
     REVOKED_DATA --> CREATING_REVOKE : user initiates revocation
-    CREATING_REVOKE --> AWAITING_APPROVAL
+    CREATING_REVOKE --> PROCESSED
 
     RECEIVED --> IN_PROCESSING : preprocessing starts
-    IN_PROCESSING --> is_error
-    is_error --> HAS_ERRORS : data contain error(s)
-    HAS_ERRORS --> RECEIVED : user edits data
-    AWAITING_APPROVAL --> RECEIVED : user edits data
-    is_error --> AWAITING_APPROVAL : preprocessing successful
-    AWAITING_APPROVAL --> is_approved
+    IN_PROCESSING --> PROCESSED : preprocessing done, might contain errors that need editing.
+    PROCESSED --> RECEIVED : user edits data
+    PROCESSED --> is_approved
     is_approved --> APPROVED_FOR_RELEASE : user approves \nor automatic approval\n via 'release_directly'
     is_approved --> DELETION : user rejects