Ingested Submissions Status Report

The reporting tool is available on publication sites that use the EM Ingest feature. The feature allows authors to submit manuscripts via publishers' Author Portals (AP) and third-party Manuscript Service Providers (MSP).

This report can be used by Editor roles with permission to check the status of ingested submissions and details about any errors. A link to the report appears in the Administrative functions section of the Editor Main Menu.

The tool provides two search types:

Ingested Date: Limits results by the defined date range.
Zip File Name: Filters by the name of the submission zip file as applied by the AP or MSP. (File name must be provided by the MSP or the submitting author.)

To run the report:

Use the radio button to select search type.
Enter the search value:
- For Ingested Date, use the calendar tools to select opening and closing dates.
- For Zip File Name, enter the file name.
Click Submit.

Results page

The results grid identifies submissions by zip file name and a globally unique identifier (GUID).

Each record shows time stamp, zip file name, GUID, ingest status, and the four stages of the ingest process (indicated in green if the stage completed successfully, red if stage failed, gray if the stage has not started).

Status is indicated as Imported or Failed based on the completion of the first three stages. Submissions must be successfully imported before the PDF build stage can begin.

A View Details link opens a pop-up window that shows details of the four stages, each marked with an icon that indicates process status:

Red X: Failed
Green checkmark: Succeeded
Yellow checkmark: In progress
Blue ellipsis: Pending

Clicking the name of a process stage provides more information about the processing request results and details on the success or failure.

SFTP process: The first step prepares the submission file transfer from the MSP to EM. SFTP failures could indicate an issue with the MSP.
API process: The ingest API call pushes submission information between EM and the MSP. API failures could indicate an issue with the call.
Ingest process: The zip file containing the submission content and metadata is sent via SFTP from the MSP to EM. Ingest failures could indicate an issue with the zip file contents or an incorrect configuration in the publication’s EM site.
PDF build process: Once ingest is complete, a submission PDF is built in EM. PDF failures could indicate an issue with the PDF build process in EM.