Clarify logic about creation of associated Master data when FETCH obtains work-product-component from External Data Sources
Take the example where Operator BigOil's EDS Fetch process obtains a work-product-component (WellLog) from Data Subscription company XYZ.
Here there is a reference to Wellbore ID. "WellboreID": "srn:master-data/Wellbore:XYZ-name-Wellbore-WB-04:",
It is expected here that BigOil's "EDS Fetch" will also obtain mete data about Wellbore "XYZ-name-Wellbore-WB-04".
The complementary INGEST process may create that at BigOil's OSDU and expect "Enrichment" process to handle this eventually.
Several possibilities exist -
- New wellbore needs to be created at BigOil end as nothing exists for this
- Need to match (merge) with existing wellbore at BigOil end even if names can be different such as BigOil-name-Wellbore-WB-04"
- Some Operator may decide to leave the wpc entry as "orphan" even without doing proper association to Wellbore
But the key point is a requirement around the FETCH process (part of EDS' key fetch-and-ingest workflow) is to bring forward associated data at the time of fetch of work-product-component. Except for third option as above.
For Welllog, Marker, Trajectory - this is Wellbore For Seismic Trace this can be Acquisition project, Processing project, 2D/3D Interpretation project.