... | ... | @@ -6,33 +6,41 @@ For detailed services that are included in this release, please refer to M9 tagg |
|
|
|
|
|
## New Features
|
|
|
|
|
|
* `Data Definition`
|
|
|
* `Core Services`
|
|
|
* `Data Definition`
|
|
|
* Persisted Collection: <span dir="">Moved </span>`master-data--Collection`<span dir=""> to the work-product-component group-type as </span>`osdu:wks:work-product-component--PersistedCollection:1.0.0`
|
|
|
* Generic Geometry Datasets: I<span dir="">n preparation of Generic Geometry Representations, we need content descriptions, which are specific enough to let consumers understand whether they can parse the data content or not.</span>
|
|
|
|
|
|
<span dir="">Dataset </span>`File.GeoJSON`<span dir=""> for </span>`WGS 84 `<span dir="">vector geometries.</span>\
|
|
|
<span dir="">Dataset </span>`FileCollection.Esri.Shape `<span dir="">added. Shapefiles can refer to any coordinate reference system (CRS) but not necessarily to a complete spatial reference allowing the geometry to be placed on the world map</span>.
|
|
|
* <span dir="">Reference Data Load Sequence: Visit </span>[here](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/reference-values/-/blob/master/Manifests/reference-data/IngestionSequence.json)<span dir="">, load sequence is provided, which prioritized manifests with content required by later manifests.</span>
|
|
|
* New Reference Values Added: <span dir="">New reference values have been added to support generic geometries and images</span> (`EncodingFormatType`<span dir="">, </span>`SchemaFormatType`<span dir=""> and </span>`AliasNameTypeClass`).
|
|
|
* `Core Services`
|
|
|
* Version endpoint - Indexer - Ability to return Elasticsearch version
|
|
|
* `Python SDK`
|
|
|
* `Workflow Services`
|
|
|
* `Python SDK`
|
|
|
* `Workflow Services`
|
|
|
* AirFlow 2.0 (define CSPs - Azure is not ready)
|
|
|
* `Data Ingestion`
|
|
|
* `Data Ingestion`
|
|
|
* Manifest by Reference
|
|
|
* `DDMS`
|
|
|
* <span dir="">LAS Loader</span> for Wellbore
|
|
|
* `DDMS`
|
|
|
* <span dir="">LAS Loader</span> for Wellbore
|
|
|
* `Well Delivery DMS`
|
|
|
* Introducing the Well Delivery DMS, focused on enabling the capture, storage and exchange of planning and execution details of well's drilling activities. The DMS focuses on a wide range of Drilling domain entities such as: Activities, Risks, Subsurface formations, Equipment used (tubulars, BHAs), Fluid programs, Cementing, Rig information and Daily Drilling Reports.
|
|
|
* The DMS has two sets of [APIs](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/well-delivery/well-delivery/-/blob/master/docs/api/swagger.yaml):
|
|
|
* a generic set of entity APIs that allow creation, deletion and retrieval of any entity type in the model
|
|
|
* a specific set of APIs aimed at retrieval of complex objects (Well Activity Programs, Activity Plans, Wells/Wellbores, Hole Sections, BHA runs and more)
|
|
|
* a generic set of entity APIs that allow creation, deletion and retrieval of any entity type in the model
|
|
|
* a specific set of APIs aimed at retrieval of complex objects (Well Activity Programs, Activity Plans, Wells/Wellbores, Hole Sections, BHA runs and more)
|
|
|
* For more details on the domain context of the DMS, please read our [Working Examples Documentation](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/well-delivery/well-delivery/-/blob/master/docs/Well_Planning_ReadMe.docx)
|
|
|
* For a complete overview overview of the DMS check out [this presentation](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/well-delivery/well-delivery/-/blob/master/docs/presentation/OSDU_Global_Event_-Well_Delivery_DDMS.pptx)
|
|
|
|
|
|
* The Well Delivery DMS is available on the following cloud platforms:
|
|
|
* Azure
|
|
|
* Google
|
|
|
* `Audit and Metrics`
|
|
|
* Provides KPI metrics which can help Operators to have a better governance on their Data Platform and effectively manage their resources. See [scope](https://community.opengroup.org/-/ide/project/osdu/platform/deployment-and-operations/audit-and-metrics/edit/master/-/docs/Audit___Metrics_M9_release_KPIs.xlsx).
|
|
|
* Provides KPI metrics which can help Operators to have a better governance on their Data Platform and effectively manage their resources. See [scope](https://community.opengroup.org/-/ide/project/osdu/platform/deployment-and-operations/audit-and-metrics/edit/master/-/docs/Audit___Metrics_M9_release_KPIs.xlsx).
|
|
|
|
|
|
## Bug Fixes
|
|
|
|
|
|
TBD
|
|
|
* `Data Definition`
|
|
|
* WellboreMarketSet: <span dir="">Similar modernization as for WellLog;1.1.0 and WellboreTrajectory:1.1.0. The content for the 'bulk' data matches the CSV fie as per </span>[<span dir="">this link</span>](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/wikis/Principles-for-Creating-OSDU-CSV-Templates#approved-templates).
|
|
|
* WellLog 1.1.0 Corrections: <span dir="">Based on issue </span>[<span dir="">255</span>](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/issues/255 "Well Log Curve depths and units in WellLog_1.1.0")<span dir=""> "Well Log Curve depths and units in WellLog_1.1.0", some deprecated properties (</span>`data.Curves[].TopDepth`<span dir="">, </span>`data.Curves[].BaseDepth`<span dir="">, </span>`data.Curves[].DepthUnit`<span dir="">) have been revived. The names stay unchanged to avoid disruptions for consumers. The description have been updated to note that the values may refer to other references than only depth.</span> [Got to the issue](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/issues/255).
|
|
|
|
|
|
## Breaking Changes
|
|
|
|
... | ... | |