Optimise the data submission/upload routine

[Osanna123]

Presently, the submissions are following the given steps:

• submitter screens the file and receives a screening report (ICES receives an e-mail)
• submitter presses the submission button on the screening report (ICES acknowledges online and ICES receives an e-mail about that the submitter wants to upload data (with sessionID))
• ICES gather sessions that need to be submitted, provide report (and files) to the WGDEC chair(s) for approval
• ICES makes manual registry in the accessions
• ICES makes manual data upload

// 3 last steps should be automated as much as possible

Submission acknowledgement:

[Osanna123]

@cmspinto and @Osanna123 meeting today on the issue.
agreed new steps of the procedure:

1. Submitter prepares, screens their file, presses the button to submit data --> David and we get an email notification; the submission is registered in AIMS; DATSU tables are copied into temp tables in VME DB.
2. David can log in to an interface, where he can see new submissions and download the files (check with David what format they should be, make a respective view).
3. David should have two buttons: 'Reject the submission' and 'Approve for upload'.
   the first button 'Reject the submission' should give him an option to send a customized email to the submitter.
   the second button should give a message to anna/accessions to make the final upload (this is a temporary solution, to see how the old data are resubmitted).
4. Anna checks if it's a resubmission, partial, etc, and uploads (with what interface?). The upload is automatically registered with the AIMS and filearchive.

The implementation steps would be for us to check with David if this new procedure would be optimal (especially points 2 and 3) within the next 3 weeks, and then we arrange regular sprints.

[Osanna123]

test before closing