| ... | ... | @@ -16,6 +16,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 `ExtensionProperties` field of well logs 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. |
|
|
|
|
| [45 - Soft mapping of Las data to osdu wellbore and welllog objects](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/45) | Open (in progress) | Main development work is complete and held on the branch `45-soft-mapping-of-las-data-to-osdu-wellbore-and-welllog-objects`. The mapping module `record_mapper.py` was coimpletly re-written so that a user can define mappings for LAS format to the wellbore and wellheader OSDU objects in the configuration file. An example configuration file is [here](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/blob/45-soft-mapping-of-las-data-to-osdu-wellbore-and-welllog-objects/src/example_opendes_configuration.json). The `readme.md` file on the branch, documents the mapping format. This development work needs to be system tested, by that I mean a set of test uploads of LAS files to OSDU must be run before merging to main. |
|
|
|
|
| [45 - Soft mapping of Las data to osdu wellbore and welllog objects](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/45) | Open (in progress) | Main development work is complete and held on the branch [45-soft-mapping-of-las-data-to-osdu-wellbore-and-welllog-objects](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/tree/45-soft-mapping-of-las-data-to-osdu-wellbore-and-welllog-objects). The mapping module `record_mapper.py` was coimpletly re-written so that a user can define mappings for LAS format to the wellbore and wellheader OSDU objects in the configuration file. An example configuration file is [here](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/blob/45-soft-mapping-of-las-data-to-osdu-wellbore-and-welllog-objects/src/example_opendes_configuration.json). The `readme.md` file on the branch, documents the mapping format. This development work needs to be system tested, by that I mean a set of test uploads of LAS files to OSDU must be run before merging to main. |
|
|
|
|
| [13 Creating custom schema for LAS headers](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/13) | Open (not started) | This is the main custom schema mapping task. This task will cover testing of the upload of data into a custom schema and possibly extending and improving the soft mapping format implemented in [45](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/45). |
|
|
|
|
|
