The picture above depicts the conceptual architecture for the R3 Manifest Ingestion scope. Much of the complexity has been extracted for the sake of simplicity, but the picture hopefully illustrates the intent. We will define scope through the Definition of Done. In short, the following is considered _In-Scope_ for R3.
- Validate (Syntax and Content) and Process the contents of a [Manifest](https://community.opengroup.org/osdu/data/data-definitions/-/blob/1bdc6e43858d7f0202316135ee4b9a943a26e297/Generated/manifest/Manifest.1.0.0.json)
-Process the contents of a CSV file into OSDU
-Process the contents of Energistics standardized content (e.g., WITSML)
- Validate (Syntax and Content) and Process the contents of a [Manifest](https://community.opengroup.org/osdu/data/data-definitions/-/blob/1bdc6e43858d7f0202316135ee4b9a943a26e297/Generated/manifest/Manifest.1.0.0.json) into OSDU via the Storage Service. Errors and storage results are returned.
-CSV Ingestion: Present a Manifest file that references a CSV file. Process the Manifest and then trigger an Ingestion Workflow that performs additional processing of the CSV file
-Energistics Ingestion: Present a Manifest file that references an Energistics file. Process the Manifest and then trigger an Ingestion Workflow that performs additional processing of the Energistics file (e.g., WITSML)
### Definition of Done ###
This is a high-level definition of done for the R3 Manifest Ingestion workflow.
This is a high-level definition of done for the R3 Manifest Ingestion workflow. A more detailed [Definition of Done](https://community.opengroup.org/groups/osdu/platform/data-flow/ingestion/-/wikis/Manifest-Ingestion/R3-MVE-Manifest-Ingestion/R3-MVE-Manifest-Ingestion-Definition-of-Done) is found here.
- A process must present a well-formed and correct Manifest to the Ingestion Service endpoint for processing
- The Ingestion Service must support multiple, simultaneous calls and scaling as required to meet demand
