ComponentReasonIDs element missing in M23 reference data

Hi.

We are not setting up a M23 OSDU server. For this we use Microsoft ADME. We do experience a problem when ingesting the reference data to the server. Airflow generates a lot of error messages (many for the same error I suspect), and then refuse to add several of the reference data types. Now, there probably are several data types with problems, but I have isolated one reference data type to try and debug this.

I chose osdu:wks:reference-data--DowntimeReasonDetailType:1.0.0. It is a LOCAL reference data type.

After ingestion, Airflow fails it, and does not enter it because of the ComponentReasonIDs element. Airflow says that element is missing (and rightly so, there are no ComponentReasonIDs in the reference data file from OSDU), and that this element is a required element. I have checked by retrieving the schema from the server that this element is indeed required. I have also verified by looking at the schemas from OSDU (both v0.26.1.1 and up to the latest schema available) that this element is marked as required in all schemas, so the M23 ADME server is right in throwing out the reference data we try to ingest.

We are working on ingesting v0.26.1.1 reference data, but I have looked into the latest versions of DowntimeReasonDetailType as well and none of them has the ComponentReasonIDs element.

AS I said, there are many Airflow error on our server after trying to ingest reference data (several hundreds) and I have not had the time to investigate more than this one in detail, but I have a sneaky suspicion this problem is larger that just this particular data type.

Can you please check this up? Is this a larger problem with many data types (schemas defining required elements and input reference data missing these) or a one of? What do you recommend we do to handle it?

Regards, Frode Lande (fjlan@equinor.com) Equinor ASA