Provide hook to Catalog information (ex: SeismicTraceData work-product component)
I envisage workflow such as create work-product, work-product component (SeismicTraceData), Dataset, FileCollection as needed for a SegY file. Currently, there is no such tool provided by OSDU Forum to create JSON files for this requirement. So, for now, let us assume that the Data Loader inspects the SegY file by using some open source tool and prepares the JSON files suitably.
Then when launching the conversion (SegY to oVDS), it should benefit from information as found from metadata in various OSDU Data Platform records as above.
Next, after successful conversion, it should also provide a link to the SegY file and declare the VDS file as its artefact (similar to oZgy flow).
Such as when SegY-to-zgy conversion is launched, it uses work-product and FileCollection as inputs.
"filecollection_segy_id": "odesprod:dataset--FileCollection.SEGY:dc-01oct-dataset:",
"work_product_id": "odesprod:work-product--WorkProduct:dc-01oct-wp:",
And after completion, work-product-component is updated with artefact information.
"Artefacts": [
{
"ResourceID": "odesprod:dataset--FileCollection.Slb.OpenZGY:481671525e464e9889290e250e2258be",
"ResourceKind": "osdu:wks:dataset--FileCollection.Slb.OpenZGY:1.0.0",
"RoleID": "odesprod:reference-data--ArtefactRole:ConvertedContent:"
}
],
cc - @mstormo , @ChrisZhang for information