Ensure consistency between Catalog data (work-product component WellLog) and bulk data input (Curve values)
Refer to this request
POST /ddms/v3/welllogs/{record_id}/data
- What if WellLog wpc mentions 4 curves (in array) and bulk data input mentions 6 curves (6 being > 4)? How does the API request react?
- What if WellLog wpc mentions 2 curves (in array) and bulk data input mentions 2 curves (but names mismatch)? How does the API request react?
- What if WellLog wpc mentions depth interval 10-100 ft and bulk data input mentions depth interval 50-200 ft.? How does the API request react?
- How does bulk data input API react if input data has irregular sampling rate? Ex: index1=10.0ft, index2 = 10.5 ft, index3=11.0 ft, index4=12.0 ft (off), index5=12.5 ft.
- What if sampling rate mentioned in catalog data (work-product component) is different from what is being provided during bulk data input?
Initial response from @DDahan
- We do not check for consistency between meta and bulk data.
- For sampling rate, we have no constraints (regular or -irregular sampled is working). Today we work with the index, hopefully in the future we will work with the reference values.
I am creating the issue here for tracking purpose.
Dror has suggested that
I think if we are to do it, it needs to go through some discussion\validation of our users community.
So, we plan to hold a meeting with User Representatives to decide way forward.
cc - @chad for information (since he is developing LAS-to-Wellbore-DDMS parser for loading curve data
cc - @Jane , @doniger and @pq - for information (conformance with EA rules about DDMS)