| ... | ... | @@ -24,6 +24,4 @@ Related issues |
|
|
|
| [36 - Investigate custom schema best way forward](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/36 "Investigate custom schema best way forward") | 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 "Soft mapping of Las data to osdu wellbore and welllog objects") | Closed | 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 "Creating custom schema for LAS headers") | 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 "Soft mapping of Las data to osdu wellbore and welllog objects"). |
|
|
|
|
| [35 Investigate WITSML parser capability](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/35 "Investigate WITSML parser capability") | Open (in progress) | The existing WITSML parser provided by Energistics is suitable for parsing WITSML files and can output a JSON file (manifest) in the format required for uploading to OSDU. The issue is maintainability - the repository is extremely big with lots of dead and untested code. Etienne Peysson has began cleaning this code and making the parser available as a package on OSDU's registry. The goal is to have the Wellbore DDMS Data Loader import this package (which after extensive code cleaning will be maintainable as well). |
|
|
|
|
| [30 Loading WITSML Log data into Wellbore DDMS](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-data-loader/-/issues/30 "Loading WITSML Log data into Wellbore DDMS") | Open (not started) | Once the cleaning of the WITSML parser (referenced in the notes for issue 35), the Wellbore DDMS Data Loader shall be able to import the parser as a package and use it to build manifests for ingestion to OSDU. |
|
|
|
|
|
