| ... | ... | @@ -15,6 +15,6 @@ Related issues |
|
|
|
|
|
|
|
| Issue | status | Notes |
|
|
|
|
| ----- | ------ | ----- |
|
|
|
|
| [36 - Investigate custom schema best way forward](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/36) | Closed | We determined that the Extended properties field could be used to include additional fields that could be searched upon. An important note is that in the schema definitions nested objects should use the `"x-osdu-indexing": { "type": "nested" }` in order to be searched upon. |
|
|
|
|
| [36 - Investigate custom schema best way forward](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/36) | Closed | We determined that the `ExtensionProperties` field could be used to include additional fields that could be searched upon. An important note is that in the schema definitions nested objects should use the `"x-osdu-indexing": { "type": "nested" }` in order to be searched upon. See the comment log in the task for further information. An example extended properties schema definition is [here](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/blob/main/dev/schema/WellLogExtensions.json) and the corresponding extended welllogs example schema definition is [here](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/blob/main/dev/schema/SlbExtendedWellLog.json) look for the `ExtensionProperties` field. |
|
|
|
|
|
|
|
|
|
