Merge pull request #285922 from sharad4u/master

August m23 release updates

Author: Stacyrch140

articles/energy-data-services/concepts-reference-data-values.md

@@ -24,9 +24,9 @@ Within the OSDU Data Platform framework, reference data values play a crucial ro
 In addition to enabling data interpretation and collaboration, reference data is required for data ingestion via the OSDU manifest ingestion workflow. Manifests provide a specific container for reference data values, which are then used to validate the ingested data and generate metadata for later discovery and use. To learn more about manifest-based ingestion, see [Manifest-based ingestion concepts](concepts-manifest-ingestion.md). 
 
 The OSDU Data Platform categorizes Reference data values into the following three buckets:
-* **FIXED** values, which are universally recognized and used across OSDU deployments and the energy sector. These values can't be extended or changed except by OSDU community governance updates
-* **OPEN** values. The OSDU community provides an initial list of OPEN values upon which you can extend but not otherwise change
-* **LOCAL** values. The OSDU community provides an initial list of LOCAL values that you can freely change, extend, or entirely replace
+* **FIXED** values: This set of reference values is universally recognized and used across OSDU deployments and the energy sector. These values can't be extended or changed except by OSDU community governance updates
+* **OPEN** values: The OSDU community provides an initial list of OPEN values upon which you can extend but not otherwise change
+* **LOCAL** values: The OSDU community provides an initial list of LOCAL values that you can freely change, extend, or entirely replace
 
 For more information about OSDU reference data values and their different types, see [OSDU Data Definitions / Data Definitions / Reference Data](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/02-GroupType.md#22-reference-data).
 
@@ -60,7 +60,7 @@ If you extend OPEN values after instance creation, we recommend creating and usi
 **NameAlias updates** don't require a separate entitlement. Updates to the `NameAlias` field are governed by the same access control mechanisms as updates to any other part of a storage record. In effect, OWNER access confers the entitlement to update the `NameAlias` field.
 
 ## Current scope of Azure Data Manager for Energy reference data value syncing
-Currently, Azure Data Manager for Energy syncs reference data values at instance creation and at new partition creation. Reference values are synced to those from the OSDU community, corresponding to the OSDU milestone supported by Azure Data Manager for Energy at the time of instance or partition creation. For information on the current milestone supported by and available OSDU service in Azure Data Manager for Energy, refer [OSDU services available in Azure Data Manager for Energy](osdu-services-on-adme.md).
+Currently, Azure Data Manager for Energy syncs reference data values at instance creation and at new partition creation for newly created instances after feature enablement. Reference values are synced to those from the OSDU community, corresponding to the OSDU milestone supported by Azure Data Manager for Energy at the time of instance or partition creation. For information on the current milestone supported by and available OSDU service in Azure Data Manager for Energy, refer [OSDU services available in Azure Data Manager for Energy](osdu-services-on-adme.md).
 
 ## Next steps
 - [Quickstart: Create Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md)

articles/energy-data-services/osdu-services-on-adme.md

@@ -4,18 +4,16 @@ description: This article provides an overview of the OSDU services available on
 author: bananibrahim
 ms.service: energy-data-services
 ms.author: bananibrahim
-
 ms.topic: conceptual
-ms.date: 06/14/2024
+ms.date: 08/30/2024
 ms.custom: template-concept
 ---
 
-# OSDU® M18 services available on Azure Data Manager for Energy 
-Azure Data Manager for Energy is currently compliant with the M18 OSDU® milestone release. Below you'll find an overview of the OSDU® services that are currently available on Azure Data Manager for Energy. This page will be regularly updated as service versions and availability evolve. 
+# OSDU® M23 services available on Azure Data Manager for Energy 
+Azure Data Manager for Energy is currently compliant with the M23 OSDU® milestone release. Below you'll find an overview of the OSDU® services that are currently available on Azure Data Manager for Energy. This page will be regularly updated as service versions and availability evolve. 
 ### Core and helper services
 - **CRS Catalog**: Provides API endpoints to work with geodetic reference data, allowing developers to retrieve CRS definitions, select appropriate CRSs for data ingestion, and search for CRSs based on various constraints. 
 - **CRS Conversion**: Enables the conversion of coordinates from one coordinate reference system (CRS) to another.
-- **CSV Parser DAG**: Helps in parsing CSV files into a format for ingestion and processing. 
 - **Dataset**: Provides internal and external API endpoints to allow and application or user fetch storage/retrieval instructions for various types of datasets.
 - **Entitlements**: Used to enable authorization in OSDU Data Ecosystem. The service allows for the creation of groups. A group name defines a permission. Users who are added to that group obtain that permission. The main motivation for entitlements service is data authorization, but the functionality enables three use cases: Data groups used for data authorization, Service groups used for service authorization, User groups used for hierarchical grouping of user and service identities.
 - **File**: Provides internal and external API endpoints to let the application or user fetch any records from the system or request file location data. 
@@ -27,7 +25,7 @@ Azure Data Manager for Energy is currently compliant with the M18 OSDU® milesto
 - **Register**: Allow an application to register an action (the function to be triggered). It expects data (context) to come from OSDU to enable the action, and the application can register a filter (enable/disable) to say what data can be used with this action.
 - **Schema**: Enables a centralized governance and management of schema in the Data Ecosystem. It offers an implementation of the schema standard. Schema Service provides all necessary APIs to Fetch, create, update, and mark a schema obsolete.
 - **Search**: Provides a mechanism for searching indexes. Supports full-text search on string fields, range queries on dates, numeric, or string fields, etc., along with geo-spatial search.
-- **Secret**: Facilitates the storage and retrieval of various types of secrets in a specified repository(ies) so that secrets can be secure, separated from the secrets in the infrastructure repository, and be managed easily by interfacing applications.
+- **Secret (Preview)**: Facilitates the storage and retrieval of various types of secrets in a specified repository(ies) so that secrets can be secure, separated from the secrets in the infrastructure repository, and be managed easily by interfacing applications.
 - **Seismic File Metadata**: Manages metadata associated with seismic data. It annotates dimensions, value channels, and generic key/value pairs.
 - **Storage**: Provides a set of APIs to manage the entire metadata life-cycle such as ingestion (persistence), modification, deletion, versioning, and data schema.
 - **Unit**: Provides dimension/measurement and unit definitions.
@@ -42,18 +40,25 @@ Azure Data Manager for Energy is currently compliant with the M18 OSDU® milesto
   - **EDS Fetch & Ingest DAG**: Facilitates fetching data from external providers and ingesting it into the OSDU platform. It involves steps like registering with providers, creating data jobs, and triggering ingestion.
   - **EDS Scheduler DAG**: Automates data fetching based on predefined schedules and sends emails to recipients as needed. It ensures data remains current without manual intervention
 -  **Ingestion Workflow**: Initiates business processes within the system. During the prototype phase, it facilitates CRUD operations on workflow metadata and triggers workflows in Apache Airflow. Additionally, the service manages process startup records, acting as a wrapper around Airflow functions.
+- **Manifest Ingestion DAG**: Used for ingesting single or multiple metadata artifacts about datasets in Azure Data Manager for Energy instance. Learn more about [Manifest-based ingestion](concepts-manifest-ingestion.md).
+- **CSV Parser DAG**: Helps in parsing CSV files into a format for ingestion and processing. 
 - **osdu-airflow-lib**: A library that enables user context ingestion within the Airflow workflows.
 - **osdu-ingestion-lib**: A library that supports user context ingestion and includes various fixes related to Python versioning and authority replacement.
 - **SegY-to-oVDS DAG**: Converts SegY file formats to oVDS.
 - **SegY-to-oZGY DAG**: Converts SrgY file formats to ZGY.
 
 ## OSDU® services unavailable on Azure Data Manager for Energy
 Note: The following OSDU® services are currently unavailable on Azure Data Manager for Energy.
+- **Reservoir DDMS**
 - **EDS Naturalization DAG**
-- **Energistics Parser DAG**
-- **Geospatial Consumption Zone**
 - **Manifest Ingestion by Reference DAG**
+- **Seismic DDMS v4 APIs**
+- **Rock and Fluid Sample DDMS**
+- **Production DDMS - Historian**
+- **WITSML Parser DAG**
+- **Energistcs Parser DAG (WITSML Parser v2, Resqml Parser, ProdML Parser)**
+- **Geospatial Consumption Zone**
 - **Partition** Note: Operations can still be performed using the available data partition APIs or through Azure portal.
 - **Policy Service**
-- **Reservoir DDMS**
-- **WITSML Parser DAG**
+- **Schema Upgrade**
+- **Wellbore Domain Services Worker**

articles/energy-data-services/release-notes.md

@@ -23,6 +23,15 @@ This page is updated with the details about the upcoming release approximately a
 
 <hr width = 100%>
 
+## August 2024
+
+### Compliant with M23 OSDU&reg; release
+Azure Data Manager for Energy has now been upgraded with the supported set of services with the M23 OSDU&reg; milestone release. With this release, you can take advantage of the key improvements made in the OSDU&reg; latest 
+ community features and capabilities available in the [OSDU&reg; M23](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M23-Release-Notes) The upgrade with the OSDU&reg; M23 release is limited to the services available and supported and you can refer [here](osdu-services-on-adme.md) for a detailed list of services available and unavailable on Azure Data Manager for Energy. See the [updated API Swaggers here](https://microsoft.github.io/adme-samples/).
+
+### Syncing Reference Values
+We are releasing a Limited Preview for syncing Reference Values with your Azure Data Manager for Energy data partitions. Note that this feature is currently only available for newly created Azure Data Manager for Energy after feature enablement for your Azure subscription. Learn more about [Reference Values on Azure Data Manager for Energy](concepts-reference-data-values.md).
+
 ## June 2024
 
 ### Azure Data Manager for Energy Developer Tier Price Update