- Met with Energistics and Data Load teams to ensure alignment
- Scheduled meeting with Microsoft
- Identified initial POCs to help establish a baseline [#Issue 24](https://community.opengroup.org/osdu/platform/data-flow/ingestion/r3-data-loading-project/-/issues/24), [#Issue 25](https://community.opengroup.org/osdu/platform/data-flow/ingestion/r3-data-loading-project/-/issues/25), [#Issue 26](https://community.opengroup.org/osdu/platform/data-flow/ingestion/r3-data-loading-project/-/issues/26)
-[Seeded initial ECCN content](https://community.opengroup.org/groups/osdu/platform/data-flow/ingestion/-/wikis/Manifest-Ingestion/OSDU-Manifest-Ingestion-Export-Control-Compliance)(more work to do)
**Dependencies/Blockers**
- Need developers to begin working POCs
- R3 Manifest Schema 1.0.0 still not approved
- Will begin with the current branch and change as needed
- File vs. Dataset approach still undecided
- Will proceed with File for now, but this will not meet AWS's needs
- Example data for Manifest Schema may be incomplete or not in full compliance with proposed schemas
- Will work with the Data Loading team to build complete examples