| Day 0 of R3 Manifest Ingestion. Able to submit a manifest that is prepopulated with required data, including `id`s and successfully write the data via the storage service. Basic schema validation occurs. Basic `exists` checks occur for cited data. | Able to process `surrogate-key`s. Integration with the new [Schema Service](https://community.opengroup.org/osdu/platform/system/schema-service). Provide support for Dataset Registry (if available). Provide _hook_ for initiating Ingestion Workflows via published messages from the Storage Service. Integrated testing. | Pre-Release activities. Operational readiness. Solution hardening. |
## Milestone 3 ##
## Horizon 1 ##
(WIP)
This is our target for _Day 0 or R3 Manifest Ingestion_ (that is, the most basic functionality qualifying as Manifest Ingestion). Able to submit a pre-populated manifest with `id`s specified (vs. `surrogate-key`s) using the 1.0.0 version of the [Schema Manifest](https://community.opengroup.org/osdu/data/data-definitions/-/blob/1bdc6e43858d7f0202316135ee4b9a943a26e297/Generated/manifest/Manifest.1.0.0.json) to the Ingestion Service API endpoint.
...
...
@@ -84,7 +84,4 @@ Able to submit a pre-populated manifest to the Ingestion Service with support fo
## Milestone 5 ##
(WIP)
This is a stretch goal. The hope is to converge the four ingestion workflow streams into some common components to unify how data is ultimately written. The four ingestion workflows are Energistics (e.g., WITSML), EDS (External Data Sources), CSV, and Manifest. Each workstream is composing DAGs to execute within the Ingestion Framework and each workstream has DAG Operators performing common functionality. Ideally, the DAG operators are composable and reusable.
- Additional details TBD
Placeholder
\ No newline at end of file
The file Milestone will focus on solution hardening, operational readiness, pre-release activities, and other carry-over items as they are identified.
