Sources other than segy require an alternate ingest flow
Sources other than segy require an alternate ingest flow. Conversion within data platform containers may lead to scalability issues when very large seismic datasets must be converted, or large numbers of volumes must be converted in parallel, potentially also requiring an alternate ingest flow.
a. A seismic dataset that comprises a dataset--FileCollection.Bluware.OpenVDS:1.0.0 can be created by using the underlying Seismic DMS APIs, together with client-side use of Bluware libraries and utilities. This approach requires orchestration of the required steps by the client of the Seismic DMS, for which an orchestration utility is likely helpful.
b. The current data definition for dataset--FileCollection.Bluware.OpenVDS:1.0.0 provides for inclusion of each object within the FileCollection within the FileCollection’s metadata in the DatasetProperties.FileSourceInfos array. However this approach leads to scalability issues for large FileCollections, which could include tens or hundreds of millions of objects, resulting in resource constraints when attempting to serialize and/or parse a single json object that lists them all.
Related to #13.