|
|
## Overview
|
|
|
|
|
|
This page lists the outstanding tasks at project handover. At present there are 2 main threads of development.
|
|
|
|
|
|
1. *Support for WITSML upload*. This includes work to package and productionise the existing ITSML parser into a form that can be used by wbdutil and then to use this parser to support upload of WITSML data.
|
|
|
1. *Support for custom data schemas*. Some LAS data fields are currently not supported by the OSDU standard well logs schemas. This task will add the capability for users to be able to use a custom data mapping to map extend data fields to a predefined custom OSDU welllog type. |
|
|
1. **Support for WITSML upload**. This includes work to package and productionise the existing ITSML parser into a form that can be used by wbdutil and then to use this parser to support upload of WITSML data.
|
|
|
1. **Support for custom data schemas**. Some LAS data fields are currently not supported by the OSDU standard well logs schemas. This task will add the capability for users to be able to define a custom data mapping that allows them to map extend data fields to a predefined custom OSDU welllog type.
|
|
|
|
|
|
The history of work items should contain sufficient information to begin development.
|
|
|
|
|
|
## WITSML upload
|
|
|
|
|
|
## Support for custom data schemas.
|
|
|
|
|
|
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. |
|
|
|
|
|
|
|