Avoid proliferation of Storage service/records from DDMS
Currently, we see way to create standard Master and work-product entities from this DDMS-specific service.
ex: Master data "Well" POST {{baseUrl}}/ddms/v3/wells
ex: Work-product component "WellLog" POST {{baseUrl}}/ddms/v3/welllogs
What is the problem in leveraging proven ways of creating wks Master/wpc entities? The benefits are -
- Avoid additional source code for long term maintenance.
- Leverage features like integrity check as provided by Manifest-based Ingestion.
Niche services such as I/O of well log curve data, Well trajectory station data, Well log recognition - are all very much welcome.
copying @gmarblestone , @chad and @todaiks for information.