|
|
This details the specific RESTful methods to target for R3 release:
|
|
|
|
|
|
For Wellbore / LogSet / Marker / Trajectory we provide those API:
|
|
|
- GET to get entity by ID, the return matches the WKS schema or a 404 if not found
|
|
|
- PUT to create or update an entity. The body matches the WKS schema
|
|
|
- DELETE to remove an entity in the lake from its ID with an option for deleting children entities. This is soft delete (similar to system core service one)
|
|
|
|
|
|
For Log we provide optimized array access API:
|
|
|
- GET to get a log by its OSDU log id, returns also meta information from the log array store
|
|
|
- PUT to create a log in OSDU and log array store giving entity data plus meta information for the log array store
|
|
|
- GET bulk log data with data in json (another api will be supporting binary format in near future)
|
|
|
- GET decimated bulk log data with data in json (another api will be supporting binary format)
|
|
|
- SET bulk log data with data in json (another api will be supporting binary format)
|
|
|
|
|
|
Search, we provide some search helpers. Users of the lake often does the same kind of queries:
|
|
|
- search all logset having some properties associated to a wellbore
|
|
|
- search all logs having some properties associated to a wellbore
|
|
|
- search all log having some properties associated to a logset
|
|
|
- search all wellbores in a given area
|
|
|
- search all logs given some criteria |
|
|
\ No newline at end of file |