@@ -400,3 +400,11 @@ 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
### 15. Within the scope of RAFS DDMS and its API calls, can the aliases within reference-data be used instead of their full ID string? e.g. Can we search or filter within the RAFS DDMS using the alias 'Methane' for properties where '{{NAMESPACE}}:reference-data--SampleCompositionComponent:C1' would be the correct reference-data ID?
Aliases, as they are implemented within OSDU, are not directly referenced in the master-data or content schema within RAFS DDMS. They are supported by OSDU, however.
On retrieval of data through a query within the RAFS DDMS API service, aliases will not be directly supported. It would be the responsibility of downstream applications to resolve a query using an alias via the OSDU search service and then run an API call using the reference-data alias' proper ID string.
On ingest and data preparation, data loading applications can check the reference lists within OSDU directly using the search service external to RAFS DDMS, and resolve the alias into its ID string prior to ingestion into RAFS DDMS.
