The Ingest report contains information about a single job that Ingest has completed. The report includes an overview which gives some high level information about the job. The details section of the report includes information about the individual files. The overview section of the report. This section contains information about the job and totals of the items processed. The details section of the report. This section contains information about the individual files and item errors. The data center ID of the provider that submitted the job. The Ingest generated unique id of the job. This ID can be used to coordinate with an ECHO Operator in the event that follow up information is required. The date that the report was generated. This may differ from the job date if the report is regenerated at a later time. The root element of the Ingest report file. A list of files. A single file. A file that was processed as part of the job. The total counts of the collections, granules, and browse images processed based on the action performed. Any file level errors that occurred while processing the file. If there was a critical file error, there may be no item errors reported. Groups of item errors. The item errors will be grouped by their error code. The name of the metadata file in the job. This will be the name of the original metadata file from the provider even if the job required adapting from an older Ingest format. The overview section of the report. This section contains information about the job and totals of the items processed. Any errors that occurred at the job level. Job errors indicate that the entire job may have been rejected for some reason. If a job error occurs, detailed information on the files in the job may not be available. The total counts of the collections, granules, and browse images processed based on the action performed. The date that the job started. This is normally when the input files were first detected and the job was queued for processing. The date the job completed processing. This date is assigned prior to the report being generated. The name of the job as assigned by the provider. This element may not occur if the provider did not supply a job name. A job name is normally taken from the original package name when a package is delivered. The job name may also come from the name of the of the zip file if the job was delivered by the package delivery mechanism. The sequence number of the job. This element may not be present if the job was not sequenced. This contains item count totals for collections, granules, and browse images. The total counts of the collections processed based on the action performed. The total counts of the granules processed based on the action performed. The total counts of the browse images processed based on the action performed. The total counts of the items processed based on the action performed. The totals are calculated from the final files that are processed. Therefore the totals may not match the totals expected from metadata files that require provider specific adapting. In order to make use of the processing totals, the latest Ingest schema should be used when delivering data. The total number of items processed which is simply the sum of inserted, replaced, updated, deleted, and rejected. The number of items inserted. The number of items replaced. The number of items updated. This will match the number of targets in partial adds or deletes in the metadata file. If a the same item is listed in different partial adds then it may be counted multiple times. The number of items deleted. The number of items rejected. The number of metadata verifications performed. An insert or replace resulting from a metadata verification will also be counted in the corresponding processing count. The number of inventories that were checked for existence in ECHO. The details section of the report. The details includes the files processed and any errors that occurred in the file. The files that were processed as part of the job. An error that can occur during the processing of a job or with metadata files. A free text message that describes the error and gives more details. The format of this message may change and it may contain embedded information specific to the error context. The level of the error. A warning is considered an information error that does not prevent Ingest from completing the requested action. A critical error indicates that the action could not be completed. The error code associated with the error that occurred. The error code can be used to locate similar errors or communicate with ECHO Operations. An error that can occur during the processing of a job or with metadata files. A free text message that describes the error and gives more details. The format of this message may change and it may contain embedded information specific to the error context. The level of the error. A warning is considered an information error that does not prevent Ingest from completing the requested action. A critical error indicates that the action could not be completed. The error code associated with the error that occurred. The error code can be used to locate similar errors or communicate with ECHO Operations. The level of the error. Critical errors indicate that the action could not be completed. Warning errors provide information but indicate that the action did complete. This is a defined list of the errors with a code that can occur in ingest. Indicates that the manifest file was corrupt and not readable. Indicates that the manifest file was not found in the package. Indicates that required files were missing from the package. Indicates that extra files were in the package that were not listed in the manifest. Indicates that the package was corrupt and not readable at the zip level. Indicates that the package contains too many files to be processed. Indicates that the sequence number is less than the last sequence number and it is therefore a duplicate. Indicates that the job was deleted by an operator and therefore did not complete processing. An input file in the job was invalid. This only applies to BMGT providers. This is a defined list of the file errors with a code that can occur in ingest. The file failed full schema validation. This is more restrictive than structural validation. The file failed structural schema validation. This checks that the element that appear are correctly named and in the right order. It ignores type validation. Ingest was unable to parse an input time in the file. The file failed dtd validation. The input adapter encountered something that was not expected. The input adapter encountered an invalid XPath in a partial metadata update file. Ingest was unable to determine what kind of file this was. An error that applies to a single metadata item. A free text message that describes the error and gives more details. The format of this message may change and it may contain embedded information specific to the error context. Note: the message is is restricted to 1024 characters, and the message may be a truncated version of an error message if the original error message exceeded 1024 characters. The level of the error. A warning is considered an information error that does not prevent Ingest from completing the requested action. A critical error indicates that the action could not be completed. The item's ID which will be different depending on the item type: granules use Granule UR, collections use DataSetId, browses use Browse ID. In a few cases, such as partial add, partial delete, and delete, the item ID may be different if the normal ID isn't available. For example, if a collection delete containing only short name and version is being processed but the collection does not exist, the data set ID is not available for the item error. The The type of item that had the error. A list of item error groups. A single item error group. A group of item errors. The item errors are grouped based on their error code. A single item error. The error code that applies to all the item errors in this group. The actual item errors contain the detailed message about the particular error. A list of ingest file errors. A single file error. A list of ingest job errors. A single job error. This entity a metadata item type handled by ingest. GeneralErrorCode - General item errors that can occur on all metadata item types. This is returned whenever the item failed schema validation. These describe different validation errors that could occur while validating a collection. The names of the algorithm packages given must be unique. The names of the associated difs given must be unique. The names of the collection associations given must be unique. The names of the contact roles given must be unique. The names of the CSDT descriptions given must be unique. The names of the additional attributes given must be unique. The names of the instrument characteristics given must be unique. The names of the platform characteristics given must be unique. The names of the sensor characteristics given must be unique. The names of the instruments given must be unique. The names of the platforms given must be unique. The names of the sensors given must be unique. The short names of the campaigns given must be unique. The URLs of the online access urls given must be unique. The last update date of the collection is prior to the existing record's date. The collection indicated does not exist. The collection's spatial region is invalid Additional attributes with child granule references cannot be deleted. Platforms with child granule references cannot be deleted. Instrument with child granule references cannot be deleted. Sensors with child granule references cannot be deleted. Instrument characteristics with child granule references cannot be deleted. Sensor charactertistics with child granule references cannot be deleted. Campaigns with child granule references cannot be deleted. Granule Spatial Representation cannot be modified. Collection temporal information cannot be deleted or modified when it invalidates temporal information for existing granules. The combination of long name and version id must be unique per provider. The combination of short name and version id must be unique per provider. The additional attribute violates data validation rules. There are TwoDCoordinateSystems with the same name in a collection. A Two-d coordinate system was being deleted from a collection that had granules referencing it. A Two-d coordinate system was invalid in a collection. A metadata field in a collection did not match the metadata from the provider. A collection is in ECHO that should not be according to the provider. A collection was not found in ECHO but should be according to the provider. These describe different validation errors that could occur while validating a granule. The additional attributes given must be a subset of their associated collection's Additional Attributes by Name. The additional attribute values given must be valid according to the associated collection's Additional Attributes. The campaigns given must be a subset of their associated collection's campaigns. by Name. The names of the campaigns given must be unique. The names of the measured parameters given must be unique. The names of the platforms given must be a subset of their associated collection's platforms. by Name. The names of the platforms given must be unique. The names of the instrument characteristics given must be a subset of their associated collection's characteristics. The names of the instrument characteristics given must unique per instrument The temporal given must be in the range of it's collection's temporal. The names of the instruments given must be a subset of their associated collection's instruments. The names of the instruments given must be unique per platform. The names of the operation modes given must be a subset of their associated collection's operation modes. The names of the sensors given must be a subset of their associated collection's sensors. The names of the sensors given must be unique per instrument. The names of the sensor characteristics given must be a subset of their associated collection's characteristics. The names of the sensor characteristics given must be unique per sensor. The granule's spatial region is invalid. The granule spatial representation must match the granule spatial representation specified in the parent collection. The URL of the online access urls given must be unique. The two-d coordinate system refers to a non-existent collection two-d coordinate system. The two-d coordinate system is not valid based on the collection's two-d coordinate system. The granule indicated does not exist. The last update date of the granule is prior to the existing record's date. The collection referenced by the original collection is different than the collection referenced by the new collection during a granule update or replacement. Moving granules from one collection to another is not supported. The referenced parent collection does not exist. The referenced field for deletion does not exist. The referenced update target field does not exist for the specified element. The referenced update target does not exist. No changes were found in the referenced update target. No changes were found in the referenced field for update. A metadata field in a granule did not match the metadata from the provider. A granule is in ECHO that should not be according to the provider. A granule was not found in ECHO but should be according to the provider. BrowseErrorCode - These describe different validation errors that could occur while validating browse metadata. The last update date of the browse image is prior to the existing record's date. Browse image file names must be unique. The file size supplied does not match the actual image file size. The browse image indicated does not exist. A browse image file is required but was not found or supplied. The URL for a browse image is malformed. A browse is linked to a collection or granule in ECHO that should not be according to the provider. A collection or granule browse link was not found in ECHO but should be according to the provider. A referenced collection does not exist.