Our current AIRR submission dialog uploads all data files, together with the corresponding MiAIRR instance, to CEDAR's submission server. When the upload is complete, the submission server generates the submission.xml file from the MiAIRR instance.
However, if the MiAIRR instance is structurally invalid, the generation of the submission.xml file will fail and therefore CEDAR will not be able to start the submission to NCBI. When uploading very large files to CEDAR, the upload may take several hours and then fail if the generation of the submission.xml file is not successful.
Suggested solution: check if the metadata are valid and generate the submission.xml file before uploading the files. If the metadata are invalid, notify the user using a clear message instead of the current "Oooops" message (see below).
Our current AIRR submission dialog uploads all data files, together with the corresponding MiAIRR instance, to CEDAR's submission server. When the upload is complete, the submission server generates the submission.xml file from the MiAIRR instance.
However, if the MiAIRR instance is structurally invalid, the generation of the submission.xml file will fail and therefore CEDAR will not be able to start the submission to NCBI. When uploading very large files to CEDAR, the upload may take several hours and then fail if the generation of the submission.xml file is not successful.
Suggested solution: check if the metadata are valid and generate the submission.xml file before uploading the files. If the metadata are invalid, notify the user using a clear message instead of the current "Oooops" message (see below).