Skip to content

Download Exported Submission Files via File Staging

Once your submission export job has been successfully completed, you can download the files from file staging.

Before downloading the files, the following conditions must be met:

  • The submission export job must have been successfully completed.
  • The API user must have a permission set which allows the Application: File Staging: Access permission.

The exported submission is packaged in a ZIP file on file staging.

  1. Use Retrieve Submission Export Results to retrieve the location on file staging.
  2. Use Download Item Content to download files from file staging.

Vault writes two files to the job folder:

Vault writes the exported submissions to the job folder as an uncompressed directory structure, and Retrieve Submission Export Results returns the job folder path in file_path.

The export summary contains the following files:

  • manifest.csv - One row for each exported document, giving the document ID, document version, source file path, XML checksum, and submission metadata ID.
  • export-results.csv - A single row summarizing the job, giving the application name, submission name, sequence ID, document count, and the application and submission record IDs.

When a job generates warnings, for example because the Submission has Enable Continuous Publishing set to Yes, the archive also contains a warnings file listing them. Review these warnings before you rely on the exported package, since the dossier may be incomplete.

Learn more about the contents of the export summary in Exporting Submissions (RIM).

Vault returns export paths that begin with the user directory, such as /u724713/Submissions Archive Export/428589/nda216432-0000.zip. Admins pass this path exactly as returned. Non-Admin users omit the leading user directory and pass the path relative to their own directory, such as /Submissions Archive Export/428589/nda216432-0000.zip. Learn more in About File Staging Paths.