@@ -197,7 +197,7 @@ In order to progress this solution, ExxonMobil, with EPAM, have:
Subsequent to this, as with any forum initiative, multiple companies and developers can contribute, coordinated though the appropriate OSDU PMC team. As of Aug. 2023, there are **recurring forum calls for this PMC Project** ([Thursdays, bi-weekly](https://www.opengroup.org/og_sduaggregatedcalendar)).
As of January 2025, the RAFS DDMS is expected to be fully released as a mature DDMS in the Milestone 25 (M25) OSDU release.
As of March 2025, the RAFS DDMS is expected to be fully released as a mature DDMS in the Milestone 25 (M25) OSDU release.
## Current Team Contacts (as of Dec. 2024)
...
...
@@ -239,7 +239,7 @@ As of December 2024, most of the WKSs are ready. There is, however, some clean-u
More explanation can be found in Data Definitions Documentation: [SampleAnalyses Worked Examples](https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/tree/master/Examples/WorkedExamples/SampleAnalyses?ref_type=heads)
**M25** M25 will be released in January 2025.
**M25** M25 will be released in April 2025.
The forum plan is both to have the WKSs cleaned up, and the RAFS DDMS graduated in M25, fully using the OSDU WKS schemas and mature content schemas.
...
...
@@ -386,3 +386,17 @@ You can read more about how the catalog schemas using this "meta" block and how
The storage is all in the same cluster as the rest of the OSDU deployment. But the RAFS DDMS sets up its own "bucket". Credentials come from the OSDU Partition Service. (This is the same approach as the Wellbore DDMS, as of March 2025.)
Note that in some previous experimental versions of the RAFS DDMS, this DDMS took a different approach: It used the "Dataset" group-type schemas to store the RAFS DDMS content using the OSDU core services. However, partially due to performance, and partially due to DDMS architectural principles (i.e., that DDMS content should only be accessible via the DDMS), this approach was abandoned.
### 14. For OSDU M25 (March 2025), the RAFS DDMS has an endpoint called "dev-samplesanalysis". What is this, and how does it relate to the main "samplesanalysis" (v2) endpoint?
Preparing for graduation, the RAFS DDMS team kept the "samplesanalysis" v2 endpoint unchanged (as stable as possible). However, we added capabilities under the "dev" version since the M24 release, to add new functionality for visibility into potential new capabilities, opening the opportunity for feedback and refinement.
The RAFS DDMS team considers the "dev" endpoint in the "alpha" testing phase.
* The ["dev" endpoint is documented here](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/rock-and-fluid-sample/rafs-ddms-services/-/tree/main/docs/dev), along with its filtering capabilities.
* The ["v2" endpoint is documented in the tutorial here](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/rock-and-fluid-sample/rafs-ddms-services/-/tree/main/docs/dev?ref_type=heads#available-metadata-fields), along with its filtering capabilities.
Some differences between the two as of March 2025:
* dev provides a search by WPC properties
* the syntax for filtering content properties is a little bit different
