Postman Collection and parquet file sample - observations
@Mykhailo_Buriak and @Kseniya - I thought it is best to create issue here as needed. Would be easier for tracking. cc @bdawson and @Siarhei_Khaletski
This refers to your recent artifacts here https://community.opengroup.org/osdu/qa/-/tree/main/Dev/48_CICD_Setup_RAFSDDMSAPI
Thanks for using IDs as per Kentish example. Page 453/1082. Wellbore KKS1, Coring ID KKS1-Core1, Rock Sample ID - KKS1-Coreing1-Sample-10A, Rock Sample analysis wpc ID=Test The RSA wpc record shows depth of 2423.26, density of 2.643, permeability of 4410 and porosity of 35.7.
Rock Sample Analysis Request-03 (Add data - parquet) - Sample parquet file in this folder does not show matching data. 3 rows. Depths 346m, 10m, 19999m. Grain Density 1.3, 1.3, 1.31.
Rock Sample Analysis Request-04 (Add data - JSON) - payload here is not matching with Rock Sample ID record Test 3 rows. Depths 346m,10m, 19999m. Grain Density 1.30, 1.30, 1.31. JSON payload does match content of sample parquet file, as far as I can tell. So, that is good.
Some general questions/comments -
- Will numerical data in DDMS optimized content match single Rock Sample Analysis record?
- Will numerical data be duplicated from actual metadata (what is in the record of Rock Sample Analysis wpc)?
- Add data request refers to single record of Rock Sample Analysis. Do we not expect many-to-1 from Catalog record into Optimized content?
- Request-04 - "Add data JSON" still has wrong unit of measure for porosity, permeability, grain density and such properties.
- Request-03 - "Add data (parquet)" still has wrong unit of measure for porosity, permeability, grain density and such properties.
- In the current approach, "unit of measure" value is repeated for each row. That is close to PPDM approach, and not close to OSDU Data Definition approach.
Copying to @bdawson and @Siarhei_Khaletski for information.