next up previous contents index
Next: Retrieve Up: Submit and Retrieve a Previous: Submit and Retrieve a   Contents   Index

Submit

Figure 11.3: Possible replies from the Archive upon a project submission: acceptance or rejection.
\resizebox{10cm}{!}{\includegraphics{images/ArchiveSubmitOk.eps}} \resizebox{10cm}{!}{\includegraphics{images/ArchiveSubmitFailed.eps}}

File $\rightarrow$ Submit Project will submit the currentproject and store it in the ALMA Archive, providing that it passesvalidation. During submission, a connection between your localplatform and the ALMA Archive is initiated and subsequently droppedopen the completion of the submission. During the actual submission ofthe project to the ALMA Archive, a progress bar will be visible andadditional submission attempts are notallowed. Figure  11.3 shows the two possible returnsfrom the Archive upon the submission of a project: Acceptance with anunique project ID number or a window stating that the submissionfailed.

If the project has not been submitted before, a new project with aunique project code will be created. If this is a resubmission of anexisting project, it will be updated. Therefore, resubmission of your project will overwrite the existing project in the ALMA Archive! For a genuine resubmission this does not cause anyproblems. However, it is extremely important to realise that if apreviously-submitted project is read back into the OT and almost everydetail of it changed, a subsequent submission will still overwrite the previous submission!

To prevent this happening unintentionally, a warning will be displayedat submission time to make it clear that you are about to overwrite anexisting ALMA project. The top of the Project Structure pane will alsofeature a prominent Submitted text field that should serve toremind you that this is a previously-submitted proposal. If you dowish to submit a separate proposal to ALMA for the same deadline, thenit must be created from scratch with e.g. the New Proposal icon inthe Toolbar, or by reading in a previously-submitted project as aread-only template where its contents can be copied over to aseparate, unsubmitted project.

The opposite problem also exists i.e. if you save a proposal justbefore submitting it and then subsequently reload it into the OT, editand resubmit, the lack of the various codes and identifiers that wouldhave been written in at submission time, will cause a completely newsubmission. We currently try to avoid this by, after a proposal has been submitted , bringing up a dialogue that asks you to savethe file to disk. The dialogue includes the Save button tolaunch a save dialogue. This problem can of course be avoided if editsfor resubmissions are only made to projects that have been retrievedfrom the ALMA Archive.


next up previous contents index
Next: Retrieve Up: Submit and Retrieve a Previous: Submit and Retrieve a   Contents   Index
The ALMA OT Team, 2011 May 20