57. Approval Workflow + Status Management

We are experiencing a real problem with the display and approval of records submitted for publication. Let me explain using the example of record FRESH-PEF60139. We received an email indicating that changes were made to this record by user Laurent BERTOLETTI. However, this record does not appear in the Admin Dashboard as “Pending Publication” but is shown as already published, with an archived version and a draft version.
First problem: The entries submitted for publication by contributors are not displayed as "pending approval" in the BO.
Next, when I look at the content of the published version of this same entry, I see that it contains the changes made without having been approved by us (as evidenced by the “Summary” field, which does not comply with our approval rules).
Second problem: records are published in the catalog without going through the admin validation process.
Specifically, no records in the BO appear as "pending validation," even though the dashboard indicates that 5 records have this status. However, when exporting the records as JSON from the catalog and via the API, there are indeed 5 records with this status—as shown in the "status" field—but they are not visible in the BO. Upon further investigation, we find a second field in these records related to the “IsImported” status, which is not present in the files sent on 02/18, nor in the model, nor added by Nada. Information regarding the import of a record should be in the “status” field, whose controlled vocabulary includes the “Imported” value. Third problem: records with the “pending validation” status are nevertheless published in the catalog and appear with the “published” status.
Fourth issue: A field named "FReSH" was added to the model without notifying us or explaining its purpose, and it overrides the "status" field—which is the one we had defined in the model.