File Ingestion
This User Story covers OSDU initial file load scenario. It can be split into 2 sub user-stories:
1. Generic File Ingestion - no schema-specific metadata is ingested.
In this case we upload file to the File Storage only with generic file metadata (e.g. Date Created, Author, Legal Tags etc)
This user story covers the following business scenarios:
- File cannot be parsed, but we want to upload it into OSDU
- Schema for this data is not ready yet, file can be uploaded into OSDU and later schema can be enriched
Pre-conditions
None
Acceptance criteria:
- Searchable (by file name, *)
- Available for Delivery API (as a file)
- Schema is not connected
- Registered in the Compliance Catalogue
Questions:
- Do we upload a file with a Manifest file or without Manifest file?
2. File Ingestion - schema-specific metadata is ingested.
Some file attributes are parsed and corresponding schema is created in OSDU.
Pre-conditions
- Schema that has to be populated with data from the file exists in OSDU
Acceptance criteria:
- Searchable (by file name, *, attributes)
- Available for Delivery API (as a file, as attribute data with reference to the Schema)
- Schema is connected - what does it mean?
- Registered in the Compliance Catalogue
OpenDES supports both these scenarios